Re: PHP_Parser - status of Core

From: Date: Thu, 20 May 2004 01:46:01 +0000
Subject: Re: PHP_Parser - status of Core
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-29415@lists.php.net to get a copy of this message
Unfortantly Structure & Tokenizer/Structure.php dont seem compatible with the generated parser I have here. - I've left the defaults in Parser.php point to Tokenizer/Core as it works OK. I think there are a few interdependancies between the two files that need isolating.. I might see if I can get this to work ok with Structure later.. http://devel.akbkhome.com/svn/index.php/BinaryPHP/Parser.jay Regards Alan Greg Beaver wrote:
Hi Alan, Core.jay/Core.php is deprecated, what should be used is Core5.jay/Structure.php and the completely unfinished Extendable.jay/Extendable.php (This should be Extensible to be grammatically correct, but oh well :). It parses PHP4 code perfectly (at least it should - only code containing functions/constants with PPM names or "clone" will bail). Sorry I've been a bit stalled on work on this (and, incidentally, phpDocumentor). Concert schedule is such that I have the time and energy to work on one project at a time, and so that's been PEAR, getting channels coded (which is done - some more regression testing to do). Greg Alan Knowles wrote:
I'm just playing around with PHP_Parser (re: a few CVS commits) From what I guess = Core.jay/Core.php is pretty much depreciated? - I've regenerated a working version so that the docs/examples/test1.php should work. If it's not a problem I'll commit it. The main reason for looking at it is, I'm toying with the BinaryPHP project - plugging in a real parser so it can generate code from a tree, rather than it's crude tokenizer.. - the plugin parser architecture of PHP_Parser makes that quite easy now. Regards Alan
-- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com

« previous php.pear.dev (#29415) next »