Hi Lukas,
Yep, that's a fair point. But at the same time, PEAR should be
namespacing their classes - and in fact the date class in PEAR is
breaking PEAR's own coding standards in that respect. Why should classes
Steph stay on topic. Date follows current PEAR naming standards just fine
and its not even the topic anyways and taking shots at others is a lame
attempt at giving your arguement more credit.
Actually I thought I was telling the truth, I'm not in the habit of taking
shots at others in that way. Should've fact-checked, didn't.
The topic is what right we (PHP) want to claim for picking "obvious"
identifiers?
I tend to say that we should tell the world to prefix and keep internals
free from a PHP prefix. We already prefix with the extension name (how
does that tie in with the timezone functions in ext/date?).
We agree.
- Steph
Is the only thing we are argueing about the naming btw? Or are there any
technical issues in the new date extension beyond the naming issue?
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
