I think the more important issue to me is that symbols are generally operators. * + / , - . The list is endless. Couldn't we have just told users to make their own function _($blah) { return gettext($blah) }? At least it doesn't give a user the impression of a operation as opposed to a function. Really, PHP has made strives in the last year toward a consistent naming convention, and has achieved amazing results. This is just like a slap in the face of hard effort. Regards, Cristopher Daniluk President & CEO email: [EMAIL PROTECTED] direct: 330/530-2373 Digital Services Network, Inc Unleashing Your Potential voice: 800/845-4822 web: http://www.dsnet.net/ -----Original Message----- From: Zeev Suraski [mailto:[EMAIL PROTECTED]] Sent: Friday, September 07, 2001 10:47 PM To: Chuck Hagenbuch Cc: [EMAIL PROTECTED] Subject: Re: [PHP-DEV] Woah At 05:40 08-09-01, Chuck Hagenbuch wrote: >It's the kind of thing that gets used a lot in HTML, where otherwise there >wouldn't be a function call at _all_ - just static text. Replacing gettext() >with _() in this case actually does improve readability, in my opinion. That's exactly what I said - there are several other functions/operators/labels which are used a lot and repeatedly, and we never made any exceptions as far as clarity goes. > > > It's documented, for what it's worth: > > >http://www.php.net/manual/en/function.gettext.php > > > > That's unfortunate. IMHO, it should be phased out. > >Exceptions in php extensions have been made before where the extension >mirrors >the c library exactly, in order to not confuse people familiar with the >library. This is another one of those cases - people familiar with gettext >will >be very confused if _() doesn't work the way they expect it to. You're talking about exceptions in the naming convention? Well, the more accurate way to describe it is that originally, modules tried to copy the low-level API function names 1::1. Only at a later stage we started to strive towards a standard naming convention. Today, when adding new functionality, the low level API function names play no role, and the functions are named using the PHP naming convention. We explicitly decided that in the lengthy discussion about function naming convention that took place half a year ago or so. There was no clear decision as to what to do with the existing functions that are named after their low-level counterparts. At any rate, this is not the kind of exception I was talking about. _ includes 0.0 information about what it does, and unless you know exactly what it does, you're lost. It's not an issue of shortening words, or neglecting to put underscores between words. Not only do you not stand a chance understanding what you're reading without looking at documentation, but you also have absolutely no way of finding what this does if you actually look it up in a manual. Zeev Zeev -- 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]
BEGIN:VCARD VERSION:2.1 N:Daniluk;Cristopher FN:Cristopher Daniluk ORG:Digital Services Network, Inc.;Executive Management TITLE:President & CEO NOTE;ENCODING=QUOTED-PRINTABLE:=0D=0A TEL;WORK;VOICE:(330) 530-2373 TEL;WORK;VOICE:(800) 845-4822 TEL;CELL;VOICE:(330) 219-4819 TEL;WORK;FAX:(208) 723-6782 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;President;89 West Marshall Avenue=0D=0ASuite A;McDonald;Ohio;44437;United S= tates of America LABEL;WORK;ENCODING=QUOTED-PRINTABLE:President=0D=0A89 West Marshall Avenue=0D=0ASuite A=0D=0AMcDonald, Ohio 4443= 7=0D=0AUnited States of America URL;WORK:http://www.dsnet.net/~cris EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20010528T230445Z END:VCARD
-- 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]