Hello Ralph,
unless someone replaces all the parser and lexer code and the tools around
we developed this is independly of our position impossibly. As doing so is
not possible we don't even have to discuss pros and cons.
best regards
marcus
Thursday, March 8, 2007, 9:48:46 PM, you wrote:
> Is
Stanislav Malyshev wrote:
> No it isn't. I can see no single serious reason why the class must be
> named Case or you have to move to Smalltalk or give up OOP altogether.
> It's a minuscule annoyance at best.
>
>> Anyway, I write so that perhaps, maybe, just maybe, someone might want
>> to see wha
Derick Rethans wrote:
You should prefix your classes in the first place, as per:
http://www.php.net/manual/en/userlandnaming.php
especially point 1 of:
http://www.php.net/manual/en/userlandnaming.rules.php
In the end (After reading the page on smalltalk), I concede. Stanislav
makes some exc
On 08/03/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
Language has its rules. Keywords are one of the rules. I, for example,
am annoyed that in English you have to put this silly "a" and "the"
everywhere, while so many real languages live perfectly well without it.
At least 'a' and 'the' a
On Thu, 8 Mar 2007, Ralph Schindler wrote:
> Stanislav Malyshev wrote:
> > > Is it still the position of internals that reserved words cannot be used
> > > as method names or class names?
> >
> > Why allow it? It would probably require substantial change in the parser,
> > and what for?
> >
>
>
I guess so that we can have a language that will be able to model real
world problems... instead of the real world changing the name of the
problem to fit the language.
Language has its rules. Keywords are one of the rules. I, for example,
am annoyed that in English you have to put this silly
Stanislav Malyshev wrote:
Is it still the position of internals that reserved words cannot be
used as method names or class names?
Why allow it? It would probably require substantial change in the
parser, and what for?
I guess so that we can have a language that will be able to model real
Is it still the position of internals that reserved words cannot be used
as method names or class names?
Why allow it? It would probably require substantial change in the
parser, and what for?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/
--
PHP Intern
