If you would have approached this originally with some respect I think you would have received a better welcome.
As I stated before, I do not reply to this mail list often, as I am busy working on the project full time. And when I saw your attacks on this list it pissed me off, so step back take a breath and think before posting here.
You where given the correct ways to deal with these reserved words, that is the proper way to do it, not by adding a prefix to a method name. Convention over configuration, would say do not use the word list if you know it is reserved. And if you must then this falls outside of above concept, since you are doing something the language would not normally allow anyway.
So this is not a flaw in the dispatcher, I WILL REPEAT AGAIN, it is not a flaw in the design of the dispatcher.
I am on the IRC channel almost 24 hrs a day so stop in there and discuss this.
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
This will be my last post on this thread. Rational discussions simply
don't seem to register in this forum.
To John, thanks for the first clear-headed response. Yes everyone
should do whatever he or she prefers, and not try to convince anyone
else. It was my mistake to think I could discuss a design issue
rationally with fanboys.
To Phpnut, I don't need to prove there is a flaw -- I just call it as
I saw it. A textbook hello-world app does not work when the action
name was called "list", but works with another name "lists".
Whose fault? Perhaps PHP. But since the list of reserved function
names in PHP is dependent on version and installed modules, this
is a poor way to spec out a default behaviour for a framework that
might have to support multiple hosting environment.
Mathematically one counter-example is all it takes to "disprove"
a framework.
I already said I don't want a pissing contest, and you still persist
in doing so. For the record, I said I have 5 years of coding MVC,
not 5 years of coding. I started coding at 13 and I am 43 years
now, so that's 30 years of IT experience beginning with PDP-11.
I won't stop pulling out my dicks when I need to since I do know
what I am talking about.
Originally I have prepared a list of 25 design issues to raise in this
forum, together with my own source code changes. But now it
is clear to me how resistant to criticism the cakesters are, so I
won't be bothering.
For those who are watching on the side and who likes Cake,
I say more power to you. My only interest is to study the
framework and learn about it -- a framework that started with
so much promise and accolade, I was not prepared for the
denial attitudes. To be honest the quality of source code is
not bad, which is why it is a big shame.
This is my last post and the Marie Antoinettes in this forum
can continuing telling people to eat cake, but in my opinion
a little humility and reality check is sorely needed for the cake
community to move ahead. A community that does not
allow critics to exist will never see the truth in the
emperor's new clothes.
Kace
sign off
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
