OK, I got the script in CVS. Right now, I have accomplished at 90% the
source scan in order to get the protos the way "it sees". While getting
them, it also parses their "validity" and is picking on the suspicious
things. My lest test on php4 checkout was 1095 imperfection ranging from
missing par
I am going to add the docs scanner and the Source Code scanner for
various comparisons.
Should I commit my code to the phpdoc/scripts at this point or later?
Yep. It would be nice to have it in CVS.
Goba
--
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://ww
> > Date: Mon, 3 Feb 2003 17:46:08 + (GMT)
> > From: Philip Olson <[EMAIL PROTECTED]>
> > To: Maxim Maletsky <[EMAIL PROTECTED]>
> > Cc: Friedhelm Betz <[EMAIL PROTECTED]>, Gabor Hojtsy <[EMAIL PROTECTED]>,
> > [EMAIL PROTECTED], [EMAIL
lson <[EMAIL PROTECTED]>
> To: Maxim Maletsky <[EMAIL PROTECTED]>
> Cc: Friedhelm Betz <[EMAIL PROTECTED]>, Gabor Hojtsy <[EMAIL PROTECTED]>,
> [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: [PHP-DOC] proto-skript [was authors]
>
> On Mon, 3 Feb
On Mon, 3 Feb 2003, Maxim Maletsky wrote:
> I don't really want to parse the .c files for protos, that is already
> being done by other scripts(*). What I want to try is to compare the
> documentation data to the actual C code where possible to get some hints
> what is not ideally matching. What ha
I don't really want to parse the .c files for protos, that is already
being done by other scripts(*). What I want to try is to compare the
documentation data to the actual C code where possible to get some hints
what is not ideally matching. What has Ilia done and where is it?
--
Maxim Maletsky
[
;, Gabor Hojtsy <[EMAIL PROTECTED]>,
[EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: [PHP-DOC] proto-skript [was authors]
On Mon, 3 Feb 2003, Maxim Maletsky wrote:
> Thanks, I think this can be useful to me.
>
> Actually, in base of this (and others out there) script(
On Mon, 3 Feb 2003, Maxim Maletsky wrote:
> Thanks, I think this can be useful to me.
>
> Actually, in base of this (and others out there) script(s), I am going
> to attempt creating a script that parses both the C code and the docs
> tree to look for any inconsistencies.
>
> Somewhat like a doc-
Friedhelm Betz wrote:
Take a look at /phpdoc/scripts/xml_proto.php
never tried, but may be a good starting point.
the ext_skel script has functionality to parse protos and generate
from it somewhere hidden in it, too ...
--
Six Offene Systeme GmbH http://www.six.de/
i.A. Hartmut Holzgraef
Thanks, I think this can be useful to me.
Actually, in base of this (and others out there) script(s), I am going
to attempt creating a script that parses both the C code and the docs
tree to look for any inconsistencies.
Somewhat like a doc-bug hunter. The goal in this case will be to
analyze t
> > I have heard some rumors about someone creating a proto check script to
> > check whether the protos in phpdoc reflect the current protos of
> > functions in the php source. Take in account undocumented new
> > parameters, etc. too... I don't think that anybody can get on this to do
> > it manu
11 matches
Mail list logo
