Derick Rethans wrote:
> On Mon, 3 Oct 2005, Greg Beaver wrote:
>
>
>>> 1. zlib is required now with php, and by default php isn't installed
>>> with zlib nor does configure catch this, so, while make install is
>>> running and when pear is being installed make dies leaving a bad
>>> installat
Matthew Kavanagh wrote:
> Would that really be a problem, given that compressing a compressed file
> and compressing an uncompressed file will usually yield similar sized
> resultant files?
>
...and I failed to see the previous email that says the same thing.
Genius at work.
Lester Caine wrote:
I'm sure many people have their own preferred tools for creating files
- all I was trying to say was that - is taint support actually needed
at run time? Something that improves the visibility of mistakes while
editing files seems to be more worthwhile - something that can a
Ilia Alshanetsky wrote:
So you propose to give a partially working tool that promises data
security and then expect people not to rely on it 100% because it is
easy to
Nobody at all in this discussion has suggested taint promises data
security. Nobody has said it promises anything. But an imper
Ilia Alshanetsky wrote:
To use your car analogy and safe_mode history, most users will start
driving like maniacs, violating every traffic law thinking that the
seat belt makes them invincible.
Most users drive like maniacs anyway, and it will ever be so. Taint mode
cannot save people from them
Rasmus Lerdorf wrote:
Stanislav Malyshev wrote:
Compile-time resolution means you don't get performance penalty for
namespaces when you are not using it, and have very low costs when you
do use it. Allowing blanket imports means we don't know what "new Foo()"
means until it is executed - mean
