On Oct 5, 2010, at 07:45, Rob van der Heij wrote: > > That made sense to me since we don't have > another easy way to compare a string with a character (or do we)? > How about CLCL with a padding character? (Or am I spoiling the riddle?)
>> Then Frank Ramaekers' reply reminded me that I, too, have written code to >> replace 16 (or hundreds, or thousands, of) consecutive identical bytes with >> the one phrase "Same as above." And I have done so more than once. > > But that would involve comparing two strings, rather than a string > with a character? I would be pretty annoyed reading a dump and get > portions omitted with "... these 32 byte are all the same, guess what > they are..." > The do the overlapping compare with offset 32, and report "previous 32 bytes repeated nnn times." -- gil
