Re: improving object oriented / procedural combinations

Folks: On Sun, Apr 25, 2010 at 10:10:28PM -0400, Daniel Convissor wrote: > STATIC > ------ > DocBook: > <classsynopsis> > <ooclass><classname>foo</classname></ooclass> > <fieldsynopsis> > <modifier>public</modifier> > <modifier>static</modifier> > <type>int</type> > <varname>bar</varname> > </fieldsynopsis> > </classsynopsis> ... snip ... > OBJECT > ------ > DocBook: > <classsynopsis> > <ooclass><classname>foo</classname></ooclass> > <fieldsynopsis> > <modifier>public</modifier> > <type>int</type> > <varname>bar</varname> > </fieldsynopsis> > </classsynopsis> I've just updated http://bugs.php.net/bug.php?id=51667 with the following comment: It seems like a good idea to have properties marked up the same way we mark up methods -- put the class name in the method/field element. This is better because it is consistent and shorter. So the proposed rendering engine changes should also allow the following markup to produce the same HTML output as discussed above. DOCBOOK FOR OBJECT ------------------ <fieldsynopsis> <modifier>public</modifier> <type>int</type> <varname>$foo->bar</varname> </fieldsynopsis> DOCBOOK FOR STATIC ------------------ <fieldsynopsis> <modifier>public</modifier> <modifier>static</modifier> <type>int</type> <varname>foo::$bar</varname> </fieldsynopsis> Thanks, --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y data intensive web and database programming http://www.AnalysisAndSolutions.com/ 4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409