[UPHPU] @include_once bad?
Daniel C.
dcrookston at gmail.com
Fri Mar 27 11:16:34 MDT 2009
On Fri, Mar 27, 2009 at 11:02 AM, Isaac <keogh24 at gmail.com> wrote:
> If you don't care the error so the include file is useless
That's not necessarily true. I can think of several situations in
which a hypothetical programmer (possibly even myself) may want to
include a file if it's present, but ignore it if it isn't.
> I think it's always very important to know which
> errors are thrown from our application y who part of the code does it.
Yes, if it's an important error. But there are a lot of things that
can go wrong in your computer, and even in your own programs, that you
don't necessarily want to be bothered with.
Anyway, I agree that handling errors well is generally a good thing.
I'm not trying to argue that it's a-okay to use @ instead of doing
things the "proper" way. I'm just curious about what the unintended
side effects of doing things that way are. Consider it a
gedankenversuch.
I am seriously stoked that I just used the word "gedankenversuch" in a sentence.
-Dan
More information about the UPHPU
mailing list