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?
> >
>
>
Doesn't seem like this ever got commited.
Can we include this in PHP 5.2.2? It doesn't break existing APIs so I
think it's a good idea.
Andi
> -Original Message-
> From: Wez Furlong [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 10, 2007 6:17 AM
> To: internals@lists.php.net
> Sub
Has anyone tried this or know of anyone who is interested in
implementing this for the Zend Engine?
http://www.php-mag.net/magphpde/magphpde_article/psecom,id,729,nodeid,21.html
I'd settle for faster method dispatching, but JIT would be great. Can
always use the speed. :)
The idea behind PHP
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
Is it still the position of internals that reserved words cannot be used
as method names or class names?
I need this to work
http://www.php.net/unsub.php
Let me know if I have any issues with my patch/thinking here:
Patch seems to be ok. I'll add it.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Has anyone tried this or know of anyone who is interested in implementing
this for the Zend Engine?
actually yes. Gopal ([EMAIL PROTECTED]) made a non-public (but working) prototype
of a JIT PHP version. It was based on libjit (used by dotgnu).
I also have a good background in compilers and I w
No, I am not interested in Phalanger. Thank you. If I wanted to work
with .NET, I would write code using .NET. That won't be happening until
some time in the Fall when I take an "advanced" programming class that
uses the language.
I do think the project is a good one, but I'm looking for somet
Phalanger might be of interest to you.. Compiles PHP to MSIL, which then
compiles to machine code JIT.. Works pretty good really..
http://www.php-compiler.net
http://www.codeplex.com/Phalanger
--
// DvDmanDT
mail: dvdmandt¤telia.com
msn: dvdmandt¤hotmail.com
"Jacob Santos" <[EMAIL PROTECTED]>
Rasmus Lerdorf wrote:
This comes up once or twice a year. The machine code you compile to is
going to end up looking a lot like the current executor since you don't
have strong types to help you optimize anything. You'd still need to
pass the unions around and do runtime type juggling and all t
> The idea behind PHP from day one was that it was an environment for
> wrapping compiled code. Things that are performance critical is written
> in C/C++ and things that aren't are left in the PHP templates. Whether
> you issue an SQL query from PHP or from a compiled C program doesn't
> affect
13 matches
Mail list logo
