On Fri, Feb 09, 2001 at 02:53:43PM -0600, Jarkko Hietaniemi wrote: > On Fri, Feb 09, 2001 at 06:46:26PM -0200, Branden wrote: > > problems (like `oh! I don't have bzip2 and the developper only supplied a > > bzip2 version of the archive', or `oh! I'll have to do zip, tgz, bzip2, > > whatever3 versions of the same thing only to satisfy users that use > > different formats'). > > And how is this different from 'oh! I don't have unzip'? Code to do unzip (yes, even including the whole of zlib just like gcc, xfree86 and several other things I can't remember offhand that irritate me as I have libz.so) is small enough to go in the perl core if needed. It's smaller than Encode by a long way :-) [or is that :-(] > > I think we should go for `standard' rather than `flexible' on this one. > > As I said on this I disagree. > > I have no problem with in the first implementation round doing just zip: > what I abhor is the idea of hardwiring the zip assumption deeply into > our design. I would agree - hardwiring is to be avoided. Nicholas ClarkThread Previous | Thread Next