> right now, we have configuration directives that are extension-specific
> in one of two places -- in the extension documentation (like for
> sessions), or in the configuration section (like for mysql). i think it
> would make sense to move the extension-specific stuff into the extension
> documentation. any objections?
>
> (in fact, i'd love to do this for compile-time configuration, too. i
> don't think the long 'list of all configure --options' section is all
> that easy to use. an up-to-date listing of all of the options is easy
> enough to get from the command line.)
The huge list of configure options is IMHO not viewable and not
manageable. So separating the options, and putting them into
the right places (ie. opening a "Configuration options for MySQL"
section side by side with the mysql refpages would be more
appropriate). And so for other refpages...
> and, just because i have the data at hand, here's the list of the top
> ten most-commented manual pages. i'm going to start working on rewriting
> these pages to address all of the notes.
>
> 113 | function.header
> 104 | function.mail
> 91 | ref.session
> 87 | function.setcookie
> 76 | function.date
> 76 | features.file-upload
> 68 | language.oop
> 63 | install.windows
> 61 | function.ereg
> 53 | function.ereg-replace
> 51 | function.include
> 49 | function.session-start
This would be a great work to do... Maybe I can help out in the
Windows section... But not for the coming days, as I'll be at
Frankfurt at PHPConf, so I can't help...
Goba
