Date: 04/24/01
- Next message: fabiankessler <email protected>: "[PHP-DEV] Bug #10483: someFunction() OR break;"
- Previous message: Anil Madhavapeddy: "Re: [PHP-DEV] 4.0.5: Merge Request"
- In reply to: Liz: "[PHP-DEV] RE: 4.0.5: Merge Request"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] 4.0.5: Merge Request"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
hi,
> Maybe something like this
>
> 1. Any problems which result in seg faults/gpfs are show stoppers, code
doesnt
> go out till its fixed, or feature is removed till we can fix it.
this is not correct (in general :) - there are segfaults in experimental
stuff that do not imply exploits, are no security risk and are just a
new/unused feature that does not work as expected. it IS ok to release with
such a segfault. an example:
bbonev <email protected>:~$ echo "<? \$a=1 ?>" | php -a
Interactive mode enabled
X-Powered-By: PHP/4.0.5RC6
Content-type: text/html
Segmentation fault
see bug id 8621
i think commonsense shall be used to judge what is showstopper and what is
not :)
this one definitely is not
b.
-- 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: fabiankessler <email protected>: "[PHP-DEV] Bug #10483: someFunction() OR break;"
- Previous message: Anil Madhavapeddy: "Re: [PHP-DEV] 4.0.5: Merge Request"
- In reply to: Liz: "[PHP-DEV] RE: 4.0.5: Merge Request"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] 4.0.5: Merge Request"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

