RE: [PHP] BUG: require_once() or die(); = fatal error

2003-11-29 Thread Rasmus Lerdorf
TECTED] > > Sent: Wednesday, November 26, 2003 8:55 PM > > To: Daevid Vincent > > Cc: [EMAIL PROTECTED] > > Subject: Re: [PHP] BUG: require_once() or die(); = fatal error > > > > This code doesn't make much sense. By definition, if require > > cannot

Re: [PHP] BUG: require_once() or die(); = fatal error

2003-11-28 Thread Curt Zirzow
* Thus wrote Daevid Vincent ([EMAIL PROTECTED]): > My way, the logic is that the file *is* 'required' (whereas I view 'include' > files as optional), and I want to exit the program with a graceful message > instead of the fatal error (which doesn't really doesn't tell me what the > problem is -- "F

RE: [PHP] BUG: require_once() or die(); = fatal error

2003-11-28 Thread Daevid Vincent
, 2003 8:55 PM > To: Daevid Vincent > Cc: [EMAIL PROTECTED] > Subject: Re: [PHP] BUG: require_once() or die(); = fatal error > > This code doesn't make much sense. By definition, if require > cannot open > a file it throws a fatal error, so you would never hit the "o

Re: [PHP] BUG: require_once() or die(); = fatal error

2003-11-26 Thread Rasmus Lerdorf
This code doesn't make much sense. By definition, if require cannot open a file it throws a fatal error, so you would never hit the "or" case anyway. Hence there is no return code from require and you can't write code like this. If you want to test the return code you need to use 'include' inste