Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query andpossible integer overflow?

Thanks guys for your feedback. With regard to PEAR, I've had to patch PEAR::DB::mysql to solve another problem I've had with the prepared_queries field growing steadily. I'm sure this is also a problem with the either DB subclasses. I'll post my patch to pear-dev as I don't have a CVS account yet.

Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query and possible integer overflow?

D'oh - read too little, too fast. :) On Tue, Mar 25, 2003 at 05:55:42PM -0800, Zeev Suraski wrote: > I believe he meant the query id's that the engine uses, and not the auto > increment id's. Wez's response was accurate, we'll overflow at some > point. This is basically because PHP was designe

Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query and possible integer overflow?

I believe he meant the query id's that the engine uses, and not the auto increment id's. Wez's response was accurate, we'll overflow at some point. This is basically because PHP was designed with short requests in mind. We could probably fix it relatively easily for ZE2. Zeev At 13:15 25/03

Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query and possible integer overflow?

On Tue, Mar 25, 2003 at 01:50:17PM +, Matt Flaherty wrote: > Hi, > > I have a question for the authors of the mysql extension. I'm sure you > gentlemen are very busy, but I'd appreciate your insight if you can > spare a moment. I'm developing a stand-alone php application running in > an infin

Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query andpossible integer overflow?

Thanks Wez, If all that happens is the query will fail, I can live with that. It's a simple SELECT query called over and over again. If the integer wraps around negative, I'm guessing that would probably have undesirable effects. If not, then I can let it run forever. What I don't want is somethin

Re: [PHP-DEV] Question for Zeev, Zak or Georg - mysql_query andpossible integer overflow?

Hi Matt, Yes, there is a risk of overflow. >From my understanding, the id is signed, so you will hit overflow at 2G rather than 4G resources. This applies to any/all PHP/ZE resources. I'm not sure what happens when it overflows; it seems like the query would fail. You could design your applicati

Re: [PHP-DEV] Question about zend_compile

Look at apc. It tracks per-file function and class tables. http://apc.communityconnect.com/ (v2.0) pear/PECL/apc (v1.x) Both versions do the thing you wish for. -- PHP Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP-DEV] Question on bug list

On Sun, Feb 02, 2003 at 01:17:41PM -0800, Sara Golemon wrote: > > Jesus suggested the same thing, I'm trying out a few different approaches > to > > see what looks best, I'll post again when I have something usable. > > > http://frankenbox.alphaweb.net/test/export.phps > Looks good and useful. +1

Re: [PHP-DEV] Question on bug list

> > Wouldn't it be nice/more useful to generate RDF/RSS on a per-bug basis? > > Then you could just add the feed url to your favourite RSS client. > > > > If you make it do that, then I will take a look and commit, provided > > that there are no objections to this. > > > Jesus suggested the same th

Re: [PHP-DEV] Question on bug list

> Wouldn't it be nice/more useful to generate RDF/RSS on a per-bug basis? > Then you could just add the feed url to your favourite RSS client. > > If you make it do that, then I will take a look and commit, provided > that there are no objections to this. > Jesus suggested the same thing, I'm tryin

Re: [PHP-DEV] Question on bug list

Hey, Wouldn't it be nice/more useful to generate RDF/RSS on a per-bug basis? Then you could just add the feed url to your favourite RSS client. If you make it do that, then I will take a look and commit, provided that there are no objections to this. --Wez. On Fri, 31 Jan 2003, Sara Golemon wro

Re: [PHP-DEV] Question on bug list

> > >I had two questions: One to assign to all NEW messages and one > > >feature request to assign to selective bugs...I wanted to avoid reading > > >all messages on any bug. Thats overkill... > > > > Get a mail client that can handle threading.. > > PHP-Bugs doesn't have "In-Reply-To" and "Ref

Re: [PHP-DEV] Question on bug list

hi, > >I had two questions: One to assign to all NEW messages and one > >feature request to assign to selective bugs...I wanted to avoid reading > >all messages on any bug. Thats overkill... > > Get a mail client that can handle threading.. PHP-Bugs doesn't have "In-Reply-To" and "References

Re: [PHP-DEV] Question on bug list

> I have a "daily page" I go to every morning which contains all my news > feeds, some comic strips, movie listings, etc If there were a > programmatic query interface to bugs.php.net I could select bug #s to track, > and be able to bring up histories of them from my daily page. > To that end..

Re: [PHP-DEV] Question on bug list

> > Wouldn't it be nice if one could attach himself to a bug and receive an email > > on every new message to that bug? > > I have a "daily page" I go to every morning which contains all my news feeds, some comic strips, movie listings, etc If there were a programmatic query interface to bugs.p

Re: [PHP-DEV] Question on bug list

[EMAIL PROTECTED] (Marcus Börger) wrote: > Wouldn't it be nice if one could attach himself to a bug and receive an email > on every new message to that bug? > > And then how am i informed about new bugs? Is there a mailing list for that? > Currently i read the bug-summary-list.. I was thinking o

Re: [PHP-DEV] Question on bug list

At 11:37 31.01.2003, Jani Taskinen wrote: On Fri, 31 Jan 2003, Marcus Börger wrote: >I had two questions: One to assign to all NEW messages and one >feature request to assign to selective bugs...I wanted to avoid reading >all messages on any bug. Thats overkill... Get a mail client that can

Re: [PHP-DEV] Question on bug list

On Fri, 31 Jan 2003, Marcus Börger wrote: >I had two questions: One to assign to all NEW messages and one >feature request to assign to selective bugs...I wanted to avoid reading >all messages on any bug. Thats overkill... Get a mail client that can handle threading.. --Jani

Re: [PHP-DEV] Question on bug list

At 10:24 31.01.2003, Thomas Seifert wrote: On Fri, 31 Jan 2003 02:49:01 + [EMAIL PROTECTED] (Daniel Lorch) wrote: > hi, > > > > Wouldn't it be nice if one could attach himself to a bug and receive an > > > email > > > on every new message to that bug? > > > > > > And then how am i informed

Re: [PHP-DEV] Question on bug list

On Fri, 31 Jan 2003 02:49:01 + [EMAIL PROTECTED] (Daniel Lorch) wrote: > hi, > > > > Wouldn't it be nice if one could attach himself to a bug and receive an > > > email > > > on every new message to that bug? > > > > > > And then how am i informed about new bugs? Is there a mailing list f

Re: [PHP-DEV] Question on bug list

hi, > > Wouldn't it be nice if one could attach himself to a bug and receive an > > email > > on every new message to that bug? > > > > And then how am i informed about new bugs? Is there a mailing list for > > that? > > Currently i read the bug-summary-list.. > > > > [EMAIL PROTECTED] Empty

Re: [PHP-DEV] Question on bug list

Marcus Börger wrote: Wouldn't it be nice if one could attach himself to a bug and receive an email on every new message to that bug? And then how am i informed about new bugs? Is there a mailing list for that? Currently i read the bug-summary-list.. [EMAIL PROTECTED] marcus -- PHP Dev

Re: [PHP-DEV] Question on SSL.

ED]> To: "Wei Weng" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, January 27, 2003 1:02 PM Subject: Re: [PHP-DEV] Question on SSL. > Hello, > > please forward user questions to the [EMAIL PROTECTED] > mailinglist, this list is for development

Re: [PHP-DEV] Question on SSL.

Hello, please forward user questions to the [EMAIL PROTECTED] mailinglist, this list is for development _OF_ PHP, not development _with_ PHP. Derick On Mon, 27 Jan 2003, Wei Weng wrote: > This question is a bit Apache specific. > > How does PHP detect whether it is on a SSL connection (with re

Re: [PHP-DEV] Question, might be stupid...

Le Jeudi 26 Septembre 2002 04:12, Ken a écrit : > I have a HTML form that has a session variable called $cost. Now I want to > set the value to this table data input field. Anyone know how this is > accomplished? > > > > Thanks in advance! This list is only intended for core PHP development. You

Re: [PHP-DEV] question type

; Sent: Thursday, September 19, 2002 3:06 PM Subject: Re: [PHP-DEV] question type > > Vergoz Michael (SYSDOOR) wrote: > >> does PHP support _s64 type ? > > there is no such thing as a _s64 type in C, > what you are refering to is a typedef to > a native C type of that s

Re: [PHP-DEV] question type

> Vergoz Michael (SYSDOOR) wrote: >> does PHP support _s64 type ? there is no such thing as a _s64 type in C, what you are refering to is a typedef to a native C type of that size ... [EMAIL PROTECTED] wrote: > No, PHP has only: > > null > bool (true or false) > string > integer (signed, 32 bi

Re: [PHP-DEV] question type

On Thu, 19 Sep 2002, Vergoz Michael (SYSDOOR) wrote: > hi list, > > does PHP support _s64 type ? No, PHP has only: null bool (true or false) string integer (signed, 32 bits) array object Derick --- Derick Rethans

RE: [PHP-DEV] question

a) Yes, if and only if memory has been allocated and you have to deallocate it. Otherwise a memory leak occurs. b) No if a is not the case. > -Original Message- > From: Vergoz Michael (SYSDOOR) [mailto:[EMAIL PROTECTED]] > Sent: Sunday, March 24, 2002 6:00 PM > To: [EMAIL PROTECTED] > S

Re: [PHP-DEV] Question concerning zend_mem_header

At 02:08 PM 3/23/2002, Stefan Esser wrote: >Hi, > >currently all memory allocated with emalloc has a >zend_mem_header infront of it. This header contains >the backward and forward pointer and the size of this >block. My question is: is there any need for this >linked list on a production system? I

Re: [PHP-DEV] Question concerning zend_mem_header

On Sat, Mar 23, 2002 at 01:23:41PM +0200, Andi Gutmans wrote: > The list is used in order to cleanup any per-request memory leaks (Also in > release mode). It's very much needed. Ahhh i see. So it would not be needed if there aren't any memory leaks anymore. Okay now I understand the use of it.

Re: [PHP-DEV] Question concerning zend_mem_header

The list is used in order to cleanup any per-request memory leaks (Also in release mode). It's very much needed. Andi At 13:08 23/03/2002 +0100, Stefan Esser wrote: >Hi, > >currently all memory allocated with emalloc has a >zend_mem_header infront of it. This header contains >the backward and f

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski wrote: [snip] > What I *really* fail to understand is the gain we get by modifying > exit()'s behavior, as opposed to adding a new function or adding a new > $silent argument. Giving a WFF to several people? Consistency with > other languages that have nothing to do with the Web

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

[EMAIL PROTECTED] writes: > On Thu, 20 Dec 2001, Zeev Suraski wrote: > > > This patch is fine with me, but as it would still print out the error > > message, I think it's not fine with some other people... > > This solves nothing IMO. The problem is that exit (5) displays '5', and > that must be

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski wrote: > At 15:18 20/12/2001, Yasuo Ohgaki wrote: > >> Nobody should complain about BC changes if changes are notified >> early enough and there is alternative way to do the same thing. >> IMHO. (This has been done for some features such as track vars ;) > > > That's a very imprac

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

On Thu, 20 Dec 2001, Zeev Suraski wrote: > This patch is fine with me, but as it would still print out the error > message, I think it's not fine with some other people... This solves nothing IMO. The problem is that exit (5) displays '5', and that must be fixed. Derick > > At 16:29 20/12/2001

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > This patch is fine with me, but as it would still print out the error > message, I think it's not fine with some other people... Well, that'd still be doable with that optional 2nd param I mentioned. But that's someone else's fight. :) 'night > At 16:29 20/12/2001, Lar

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

This patch is fine with me, but as it would still print out the error message, I think it's not fine with some other people... At 16:29 20/12/2001, Lars Torben Wilson wrote: >Zeev Suraski writes: > > At 15:18 20/12/2001, Yasuo Ohgaki wrote: > > >Nobody should complain about BC changes if changes

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > At 15:18 20/12/2001, Yasuo Ohgaki wrote: > >Nobody should complain about BC changes if changes are notified > >early enough and there is alternative way to do the same thing. > >IMHO. (This has been done for some features such as track vars ;) > > That's a very impractical

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

At 15:18 20/12/2001, Yasuo Ohgaki wrote: >Nobody should complain about BC changes if changes are notified >early enough and there is alternative way to do the same thing. >IMHO. (This has been done for some features such as track vars ;) That's a very impractical statement in my opinion... Break

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

On Thu, 20 Dec 2001, benjamin yates wrote: > > > > No offense Benjamin, but you don't understand the conversation. This is > > about running PHP apps in consoles, mail pre-processors and as cron jobs > > where exit status is needed. The only way to get an exit status is with > > exit. > > wow

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

> No offense Benjamin, but you don't understand the conversation. This is > about running PHP apps in consoles, mail pre-processors and as cron jobs > where exit status is needed. The only way to get an exit status is with > exit. wow i just tried it... i never realized that return wasn't se

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Markus Fischer wrote: > Actually, a good idea to keep BC. Its now just a matter if > its really worth to keep BC for exit. I agree with Markus. However, since there are people who want strong compatibility. I think we can wait exit() to return status code, a litle more. As I posted al

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Actually, a good idea to keep BC. Its now just a matter if its really worth to keep BC for exit. On Wed, Dec 19, 2001 at 08:28:19PM +, [EMAIL PROTECTED] wrote : > > Just a thought... > > --- > void exit ( [mixed messag

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

This is what I suggested ages ago. I think this is the correct solution for this one. I don't see mass-breakage, or perhaps even any, caused by this change. The case-insensitivity stuff is completely another matter though. I see very little benefit in 1) breaking thousands of existing scri

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Just a thought... --- void exit ( [mixed message[, int return_value]]) Note: This is not a real function, but a language construct. The exit() function terminates execution of the script. Message must be a string or an int. If

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Markus Fischer writes: > Implictely is more error prone. How so? Can you give an example? > On Wed, Dec 19, 2001 at 04:12:02PM -0800, Lars Torben Wilson wrote : > > Markus Fischer writes: > > > Why not just check the type of the parameter? No conversion > > > needed at all. If its a

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Implictely is more error prone. On Wed, Dec 19, 2001 at 04:12:02PM -0800, Lars Torben Wilson wrote : > Markus Fischer writes: > > Why not just check the type of the parameter? No conversion > > needed at all. If its a long -> exit/no show it. If anything > > else (well, thats to

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Yeah Jani I know. It was more targeted at Torben than the whole audience ;) On Thu, Dec 20, 2001 at 02:16:21AM +0200, Jani Taskinen wrote : > > I have said this all the time..as well as many others. > Try convince Zeev to fix his one script that breaks. > > --Jani > > > On Thu, 20 De

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Markus Fischer writes: > Why not just check the type of the parameter? No conversion > needed at all. If its a long -> exit/no show it. If anything > else (well, thats to argue, but not the point) exit and show. > It would be that easy. And, in that case, I don't care about > t

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

I have said this all the time..as well as many others. Try convince Zeev to fix his one script that breaks. --Jani On Thu, 20 Dec 2001, Markus Fischer wrote: >Why not just check the type of the parameter? No conversion >needed at all. If its a long -> exit/no show it. If anything >

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Why not just check the type of the parameter? No conversion needed at all. If its a long -> exit/no show it. If anything else (well, thats to argue, but not the point) exit and show. It would be that easy. And, in that case, I don't care about the number of broken scripts. Prov

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Vlad Krupin writes: > Please, understand me correctly - I have nothing against exit() working > in the same manner regardless of the type of the argument. I would love > to see that. The problem is that (1) it already accepts a string, and > has been working that way for a long time, so this ca

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

t;[EMAIL PROTECTED]>; "Jani Taskinen" <[EMAIL PROTECTED]>; "PHP >Developers Mailing List" <[EMAIL PROTECTED]> >Sent: Wednesday, December 19, 2001 2:26 PM >Subject: Re: [PHP-DEV] Question: Should exit() print out the integer >exit-status? > > > >

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Please, understand me correctly - I have nothing against exit() working in the same manner regardless of the type of the argument. I would love to see that. The problem is that (1) it already accepts a string, and has been working that way for a long time, so this can't go away, and (2) there

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Vlad Krupin writes: > Lars Torben Wilson wrote: > >Perhaps I have not explained my position. I don't care whether it > >outputs the exit status as a string--as long as it sets the error code > >appropriately *as well*. By appropriately, I mean that 'exit("boo");' > >would a) print 'boo' and b) ret

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

s" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 3:00 PM Subject: Re: [PHP-DEV] Question:

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

<[EMAIL PROTECTED]>; "Vlad Krupin" <[EMAIL PROTECTED]>; "Jani Taskinen" <[EMAIL PROTECTED]>; "PHP Developers Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 2:26 PM Subject: Re: [PHP-DEV] Question: Should exit() print out the

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

>What are you talking about? >1) Setting the exit status of a process is common. >2) Try and right any kind of executer/parser that performs well without >goto's 1 - u can return a value just fine (and silently :) with return, and having multiple exit points i've always thought was bad design

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 2:45 PM Subject: Re: [PHP-DEV] Question: Should exit() print out the integer exit-status? > >Tw

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

>Two reasons: one more... (3) exit is as forbidden as goto so stop using it. -benjamin _ Join the world’s largest e-mail service with MSN Hotmail. http://www.hotmail.com -- PHP Development Mailing List T

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

eev Suraski" <[EMAIL PROTECTED]> >To: "Lars Torben Wilson" <[EMAIL PROTECTED]> >Cc: <[EMAIL PROTECTED]>; "Vlad Krupin" <[EMAIL PROTECTED]>; "Jani Taskinen" ><[EMAIL PROTECTED]>; "PHP Developers Mailing List" ><

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Lars Torben Wilson wrote: >Zeev Suraski writes: > >>At 15:15 19/12/2001, Lars Torben Wilson wrote: >> >>>Zeev Suraski writes: >>> exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something should fit :) >>>Yeah, you could do that. But then, why don't we have a >>>'c_compat

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

it's kinda lame to create a yet another function when exit() already exists. After a while you have die(), exit(), exit_with_status(), silent_exit(), loud_exit(), etc. Maybe not *that* bad, but still exit is just as simple as... well, an exit. Unfortunately, it seems like there will be tons of

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Krupin" <[EMAIL PROTECTED]>; "Jani Taskinen" <[EMAIL PROTECTED]>; >"PHP Developers Mailing List" ><[EMAIL PROTECTED]> >Sent: Wednesday, December 19, 2001 6:59 AM >Subject: Re: [PHP-DEV] Question: Should exit() print out the integer exit-status? &g

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Cc: <[EMAIL PROTECTED]>; "Vlad Krupin" <[EMAIL PROTECTED]>; "Jani Taskinen" <[EMAIL PROTECTED]>; "PHP Developers Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, December 19, 2001 6:59 AM Subject: Re: [PHP-DEV] Question: Should exit() print

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > >Perhaps I have not explained my position. I don't care whether it > >outputs the exit status as a string--as long as it sets the error code > >appropriately *as well*. > > AFAIR, this is the way it works now... > > Zeev If that were the case I would expect the last 'echo

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

At 16:11 19/12/2001, Lars Torben Wilson wrote: >Zeev Suraski writes: > > At 15:15 19/12/2001, Lars Torben Wilson wrote: > > >Zeev Suraski writes: > > > > exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something > > > > should fit :) > > > > > >Yeah, you could do that. But then, why do

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > At 15:15 19/12/2001, Lars Torben Wilson wrote: > >Zeev Suraski writes: > > > exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something > > > should fit :) > > > >Yeah, you could do that. But then, why don't we have a > >'c_compatible_dirname()' now, instead of a

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

At 15:21 19/12/2001, Lars Torben Wilson wrote: >Zeev Suraski writes: > > Even if you repeat it may times, it still wouldn't be a bug. When I wrote > > exit() I intended exit() to print out its argument, regardless of its > > type. It's been behaving like this since PHP 3.0.0 alpha 1, because it

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

At 15:15 19/12/2001, Lars Torben Wilson wrote: >Zeev Suraski writes: > > exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something > > should fit :) > >Yeah, you could do that. But then, why don't we have a >'c_compatible_dirname()' now, instead of a proper dirname() patch >which has b

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > Even if you repeat it may times, it still wouldn't be a bug. When I wrote > exit() I intended exit() to print out its argument, regardless of its > type. It's been behaving like this since PHP 3.0.0 alpha 1, because it was > supposed to behave like that. > The doc team

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something > should fit :) Yeah, you could do that. But then, why don't we have a 'c_compatible_dirname()' now, instead of a proper dirname() patch which has been proven to break BC? Because the new version is Corr

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Even if you repeat it may times, it still wouldn't be a bug. When I wrote exit() I intended exit() to print out its argument, regardless of its type. It's been behaving like this since PHP 3.0.0 alpha 1, because it was supposed to behave like that. The doc team got it wrong, and misdocumented

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Fixing a bug by adding new function that behaves correctly is really not the way to go. Could you please give me nice example what kind of scripts break if the integer is not printed out? --Jani On Wed, 19 Dec 2001, Zeev Suraski wrote: >exit_with_status(), silent_exit(), quiet_exit(), etc. e

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something should fit :) At 14:49 19/12/2001, Lars Torben Wilson wrote: >Zeev Suraski writes: > > At 14:04 19/12/2001, [EMAIL PROTECTED] wrote: > > >Two ways to fix it then, either update the manual, or fix exit(). I go for > > >the las

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Zeev Suraski writes: > At 14:04 19/12/2001, [EMAIL PROTECTED] wrote: > >Two ways to fix it then, either update the manual, or fix exit(). I go for > >the last one then. Ppl who relied on the undocumented feature then, did > >simply the wrong thing. > > Only the documentation was wrong to begin wi

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

At 14:04 19/12/2001, [EMAIL PROTECTED] wrote: >Two ways to fix it then, either update the manual, or fix exit(). I go for >the last one then. Ppl who relied on the undocumented feature then, did >simply the wrong thing. Only the documentation was wrong to begin with! A documentation bug should

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Hello, On Wed, 19 Dec 2001, Lars Torben Wilson wrote: > Vlad Krupin writes: > > lot of reasons), and we don't have this functionality. Hence, at least > > if parameter to exit() is an int, we should just return the error code, > > *not* print it. > > +1 >From a techincal point of view I totally

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Vlad Krupin writes: > Uh? > You probably do not want to see the returned code printed anyway (unless > you are debugging and are lazy to get it in any other way). Chances are > that the codes returned by exit() won't make much sense to anyone but > the one who develops the code, and it's not to

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?

Uh? You probably do not want to see the returned code printed anyway (unless you are debugging and are lazy to get it in any other way). Chances are that the codes returned by exit() won't make much sense to anyone but the one who develops the code, and it's not too difficult to do: echo 1; exi

[PHP-DEV] Re: [PHP] RE: [PHP-DEV] Question about PDF lib.

Try http://groups.yahoo.com/pdflib/ - Original Message - From: "Criegern, Phillipp von (PDV)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, August 27, 2001 6:12 PM Subject: [PHP] RE: [PHP-DEV] Q

RE: [PHP-DEV] Question about PDF lib.

I would suggest looking for a real *Support Forum* or http://www.pdflib.com/ >Do anyone know, how i define the "width", "height" etc. parameters in PDFlib >functions in PHP? Is it in cm, pixels, inch? Or? -- PHP Development Mailing List To unsubscribe, e-mail: [EMAIL PROT

Re: [PHP-DEV] === Question

Check out: http://www.php.net/manual/en/language.operators.comparison.php Also, this list is for the development of the language, not development with the language. You probably want to be at php-general. John On Thu, 19 Jul 2001, Patrick Pease wrote: > What does the === operator do > > and

Re: [PHP-DEV] Question regarding zend's _efree implementation

Hi Zeev, > > Release build assumes no bugs, and thus doesn't try to help you to solve > bugs, and favours performance. In release builds, we don't perform slow > checking of every memory block. If an invalid block was passed - it'd > cause a crash (most probably). In debug builds, which can b

Re: [PHP-DEV] Question regarding zend's _efree implementation

At 16:22 19/07/2001, Holger Zimmermann wrote: >Hi, > >I don't understand the purpose of the following code in zend_alloc.c: > >8< snip > >ZEND_API void _efree(void *ptr ZEND_FILE_LINE_DC ZEND_FILE_LINE_ORIG_DC) >{ > zend_mem_header *p = (zend_mem_header *) ((char *)ptr - > sizeof(zend_mem

Re: [PHP-DEV] Question about form

1) php-dev@ is not a support forum, you should ask this question in php-general@ 2) you shouldn't post to php-general@ before you RTFM, because 3) this is a matter of configuration. set register_globals to On either in php.ini or in httpd.conf, or in .htaccess. At 00:39 14.5. 2001, ÕŕF wrote t

Re: [PHP-DEV] Question

What is doing your extension? -- alex On Mon, 30 Apr 2001, Billy Rose wrote: > I have developed an extension, and am wondering to whom or where I submit it for >review? > > -- > PHP Development Mailing List > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional comm

Re: [PHP-DEV] Question about PEAR DB (mysql)

["Chris Newbill" <[EMAIL PROTECTED]>] > There are two functions query and simpleQuery...query CAN return a DB_Result > object, simpleQuery returns a resource ID. When you call fetchRow() with a > DB_Result, it fails because it expects simply a resource and doesn't check > for a DB_Result object.

Re: [PHP-DEV] Question about socket ext. file descriptors

At 20:11 30/3/2001, [EMAIL PROTECTED] wrote: >I'm currently updating my CVS tree so I can update the current source with >something to make sure that stuff opened here is closed at the end of >it. For this, I'm not too fond of going the resource route for it, simply >because I know people are more

Re: [PHP-DEV] Question about socket ext. file descriptors

On Thu, 29 Mar 2001, Lars Torben Wilson wrote: > Zeev Suraski writes: > > Note that the situation isn't as bad as you thought - it's not that it's > > not using the resource mechanism. It is, if it wasn't, we'd be getting > > loads of complaints from people running out of descriptors very > >

Re: [PHP-DEV] Question about socket ext. file descriptors

Andi Gutmans writes: > At 12:44 PM 3/29/2001 -0800, Lars Torben Wilson wrote: > > >Slightly different topic--is it a problem that call-time pass-by-ref > >is being deprecated but several functions require it in order to work? > > It is possible. Functions which require their argument by referenc

Re: [PHP-DEV] Question about socket ext. file descriptors

At 12:44 PM 3/29/2001 -0800, Lars Torben Wilson wrote: >Slightly different topic--is it a problem that call-time pass-by-ref >is being deprecated but several functions require it in order to work? It is possible. Functions which require their argument by reference should ask for it to be sent b

Re: [PHP-DEV] Question about socket ext. file descriptors

Zeev Suraski writes: > ext/sockets does indeed appear to be broken; It doesn't obey the standard > PHP return value rules at all (errors are negative numbers instead of > false, resource are passed back as-is instead of as resources). > > I was actually looking at the other socket functions, f

Re: [PHP-DEV] Question about socket ext. file descriptors

Zeev Suraski writes: > Note that the situation isn't as bad as you thought - it's not that it's > not using the resource mechanism. It is, if it wasn't, we'd be getting > loads of complaints from people running out of descriptors very > quickly. It just uses old, PHP 3 style resources, of typ

Re: [PHP-DEV] Question about socket ext. file descriptors

ext/sockets does indeed appear to be broken; It doesn't obey the standard PHP return value rules at all (errors are negative numbers instead of false, resource are passed back as-is instead of as resources). I was actually looking at the other socket functions, fsockopen() and friends. They'

Re: [PHP-DEV] Question about socket ext. file descriptors

At 03:47 PM 3/29/2001 +0200, Zeev Suraski wrote: >At 15:41 29/3/2001, Andi Gutmans wrote: >>At 03:35 PM 3/29/2001 +0200, Zeev Suraski wrote: >>>Note that the situation isn't as bad as you thought - it's not that it's >>>not using the resource mechanism. It is, if it wasn't, we'd be getting >>>l

Re: [PHP-DEV] Question about socket ext. file descriptors

At 15:41 29/3/2001, Andi Gutmans wrote: >At 03:35 PM 3/29/2001 +0200, Zeev Suraski wrote: >>Note that the situation isn't as bad as you thought - it's not that it's >>not using the resource mechanism. It is, if it wasn't, we'd be getting >>loads of complaints from people running out of descript

Re: [PHP-DEV] Question about socket ext. file descriptors

At 03:35 PM 3/29/2001 +0200, Zeev Suraski wrote: >Note that the situation isn't as bad as you thought - it's not that it's >not using the resource mechanism. It is, if it wasn't, we'd be getting >loads of complaints from people running out of descriptors very >quickly. It just uses old, PHP 3

Re: [PHP-DEV] Question about socket ext. file descriptors

Note that the situation isn't as bad as you thought - it's not that it's not using the resource mechanism. It is, if it wasn't, we'd be getting loads of complaints from people running out of descriptors very quickly. It just uses old, PHP 3 style resources, of type IS_LONG. They're still de

  1   2   >