Re: [PEPr] Comment on Text::Diff

Jon Parise wrote:

1 class = 1 file is occasionally just silly and wasteful. I don't intend to change that.

It's also not a PEAR standard. Witness the DB package's declaration of four classes in DB.php (which I think is fine).

That is one thing I found slightly annoying about DB - when i first read the code - I had to hunt around alot guessing where the classes where defined.. It is quite often useful to stick everything in one file when you are developing and designing the code, but when it gets to stable - making it clear for others to read usually outweights any advantage.

Nor is "one class :: one file" a standard:

    http://pear.php.net/manual/en/standards.php

Yes. The PEAR "channels" feature is designed to enhance this option, as well.

Yeah if I had more time - and spent less of it writing annoying emails :) -- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com