Very Interesting

Sayian


require_once('some_file.php') or handleError(1);

function handleError($error) {

  $error = (int) $error;
  $response = '';

  switch($error) {

     case 1:

     $response = 'A Required system file has not been included';

     break;

  }

  return $response;

}

Playing around just testing various things earlier, I found out that you cannot use OR to supply an alternative action to a require once.

The manual states that "Variable Operators" cannot be used on Language Constructs, OR being a Variable Operator this makes sense why it wouldnt work in the example above.

My next question would be, is their a way to be able to call a callback function on a false return of require_once. Or does it even return false?

Im Curious about this now.

vaaaska

file_exists() might be what you are looking for?

Sayian

Thanks for your reply.

No, im not really looking to see if the file exists, im more interested in the behavior that require_once is taking if the require fails.

Assuming you had error_reporting set to off in a production enviorment, and PHP couldnt throw a fatal error, does require_once have a return value such as null, or false?

Thats more of what im trying to find out.

vaaaska

A look at the manual says no.

Sayian

Yeah, I've read the same thing.

There has to be a way to callback a function on a failed require.

Anyone else have any ideas?

Installer

The "require_once...or..." construct won't work simply because as soon as the require fails, the script ends with a fatal error. This is independent of the error_reporting setting and the use of "@". Generally it's better to use "include_once" with a graceful error handling scheme (to avoid your script suddenly quitting). And you should leave error_reporting on and have errors logged rather than displayed (in production).

You can make "include_once...or..." work like this:code=php or handleError();[/code]

Sayian

Thanks for your reply Installer.

I agree that error reporting should be left on in production, and use of the set_error_handler() function should be used to define your own error handling methods which should include logging of errors to a seperate logfile ect.

I was trying to state that if error reporting was off, how does php deal with a defunct language construct? It wouldnt return false? I see that now.

I wonder if PHP5 allows you to throw an exception if the file isnt required.

Im just trying to explore the more inner workings of how php operates, Im not seeking help with this issue, more just seeking discussion.

Thanks for all your points and views, I agree with all of them. Using a simple if statement could contain all this, Im just simply trying to explore other options and see how PHP really deals with the execution of my applications.

Cheers.

Installer

...if error reporting was off...

Then errors aren't reported. That's all.

There has to be a way to callback a function on a failed require.

That's the point I was "discussing". There are ways to deal with errors with include, though, such as the one I "discussed".

Assuming you had error_reporting set to off in a production enviorment, and PHP couldnt throw a fatal error...

I guess I misunderstood you to be saying that having error_reporting off prevents fatal errors. My mistake.

I wonder if PHP5 allows you to throw an exception if the file isnt required.

No. It's a fatal error.

Im not seeking help...

Sorry. I can't help myself.