Re: javadoc, phpdoc, XML, and PEAR

Joey wrote: > Maybe inline is not the right place for what I am thinking of. > Maybe what I am thinking of has no place whatsoever in PHP/PEAR, > but before it gets completely shot down, let me try to pass the > vision along... > > I see aweb interface to PEAR. Since I agree that maybe inline is > not the right way for this to work, let's say the user is asked to > to upload a normal PEAR file, perhaps using current > CODING_STANDARDS, or whatever comes out of all of this... > > The "thingy" (as Larry Wall would say) that handles the file > upload runs the PEAR file through my theoretical XML validating > parser, and generates a companion XML file that can be used as the > "online documentation" for this particular PEAR module. When it > has finished (before it even starts?) building the XML document, > it simply attempts to validate it. > > If the document can be validated (is both well-formed and conforms > to it's DTD), then the PEAR file is added to the PEAR dir, and the > XML file is added to the list of to-be-updated-on-some-website- > somewhere files. Hi Joey, all these ideas are really great, just they won't work. There tools missing we would need to realize such a system. For example you can't validate (compare it with a DTD) an XML document with PHP yet. And I agree with Stig that it's somehow an "extended parser" that belong to the language core. I don't think we have to worry about PEAR module that do not follow the Coding Standards whatever they will finally look like. Be sure a few days after publishing a PEAR module that does not follow the coding rules, there will be discussion on it ;-) Ulf -- Ulf Wendel NetUSE Kommunikationstechnologie GmbH Siemenswall, D-24107 Kiel, Germany Fon: +49 431 386435 00 -- Fax: +49 431 386435 99