stas at stason
Dec 14, 2004, 3:09 PM
Post #1 of 2
(1387 views)
Permalink
|
|
Re: svn commit: r111875 - /perl/modperl/docs/trunk/src/docs/2.0/user/config/custom.pod
|
|
gozer [at] apache wrote:
> +To retrieve the contents of a custom "container" directive, use the
> +C<L<Apache::Directive>> object's methods
> +C<L<as_hash|Apache::Directive/C_as_hash_>>
> +or C<L<as_string|Apache::Directive/C_as_string_>> :
Even though I made this kind of linking working some time ago, I prefer
not to use it. It relies on a very specific search pattern, which prefers
2.0 docs at the moment, thus resolving any conflicts if there is the same
filename for 1.0, 2.0, etc. But once a new generation of docs is added
(2.2, 3.0) this will stop working. Therefore I think it's beneficial to
use a fully-qualified links everywhere: i.e. :
C<L<Apache::Directive|docs::2.0::api::Apache::Directive>>
and
C<L<as_hash|docs::2.0::api::Apache::Directive/C_as_hash_>>
even though it's uglier and longer to type.
What do you think?
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas [at] stason http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe [at] perl
For additional commands, e-mail: docs-dev-help [at] perl
|
signature.asc
