Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_execute.c zend_language_parser.y zend_language_scanner.l zend_operators.c
zend_operators.h
| From: | Andrei Zmievski | Date: | Tue, 30 Jul 2002 06:43:57 +0000 |
| Subject: | Re: [ZEND-ENGINE-CVS] cvs: ZendEngine2 / zend_compile.c zend_compile.h zend_execute.c zend_language_parser.y zend_language_scanner.l zend_operators.c zend_operators.h |
||
| References: | 1 2 | Groups: | php.zend-engine.cvs |
| Request: | Send a blank email to php-zend-engine-cvs+get-284@lists.php.net to get a copy of this message | ||
On Tue, 30 Jul 2002, Andi Gutmans wrote:
> Hey,
>
> Can't you share the patch before you just go ahead and just commit it? I
> still have the same issue I used to have.
Hey, the patch has been available for a long while now. :-)
> I think using the cast operators for the types is pretty ugly. The code
> looks something like:
> $foo is (int)
> I we should only support classes and not support basic types? We have the
> non-OOP function for those. This is really an OOP operator.
Don't you think we should have a unified way of testing for variable's
type/class? I understand that we don't have type unification yet, but
having a separate function for each basic type is kind of ugly too.
> BTW: I think it's a good idea to not declare is_type_expr in the parser but
> to use catch_or_import_class_entry and change its name to something which
> fits both. I don't like declaring the same rules more than once if I can
> help it. This rule will probably also be useful for future things.
Yeah, I think it's a good idea too. Should we call it "class_entry_ref"
or something like that?
-Andrei http://www.gravitonic.com/
* 2 + 2 = 5 for extremely large values of 2. *