Re: cvs: php4 /ext/standard file.c

From: Date: Fri, 22 Dec 2000 19:14:32 +0000
Subject: Re: cvs: php4 /ext/standard file.c
References: 1  Groups: php.cvs 
Request: Send a blank email to php-cvs+get-3245@lists.php.net to get a copy of this message
It's *not* a question of interpreting text. I really don't know why you pick this cold all-knowing-like condescending attitude. Why is it not a question of interpreting text? Because there's no question as to what the text means. Why is it still a question? Because if miraculously, all available platforms behave like this even though it's not documented, I'd use it. True, some obscure platforms may behave differently. New platforms may not behave like this. Bottom line is that it's much better than the current situation, much much better. As MySQL is an application that works with disks intensively, I'd imagine that this code is well tested. Knowing Monty, he can probably give you a short lecture about this and how it behaves on the various platforms. Zeev At 21:03 22/12/2000, Sascha Schumann wrote:
On Fri, 22 Dec 2000, Zeev Suraski wrote: That's what I said in the subsequent letter. I tend to believe that this code is correct, for one main reason - the guy who wrote it has more real-world experience than all three of us combined times 2.
    This is an issue of interpreting a text.  The error in MySQL
    shows up only in obscure corner cases, and I certainly think
    that it can go unnoticed for years.
    If you don't trust your judgment when it comes to
    interpreting texts, I'd suggest to ask any active contributor
    to the Austin Group[1].  Those often act as standard lawyers
    and should be equipped with the right knowledge to make a
    decision.
    [1] http://www.opengroup.org/sophocles/show_subscribers.tpl?listid=2481
    - Sascha
-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/

« previous php.cvs (#3245) next »