On Mon, 2 Dec 2002, Gabor Hojtsy wrote:
> > die("foo");
> >
> > vs.
> >
> > trigger_error("foo", E_USER_ERROR);
> >
> > is IMO a complication.
> >
> > > If we leave errors unhandled in examples, that is simple,
> > > but harms the developers. I do think, that using too much
> > > error handlin
On Mon, 2 Dec 2002, Gabor Hojtsy wrote:
> > right, die() works fine for that.
>
> OK, let die() stay there. BUT big notes should be added to the
> die() docs then about unsafe usage (to print out error messages
> to users). So if someone is interested in what die() does, he
> get some explanation
> die("foo");
>
> vs.
>
> trigger_error("foo", E_USER_ERROR);
>
> is IMO a complication.
>
> > If we leave errors unhandled in examples, that is simple,
> > but harms the developers. I do think, that using too much
> > error handling code in examples hurts, but none is not
> > better...
>
> rig
On Mon, 2 Dec 2002, John Coggeshall wrote:
> >
> >Regarding the confusion factor this is a valid point. The
> >error handling docs should clearly describe how the error
> >directives such as display_errors, error_reporting, and
> >log_errors behave and why a blank page my result. And describe
>
>Regarding the confusion factor this is a valid point. The
>error handling docs should clearly describe how the error
>directives such as display_errors, error_reporting, and
>log_errors behave and why a blank page my result. And describe
>ideal production vs. development scenerios.
We're g
-
>> From: "Philip Olson" <[EMAIL PROTECTED]>
>> To: "Gabor Hojtsy" <[EMAIL PROTECTED]>
>> Cc: <[EMAIL PROTECTED]>; "'Sara Golemon'" <[EMAIL PROTECTED]>;
>> <[EMAIL PROTECTED]>
>> Sent: Mo
The examples won't be much longer. And the main focus
won't be trigger_error(), just like how the focus isn't
die(), mysql_error(), 'or', etc. right now.
Regarding the confusion factor this is a valid point. The
error handling docs should clearly describe how the error
directives such as displ
On Mon, 2 Dec 2002, Gabor Hojtsy wrote:
> > > +1 on using trigger_error() in examples, including in mysql_connect. In
> my
> > > experience, it needs more exposure to newbies as it is a far more
> efficient
> > > way of dealing with errors. (And it actually took me a couple years to
> > > discover
> > +1 on using trigger_error() in examples, including in mysql_connect. In
my
> > experience, it needs more exposure to newbies as it is a far more
efficient
> > way of dealing with errors. (And it actually took me a couple years to
> > discover it! :)
>
> I'm -1 on this; don't over complicate exa
quot;Gabor Hojtsy" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>; "'Sara Golemon'" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Monday, December 02, 2002 9:08 AM
> Subject: Re: [PHP-DOC] Re: error handling [was: ugly cvs subject]
>
> Unfortunately, we havn't answered the original concern. Is it proper to
> be dumping detailed error messages in the examples. I say yes. Showing
> the scripter how to do basic debugging until their program is working will
> help them learn faster.
>
> Of course, this does introduce the problem
ECTED]>; "'Sara Golemon'" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> Sent: Monday, December 02, 2002 9:08 AM
> Subject: Re: [PHP-DOC] Re: error handling [was: ugly cvs subject]
>
>
>>
>> I like the idea of trigger_error() and not usi
EMAIL PROTECTED]>
To: "Gabor Hojtsy" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; "'Sara Golemon'" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, December 02, 2002 9:08 AM
Subject: Re: [PHP-DOC] Re: error handling [was: ugly cvs subject]
I like the idea of trigger_error() and not using 'die'. Using
'die' in errors in unsexy and rather limiting but yes I remember
we discussed this before too but it was only part of a huge
discussion regarding the coding_standards RFC. I also feel
'or' for errors is unsexy and limiting. How about
I personally have no problem with using trigger_error instead of
die()... I just have an issue with not using mysql_error() because we
don't want to be flooding with SQL queries, or using some sort of
debugging logic in a reference manual
John
>-Original Message-
>From: Gabor Hojtsy [ma
> IMHO, I think it's the newbies' decision on how and when to use
> functionality available in PHP. I see no problem with the examples in
> the documentation reflecting the use of functionality. There are
> countless examples in the manual currently which don't use what could be
> considered "best
16 matches
Mail list logo
