>
>
> If your choice is between throwing the error out or handling it
> elegantly, then obviously the latter option is better. But if the
> choice is between
>
> @include_once($file);
>
> or
>
> if (file_exists($file)) {
> include_once($file);
> } //End of code - no error handling intended or desired
>
> what, really, is the difference? I don't see one, except that it took
> me longer to type the second one. (Slowdown when evaluating @ aside -
> I think that's of arguable benefit anyway. The bottleneck in your
> program is likely to be elsewhere.)
>
> Again, I'm only talking about situations where you don't care what the
> error is. Obviously if you care what the error is and want to handle
> it, you've got to use file_exists.
If you don't care the error so the include file is useless, in that case why
should you include it? I think it's always very important to know which
errors are thrown from our application y who part of the code does it.
Regards,
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
