Re: Re: svn: /php/php-src/ branches/PHP_5_2/NEWS branches/PHP_5_2/ext/pcre/pcrelib/AUTHORS branches/PHP_5_2/ext/pcre/pcrelib/ChangeLog
branches/PHP_5_2/ext/pcre/pcrelib/HACKING branches/PHP_5_2/ext/pcre/pcrelib/LICENCE branches/PH
| From: | Alexey Zakhlestin | Date: | Fri, 29 Jan 2010 11:26:20 +0000 |
| Subject: | Re: Re: svn: /php/php-src/ branches/PHP_5_2/NEWS branches/PHP_5_2/ext/pcre/pcrelib/AUTHORS branches/PHP_5_2/ext/pcre/pcrelib/ChangeLog branches/PHP_5_2/ext/pcre/pcrelib/HACKING branches/PHP_5_2/ext/pcre/pcrelib/LICENCE branches/PH |
||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-46906@lists.php.net to get a copy of this message | ||
On 29.01.2010, at 13:32, Pierre Joye wrote:
> On Fri, Jan 29, 2010 at 9:36 AM, Alexey Zakhlestin <indeyets@gmail.com> wrote:
>> As far as I remember, it was decided that C99 is ok for php6.
>
> I can't remember any decision about C99.
I remember some talk with andrei on irc… I guess we never wrote that down
>
>> Anyway, we probably need to compose some table on what compilers have limited (and how
>> limited) support for c99.
>> Then we can objectively decide if we can leave those aside
>
> That's not a solution, or we kill solaris, HPUX, windows, etc.
> support. GCC does a very bad job here by enabling part of C99 by
> default and breaking the other half of the specs. Also C99 is pretty
> much a bastarized version of C++ in an incompatible way. The price to
> accept C99 is too high, especially when all we use (in 99.99999% of
> what the usages) is stdint/stdbool.
>
> Simply detect and define them at configure time will kill the need to
> use c99 and keeps us on the good/right side (what I do on win for
> example,easy) :)
you forgot about C++-style comments :)
Does Visual Studio support none of C99? I thought recent versions had partial support