At 22:33 07/03/2001 +0200, Andi Gutmans wrote:
Why not bzip2_?
*** Well, if bzip2_, then gzip_ !
If gz_ then bz_ or bz2_.
Am I wrong or too fastidious ?
hellekin
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
On Thu, 8 Mar 2001, Hellekin O. Wolf wrote:
At 22:33 07/03/2001 +0200, Andi Gutmans wrote:
Why not bzip2_?
*** Well, if bzip2_, then gzip_ !
I'd prefer these. Readable is better than saving 2-3 keystrokes.
--Jani
--
PHP Development Mailing List http://www.php.net/
To unsubscribe, e-mail:
At 02:20 PM 3/8/2001 +0100, Hellekin O. Wolf wrote:
At 22:33 07/03/2001 +0200, Andi Gutmans wrote:
Why not bzip2_?
*** Well, if bzip2_, then gzip_ !
If gz_ then bz_ or bz2_.
Am I wrong or too fastidious ?
No, because gz_ has existed for a long time. If we'd give it a name today
we'd probably
At 23:48 06/03/2001 -0700, Zak Greant wrote:
Andi wrote:
[snip]
Yep. Let's start doing some damage. bzip2 is a very good victim.
bzclose - bz_close
bzcompress - bz_compress
bzdecompress - bz_decompress
bzerrno - bz_errno
bzerror - bz_error
bzerrstr - bz_errstr
bzflush
At 11:07 AM 3/7/2001 +0100, Hellekin O. Wolf wrote:
At 23:48 06/03/2001 -0700, Zak Greant wrote:
Andi wrote:
[snip]
Yep. Let's start doing some damage. bzip2 is a very good victim.
bzclose - bz_close
bzcompress - bz_compress
bzdecompress - bz_decompress
bzerrno - bz_errno
bzerror
At 17:22 07/03/2001 +0200, Andi Gutmans wrote:
*** What is the difference between error ad errstr ?
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 ?)
How
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 ?
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
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 errstr should be changed to errmsg ? (Did I say
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.
Andi Gutmans wrote:
bzerror returns an array containing the error string and error number.
Maybe it should be error_info() then?
nerk? error seems sufficient to me...
Maybe errstr should be changed to errmsg ? (Did I say that
elsewhere ?
;-)
As the file extension is .bz2, maybe the
Hello Everyone,
Is anyone bold enough to comment on the suggested names besides Phil? I know
that you all have opinions...
Don't make me use humor again. This time, I'll make fun of people by name
(and by reference - I've got to be thorough) grinwink
--zak
--
PHP Development Mailing List
Can you please resend :)
Andi
At 11:02 AM 3/6/2001 -0700, Zak Greant wrote:
Hello Everyone,
Is anyone bold enough to comment on the suggested names besides Phil? I know
that you all have opinions...
Don't make me use humor again. This time, I'll make fun of people by name
(and by reference -
Andi wrote:
Can you please resend :)
Your wish is my command! :)
--zak
This message is a duplicate of a post on Saturday, March 03, 2001:
Andi wrote:
We should probably just make a list of all the effected functions and see
which ones we start fixing and which not.
Based on Andi's
For starters (too long of a list and not that easy to decide on each and
everyone of them) I'll give you what I can think of :)
I started making a list of what looks OK to me but it became too long so
I'll just mention what isn't OK in my opinion. Consider me pretty much pro
all the other
Well, let's start fire =8)
I think the compression extensions should follow the same standard.
The one you proposed for bzip2 should be applied to gzip functions as well.
readgzfile - gz_readfile (or gzreadfile), at least to keep functions names
in alphabetical order ;-)
Also, I know the gd
On Tue, 6 Mar 2001, Andi Gutmans wrote:
6) I think create_function() is OK. There was a long thread which decided
upon this name. Same for function_exists().
Can't we call it lambda()? =)
Derick Rethans
-
PHP:
- Original Message -
From: "Zak Greant" [EMAIL PROTECTED]
To: "Andi Gutmans" [EMAIL PROTECTED]
Cc: "PHP Development" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, March 06, 2001 1:35 PM
Subject: [PHP-DEV] Re: [PHP-QA] ctype function (re?)naming
HOW wrote:
Well, let's start fire =8)
I think the compression extensions should follow the same standard.
The one you proposed for bzip2 should be applied to gzip functions as
well.
readgzfile - gz_readfile (or gzreadfile), at least to keep functions
names
in alphabetical order ;-)
I
Sterling wrote:
Overall I think this is very good. I have a few problems with it (all
prefixed with a large IMHO :)...
:)
array_multisort - array_multi_sort
nah, doesn't sound as good as array_multisort, multisort should be a
single
word... Its a type of sorting method, shouldn't be two
Overall I think this is very good. I have a few problems with it (all
prefixed with a large IMHO :)...
agreeing in anything sterling mentioned, except and in addition this:
GETTEXT
bindtextdomain
dcgettext
dgettext
gettext
textdomain
is there any reason not to change them?
IISFUNC
Waldschrott wrote:
Overall I think this is very good. I have a few problems with it (all
prefixed with a large IMHO :)...
agreeing in anything sterling mentioned, except and in addition this:
GETTEXT
bindtextdomain
dcgettext
dgettext
gettext
textdomain
is there any reason
At 05:05 PM 3/6/2001 -0700, Zak Greant wrote:
Andi wrote:
[snip]
I don't have any complaints or helpful comments on what was above this.
3) Why change the imap ones to not include underscores? Looks as if you
did
the reverse here :)
Removing the underscores was the choice that meant the
At 05:26 PM 3/6/2001 -0700, Zak Greant wrote:
Derick Rethans wrote:
[snip]
6) I think create_function() is OK. There was a long thread which
decided
upon this name. Same for function_exists().
Can't we call it lambda()? =)
That would make a sensible alias for it. :)
Nah no aliasing to
At 05:43 PM 3/6/2001 -0700, Zak Greant wrote:
Sterling wrote:
Overall I think this is very good. I have a few problems with it (all
prefixed with a large IMHO :)...
:)
array_multisort - array_multi_sort
nah, doesn't sound as good as array_multisort, multisort should be a
single
Andi wrote:
At 05:05 PM 3/6/2001 -0700, Zak Greant wrote:
Andi wrote:
[snip]
I don't have any complaints or helpful comments on what was above this.
3) Why change the imap ones to not include underscores? Looks as if
you
did
the reverse here :)
Removing the underscores was the
At 11:28 PM 3/6/2001 -0700, Zak Greant wrote:
Andi wrote:
At 05:05 PM 3/6/2001 -0700, Zak Greant wrote:
Andi wrote:
[snip]
I don't have any complaints or helpful comments on what was above this.
3) Why change the imap ones to not include underscores? Looks as if
you
did
Andi wrote:
[snip]
Yep. Let's start doing some damage. bzip2 is a very good victim.
bzclose - bz_close
bzcompress - bz_compress
bzdecompress - bz_decompress
bzerrno - bz_errno
bzerror - bz_error
bzerrstr - bz_errstr
bzflush - bz_flush
bzopen - bz_open
bzread
Prodigious work Zak - well done. This certainly represents a useful initial
tidy up. It doesn't break anything and cures many of the 'bad offenders'.
In looking through the unchanged function names, the one that screamed 'I am
wrong' most loudly was 'velocis_off_autocommit' which appears to set
Phil wrote:
Prodigious work Zak - well done. This certainly represents a useful
initial tidy up. It doesn't break anything and cures many of the
'bad offenders'.
Thanks Phil - I expect that closer examination will reveal how sloppy it is!
:)
In looking through the unchanged function names,
Andi wrote:
We should probably just make a list of all the effected functions and see
which ones we start fixing and which not.
Based on Andi's suggestion of a moderate approach, I feel that the goal of
the renaming is to fix the most obvious mistakes with the least amount of
change. If an
On Mon, 26 Feb 2001, Hartmut Holzgraefe wrote:
RFC: what should their names be in 4.0.5?
( ) stay with ctype_alpha() ...
( ) switch to ctype_isalpha() ...
( ) switch to ctype_isalpha() ... and have ctype_alpha() aliases
( ) switch to ctype_is_alpha() ...
(X) switch to
RFC: what should their names be in 4.0.5?
( ) stay with ctype_alpha() ...
( ) switch to ctype_isalpha() ...
( ) switch to ctype_isalpha() ... and have ctype_alpha() aliases
(X) switch to ctype_is_alpha() ...
( ) switch to ctype_is_alpha() ... and have [Undocumentated]
32 matches
Mail list logo
