> From: Hartmut Holzgraefe [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 03, 2003 11:48 AM > Pierre-Alain Joye wrote: > > And now I'm wondering why that suddenly becomes ugly and, as pointed > > Sebastion, why PHP should follow different things than 99.9999% of > > others OO langages. > > one reason might bee that we do not have case sensitive function names > so that it is possible to use whatever "CAPSulation" you want > as it already happens today with code using GD or OCI functions > > when reading code that uses e.g. GD you'll see > > - imagecreatefromgif > - imageCreateFromGif > - ImageCreateFromGif > - ImageCreateFromGIF > - ... > > and i see no reason why we should expect this *not* to happen with > code using PEAR classes > > i know that it is to late to change the PEAR coding standards in that > respect but i don't want to see this virus spread ... :-|
Ok I can comment on how things are in PEAR 1) I have seen people complain about our CS .. but studyCaps has rarely been addressed 2) Right now error messages are not case preserving .. even still few people complained (actually I don't remember anyone) 3) I have seen code being posted on the web using PEAR and its all nicely along studyCaps So please realize that studlyCaps is how it is done in the OO world. Its how it is done in the PHP OO world (I don't have statistical data to back this up, but I feel quite safe with my argument here - I would appreciate it if someone would find a way to proof me wring/right). And yes I know that it is no major source of problems because I happen to be heavily involved in one of the largest PHP OO projects that exists. Aside from that yes it will be a major problem for PEAR if objects don't follow studyCaps as this means we will have to either kick our CS or wrap objects instead of just exending them. Regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
