Re: [PHP-LANG] "Mission Statement"

Why not have both sets of documents?

Users at my level of skill would value a readable and authoritative guide 
to how PHP can be expected to behave, while having a standards document 
will probably help the core developers make better choices when working on PHP.

The guide for PHP users would probably be fastest and easiest to develop, 
and should provide a solid base for the specifications document.

Just my $0.02 CA

  --zak


At 02:18 AM 11/21/00 +0200, you wrote:
>At 02:04 21/11/2000, Sascha Schumann wrote:
>>     Would you want to standardize a feature which works on
>>     Linux/ia32, but not on Linux/Alpha?
>>
>>     That is reality, as far as I am concerned, and something
>>     which we should not simply put aside.
>
>You have a point there, but since we're not planning to become Java 
>anywhere in the near future, I think we need to find something in the middle.
>I think that documenting platform specific behavior, clearly denoting it 
>as such, is acceptable.
>
>>     Well, we will have to evaluate the impact of a particular
>>     feature and come to a decision on whether it is a valid
>>     behaviour which we want to continue or a mere side-effect.
>>     Most things in PHP are well understood, but there are some
>>     areas (like reference passing) which are neither well-
>>     understood (by the users) nor well-defined.
>
>OK (reference passing is well defined, BTW, but undoubtfully, not well 
>understood :)
>
>Zeev
>
>--
>Zeev Suraski   <[email protected]>
>CTO, Zend Technologies Ltd.  http://www.zend.com/
>
>
>--
>PHP Language Mailing List (http://www.php.net/)
>To unsubscribe, e-mail: [email protected]
>For additional commands, e-mail: [email protected]
>To contact the list administrators, e-mail: [email protected]