Hannes Magnusson wrote:
In the markup I'd write:
<property>mysqli->affected_rows</property>
The problem here, which I didn't realize immediately, is that would
have to be <property>mysql->varname</property>...
Ah, I just realized why the PHP docs use :: eveywhere, even for
non-static variables/methods, escaping the '>' is a pain. Actually I
don't do that in my current document and it still builds fine. Anyway, I
can easily change my XML to use '>' in that case. So not a problem -
although you are right, I (and probably others) will forget from time to
time.
How would the actual documentation of the variable look like?
If we use the current
<classsynopsis>
<ooclass><classname>classname></classname></ooclass>
<fieldsynopsis>
<modifier>static</modifier><modifier>public</modifier>
<type>string</type><varname>foobar</varname>
</fieldsynopsis>
</classsynopsis>
markup, we could have <property>clssname::property</property>
automatically figure out if its a static variable or not, therefore
avoiding the problem of escaping > for normal props..
So, in table-zilla I would write:
<property>classname::property</property>
Then PHD would check the documentation page for that property, see the
static modifier (or not) and do The Right Thing with respect to HTML
generation?
Yes, if we could do that it would be *really* cool.
Thanks,
Tony
