Re: [PHP-DEV] javadoc, phpdoc, XML, and PEAR From: Stig Bakken (ssb <email protected>)
Date: 05/16/00

Joey wrote:
>
> >
> >The idea you toss in about looking for deprecated functions is cool.
> >The functionality you are suggesting (not only checking for specific
> >functions, but tracing the output as well) is called static code
> >analysis. I'm not a compiler guru, but I have a feeling writing one is
> >about the same amount of work as writing an optimizing parser/compiler.
> >:-)
> >
>
> Hmm...I was simply thinking of something along the lines of
> "tidy". I, also, am not a compiler guru, but I note that it only
> takes 24 files for tidy, and this warns of things like using
> the font tag, which is a deprecated HTML tag.

Looking for deprecated usage in markup and code is very different.
Doing markup is easy, looking for deprecated functions is easy, looking
for deprecated use of return values from functions is _hard_. (...he
said, hoping that someone steps up saying "naah, I can do that in a
week" ;-)

 - Stig 

-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: php-dev-unsubscribe <email protected>
For additional commands, e-mail: php-dev-help <email protected>
To contact the list administrators, e-mail: php-list-admin <email protected>