Date: 09/29/01
- Next message: mike: "[PHP-DEV] Segfault on writing to shared memory block"
- Previous message: Sander Steffann: "Re: [PHP-DEV] why does exit() print its argument?"
- In reply to: Sander Steffann: "Re: [PHP-DEV] why does exit() print its argument?"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Reply: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Reply: Yasuo Ohgaki: "Re: [PHP-DEV] why does exit() print its argument?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Usualy I am very much against breaking backwards compatibility, but in this
> case I think it's the best thing to do... Because:
> - It's already documented that way
> - It's the 'expected' behaviour (from other languages, and from the docs)
>
> As Rasmus said: It would be surprising if this broke a lot of (or even any)
> code.
+1
Hey, my second vote O_o
-- 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: mike: "[PHP-DEV] Segfault on writing to shared memory block"
- Previous message: Sander Steffann: "Re: [PHP-DEV] why does exit() print its argument?"
- In reply to: Sander Steffann: "Re: [PHP-DEV] why does exit() print its argument?"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Reply: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Reply: Yasuo Ohgaki: "Re: [PHP-DEV] why does exit() print its argument?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

