Mailing List Archive

Re: svn commit: r111875 - /perl/modperl/docs/trunk/src/docs/2.0/user/config/custom.pod
gozer@apache.org 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@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: svn commit: r111875 - /perl/modperl/docs/trunk/src/docs/2.0/user/config/custom.pod [ In reply to ]
Stas Bekman wrote:
> gozer@apache.org 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?

Think you are right. Fixed!

--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/ F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5