Hi Marcus,
Marcus Boerger wrote:
Hello Edin,
it is nice to get you back on track on formalism now that it suits you.
(Hint inheritance rules and bla bla). However we never had any way of
any formalized todo we actually cared for.
I was talking about formalism in the language, not the development
process. What, I should just take the one line patch to allow for
dynamic class variables and commit it without bringing proposal to
internals? And I should do it in time between final RC and the release.
And mask it as some making some class variables? You can do better than
take cheap shots like that Marcus.
I made a proposal, the internals discussed it, it was voted down and
life goes on. I don't like it a bit, but there is nothing I can do about
it, and that's the way we should work here.
I did admire your work ethics and the fact that you have written many
many good proposals for the review in the internals. We do disagree on
how PHP language should look like in the future, but we have never
disagreed on how to proceed.
Therefore, I would really hate that you change your way and let Derick
persuade you that internals is bunch of morons that should not be
listened to and that you should just do and commit what you please. I
know it can be frustrating, but it *is* the right way to do things.
If you look up the todo's most
close to a release of any prior version you'll find out two things. First
todo's have not been met and second most things dones apart from bugfixes
have been done after some mailings or without any public decision what so
ever. That does not mean that i favor it but it is indeed the php way and
we all lived good without having to much formalisms like (you call me a
java guy anyway :-) JSR's. Nonetheless the particular thing in question
has been decided, whether we agree or not, whether we like it or not and
especially regardless of any later outcome. The decision was done and a
pure timing problem made us (from my perspective lucky decision) not do
it in 5.2.
Now we do disagree on this one. Never ever was there a decision to
introduce class Date into PHP. I have challenged Derick to come up with
any sort of proof of that and he failed miserably.
So please let's get the facts straight.
All that nonsense above said. I just would like to see that we agree on
having an official todo thing like lukas' site. Actually we should do
that on php.net somewhere and have a selected group get cvs access right
to that and have changes mailed to internals@ so that people have a place
to discuss any decisions....
Lukas's list does not mention enabling date class. Nor does any place
else. Now tell me why does it take months to commit a trivial patch
(just removing a bunch of ifdefs)? Why wait until the last second before
the RC? If not to avoid having to ask for opinion on the list, thinking
one's smarter and knows better than anybody. It's this kind of arrogant
self-absorbed behavior that upsets me and makes me react so passionately.
Edin
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
