Re: [PHP-DEV] Re: exit() / die()

I'm glad I read the list. Doing (a) will break several scripts that my site depends on. Ok, I was mistaken in thinking it wouldn't break (a lot of) existing code. Zeev Suraski [EMAIL PROTECTED] wrote in message news:5.1.0.14.2.20010929020430.051aa2a8@localhost... Guys, Changing these

[PHP-DEV] MySQL_Num_Rows functionality

mysql_num_rows() to a result that returned zero rows returns 'Supplied argument is not a valid MySQL result resource'. If it is an invalid resource (such as SELECT * from table to an empty table), shouldn't it return ZERO (0). That seems to make the most sense, as opposed to throwing

[PHP-DEV] Öйú²ÅÍø֪ͨ

Title: °Ù´óÍø/Óʼþ ¡¡¹úÄÚΨһµÄÒ»¸öԺУÈ˲ÅÍøÕ¾Á¬Ëøƽ̨ Badajob.com ÎʺòÄú

Re: [PHP-DEV] why does exit() print its argument?

Markus Fischer wrote: 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

Re: [PHP-DEV] MySQL_Num_Rows functionality

Ignore. This only happened for a few minutes and without changing anything started working. I don't know why. -- Mike - Original Message - From: Mike Rogers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, September 30, 2001 12:48 AM Subject: [PHP-DEV] MySQL_Num_Rows

[PHP-DEV] exit() and discussion

Zeev, You are right that there is no immidiate reason for changing exit() right now to behave as expected. However, I think most have to admit that its a bad story[tm] that exit() evolved to it what it is right now. As you see many people expect exit() to behave like its C counterpart; and,