At 10:20 AM 3/7/2001 -0700, Zak Greant wrote:
>Andi wrote:
>
> > At 04:34 PM 3/7/2001 +0100, Hellekin O. Wolf wrote:
> > >At 17:22 07/03/2001 +0200, Andi Gutmans wrote:
> > >
> > >>>*** What is the difference between error ad errstr ?
>
>bzerror returns an array containing the error string and error number.
Maybe it should be error_info() then?
> > >>>Maybe errstr should be changed to errmsg ? (Did I say that elsewhere ?
>;-)
> > >>>As the file extension is .bz2, maybe the prefix should be bz2_ as well
> > >>>(it's an algorithm, not a version right ?)
>
>bz2_ vs. bz_ ... this is a coin-toss decision. We might run into an
>extension in the future where bz is a good choice for the name, thought I
>feel it is unlikely.
>Personally, I don't *really* care - if it came to a heated discussion and a
>vote, I would go for bz2_... - just so that the no one could tell us "I told
>you so..." in the future. ;)
Why not bzip2_?
> > >>How about error_message or error_string?
> > >
> > >*** Well, errmsg/errstr are everywhere else, be it in PHP or C.
> > >errno would take the lifting also... We would end with function names
>like :
> > >
> > > mysql_error_number()
> > > mysql_error_string()
> > >
> > >Looks great regarding paragraph formatting but wastes lots of keystrokes
>;-)
> >
> > It's always better to write a few extra characters if it makes your code
> > much more readable.
>
>Agreed. We could try to save a bit of space doing /error/err/ or
>/string/str/ or /number/num/. Where do we draw the line on
>length/convenience vs. readability?
It's very hard to draw the line but I tend to be in favor of readability
vs. how many characters you need to type.
Andi
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
