* Jim Cromie <[EMAIL PROTECTED]> [2003-11-14 17:43]: > Its not 'particular' to C, except in reduce(), the last step, > which acts on the detected redundancies. As I outlined, a Perl > version could move chunks into strings, then eval that in the > many places its needed.
Then maybe it should be split into two modules, one making use of the other. > Parse::* makes promises about its capabilities / sophistication > which are untrue. I know.. I noted that myself, but it seemed the cloest I could think of. > Indeed its an implementation thing, but 'Shred' is unlikely to > be confused with anything else, except perhaps 'rm -rf *', > which most people wouldnt look on CPAN for ;-) It will certainly be confused! File::Shred to me sounds like a secure deletion module which does one of those "overwrite filedata X times before deleting" algorithms. > And because 'shred' is open-source, and part of the Linux vs > SCO drama, it serves as something of a touchstone - By > understanding the algorithm, you know its > advantages/disadvantages; fast but naive compared to parsing to > an ASN. Good point. Algorithm::Shred? > Its also applicable to any line-oriented text, not just > programs, hence the File:: Again, Algorithm::Shred sounds more like it. The C-specific part would then be provided in another module which would have to be named independently, probably leaving C as the last part of the name so there is ::C, ::Perl etc. -- Regards, Aristotle "If you can't laugh at yourself, you don't take life seriously enough."
