RE: [PEAR-DEV] Re: [Zend Engine 2] Constants (was: delete construct)

I would also welcome case sensitivity. But I guess most of the people on this list would as we are not the casual programmer that might get tripped by this Then again I do not actually plan to use case sensitivity to differentiate my functions. Also to the Pear conventions: I think the basic idea is ok but the conventions go too for in some cases This is definitely turning people off. Best regards, Lukas Smith smith@dybnet.de _______________________________ DybNet Internet Solutions GbR Alt Moabit 89 10559 Berlin Germany Tel. : +49 30 83 22 50 00 Fax : +49 30 83 22 50 07 www.dybnet.de info@dybnet.de _______________________________ > -----Original Message----- > From: mlemos@toole.uol.com.br [mailto:mlemos@toole.uol.com.br] On Behalf > Of Manuel Lemos > Sent: Wednesday, December 19, 2001 7:10 PM > To: Jon Parise > Cc: Jason Greene; Thomas Hurst; engine2@lists.zend.com; pear- > dev@lists.php.net > Subject: [PEAR-DEV] Re: [Zend Engine 2] Constants (was: delete construct) > > Hello, > > Jon Parise wrote: > > > > On Wed, Dec 19, 2001 at 09:40:19AM -0600, Jason Greene wrote: > > > > > I really would like to see php become case sensitive, the > > > problem is that that kind of change would break alot of > > > backwards compatibility. It also does slightly increase the > > > difficulty level of the language. If I had to vote on it, I > > > would say that I am for it, but I can tell you that you would > > > get alot of negative feedback on that for the above mentioned > > > reasons > > > > We have enough problems on the PEAR lists with developers not > > wanting to conform to any given naming convention. That appears > > to indicate that they'd prefer to code things in their own way. > > It is not developers do not want to conform to ANY given naming > conventions, but rather often that they already follow consistently > conventions that are different than those that you borrowed from Horde > to PEAR. > > I already suggested that instead of pushing your conventions that are > not necessarily the only ones that are right, PEAR rules could be > changed in such way the code in PEAR should preserve the conventions of > the original contributor, which could default to the current PEAR rules > if the original developer does not follow any conventions consistently. > > I think that if you become this open minded, you will see more people > willing to contribute to PEAR in the future. The ball is in your court. > > > > I agree with you when it comes to writing _you own code_, but I > > often see things like this: > > > > mysql_query() > > mysql_Query() > > MySQL_query() > > > > ... so I think it would just make things confusing for end-users. > > > > I agree, however, that it would be a good thing to add to the > > language. I'm just not sure it's a good idea to add it. > > > > Constants should be case-sensitive, though, but I think that's > > already been done. > > I don't see a problem is making case sensitiveness an PHP option that it > is up to each developer to enable or not, maybe in php.ini or with > ini_set() or something like that. It would work similarly to use strict; > of Perl that in the case requires variables to be declared. > > Regards, > Manuel Lemos > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > For additional commands, e-mail: pear-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net