Re: [PHPLIB-DEV] Comments in PHPLIB source code From: teo <email protected>
Date: 04/19/00

Hi Adam!
On Wed, 19 Apr 2000, Adam N. Thompson, MCNE, MCSE wrote:

> I was just thinking...
> Ulf/KK (not sure which) made a comment here about the fact that PHP3
> takes a non-zero amount of time to process comments in source code - and
> therefore having gobs and gobs of documentation embedded in the code was
> a bad thing.
also it takes delta > 0 time to parse `static' strings when " are used.

> Obviously, the counter argument is that the code is bloody near
> impossible to decipher without some guidance - witness OOHforms for a
> perfect example.
>
> Can we not ship a small script that, at the user's discretion, strips
> comments out of the source files to speed up PHPLIB? Most of my servers
> are ridiculously overpowered already, and those of us running PHPLIB
> code on 386-class boxes (or really, really busy sites) could run one
> script to speed it up...?
I also though of that and decided not to say a word until I do have a script :-)
But how about something like a `Makefile' setup.

1. the user downloads phplib
2. `make config' customize the dirs/paths
3. `make install' does a comment strip and installs phplib related files
under,say, /usr/local/lib/phplib (if no other path is provided).

I am not as fluent in perl as in python or bash, but anyway I would happily use
any script which does that.

Also, instead of just `stripping' that script should generate some sort of
phplibdoc. Some commenting convensions would help.
Least I am seduced by javadoc, so I'm biased.

Also haven't contributed anything to PHPLIB :-) but I did plan to help
porting it to PHP4.

So what do you guys think about an `install' feature?
Should I even start looking into `javadoc' docs? :-)

thanks, bye
-- teodor
-
PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in
the body, not the subject, of your message.