Date: 03/21/01
- Next message: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Previous message: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> I don't think that there would be a real life situation in which a new
> module would break a build under one platform, and won't under another
> platform, without you actually using the module. The author has to be
> exceptionally 'talented' to achieve that.
The config.m4 just has to reach a certain complexity to
become incomprehensible. I suggest reading ext/gd/config.m4
for starters.
> I know, and as I said, I disagree. I don't think it can go unnoticed in
> the further RC.
Ah, of course. Just as newly introduced bugs in the code are
catched by further RCs..
- Sascha Experience IRCG
http://schumann.cx/ http://schumann.cx/ircg
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Previous message: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4(PHP_4_0_5) /sapi/fastcgi"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

