Re: [ANNOUNCEMENT] phpDocumentor 1.2.0rc1 (beta) Released

Hi Alan, This is definitely the direction we want to move for 2.0. Tal has been talking about working in C to write an extension to take care of some of the memory and time-intensive elements. We haven't had much trouble with the parser eating up memory, it's been the linking and conversion to output that has really been the killer. Large projects currently require a ton of information to guarantee that linking will work, and it all needs to be in memory at once, otherwise the speed of the disk would determine parsing speed, and we'd be looking at days to parse large projects. This is with the current design, mind you, so we are looking for bright ideas from bright people like you :). The current parser is slightly more complex due to the parsing of docblock templates. I like the idea of only processing docblocks that belong to an element, and requiring that they immediately precede the element, and of generating a parser from the same rules that PHP uses. I need to read more on jay/bison before I can give you an intelligent response, so I'll do that. Greg Alan Knowles wrote:

Greg, Whats the current state of your parser - I've not looked that closely at the code recently. The reason I was asking was I wanted to write a small gtk app to navigate and browse classes and was looking at a way to parse the classes into a datastructure - the thinking being that a small application could just parse a PHP file into a simple array and serialize it. into a file: eg. DB/DataObjects.php would have a serialized description as DB/DataObjects.php.serial you could then just do date checking on the 2 files to see if it needs re-parsing. Since parsing is generally the memory killer for these apps it should solve alot of problems, and In theory could be a small simple shared component of all 'PHP code analysis tools'..... anyway - the example code is at (The jay/bison base file) http://www.akbkhome.com:81/svn/akpear/PHP_CodeDoc/CodeDoc/Parser2.jay the generated php class http://www.akbkhome.com:81/svn/akpear/PHP_CodeDoc/CodeDoc/Parser2.php (you can modify the last line to play with it parsing other files..) how to use phpJay http://www.akbkhome.com:81/svn/akpear/PHP_CodeDoc/CodeDoc/test_jay.sh the current print_r version of the output. http://www.akbkhome.com:81/svn/akpear/PHP_CodeDoc/CodeDoc/Parser2_example_output.txt The intention is not for this to get involved in phpdoc comment parsing. - just to provide a generic file parser for PHP. (as in small reusable component) let me know if you have any thoughts.. Regards Alan Beaver wrote:

Hi, pear.php.net crapped out after 30 seconds in PEAR.php (don't know what the problem is), so there was no release announcement sent. phpDocumentor 1.2.0rc1 has been released, and is available for immediate installation through pear.php.net This release fixes nearly 50 bugs, and has all major features for the 1.2.0 release cycle implemented. The peardoc2 converter should be fully functional, source highlighting has been greatly enhanced, and all of the HTML:frames templates have been spiffed up by Marco von Ballmoos, our new favorite developer. Contrary to the release notes, there are a few open bugs in this release (oops), and there will possibly be more discovered. If you find any, please open a new bug at the sourceforge project page. to install phpDocumentor, use: pear install PhpDocumentor NOT pear install PHPDoc Regards Greg Beaver -- phpDocumentor http://www.phpdoc.org