Somebody has deleted all templates in xsl/ and no history left. When I
was writing my previous letter they were there. That bloody CVS is no
more useful than plain FTP if I constantly need to use mail list and
archives to get the idea of "what the heck is going on"? FTP at least
works through my web proxy.
The problem with CVS is that those who was capable to setup it are fed
up with the process and do not want to dip into another VCS and those
who failed are just not here. If not the precious time I could argue
on the topic endlessly, so I better leave a proposal to discuss.
http://doc.php.net/rfc/rfc-proposal-show.php?id=8
As for actual subject of this letter - before I could help with new
xCHM development it is a good idea to try to reduce waste of precious
time to a minimum. I can only cope up with phpdoc/ development if I
get _fast_ and _convenient_ access to sources and tools discussions.
So that the next time I feel desire for some free-time coding I won't
have to waste it completely to read irrelevant stuff in phpdoc/
archives, find a free SSH hosting, setup SSH tunnel to bypass my web
proxy in order to make CVS working. The only idea of the process kills
all desire to participate - I'd better do some other useful things
instead - like anybody else in my situation.
P.S. About the bloody tools list - I am writing another proposal at
the moment so it should be available under
http://doc.php.net/rfc/rfc-proposal-show.php?id=9 in a few minutes if
everything goes as expected.
On 3/17/07, Philip Olson <[EMAIL PROTECTED]> wrote:
> What is wrong with the scripts and generated content?
Some output is incorrect, see below:
> quickref.txt is generated from manual.xml via XSLT and I am pretty
> sure it doesn't contain any errors.
It contains all the Zend API stuff including macros, so all these end
up in funcindex.xml as well. Maybe have the script take into account
the INTERNALS_EXCL_* inside manual.xml
> genfunclist.php and hence funclist.txt is much better than awk scripts
> provided before - you may annotate makefile and extract them from
> attic to compare as it said in commit comments for the script.
This one isn't that bad, in fact, it might be perfectly valid output.
Please I'd rather not touch the awk script or even look at it...
we'll never never ever go back to those! But over time bugs have been
introduced mainly due to changes made elsewhere in both php src and
php doc. At least I assume this is why some bugs now exist in these
scripts.
> genfuncsummary.php - perhaps I was running out of time to finish
> testing of this one, but I've added it to makefile, so it should be
> better as well. In any case - awk scripts are still present and it
> will not take too much time to annotate makefile and find command line
> used to launch them to see which result is better
Examples from the output:
avoid php_snmpv3(INTERNAL_FUNCTION_PARAMETERS, int st)
* * Generic SNMPv3 object fetcher * From here is passed on ...
void DOMAttr::__construct(string name, [string value]) U */
PHP_METHOD(domattr, __construct) { zval *id; xmlAttrPtr ...
apache_request_basic_auth_pw() */
PHP_FUNCTION(apache_request_basic_auth_pw) { zval * ....
Other Notes:
At some point we need to come up with one solid method for sifting
through php-src because currently we do it so many ways... See also
check-references.php and functable.php
Regards,
Philip
--
--anatoly t.
