[re Pod::Usage and pod2usage]
> i think reading the file may have issues like finding it.
Not a problem. You can tell pod2usage where to look or give
it a search path
> have to read that file for stuff that was in the source. so some better
> syntax to make that accessible to the code seems like
> "JV" == Johan Vromans <[EMAIL PROTECTED]> writes:
JV> Uri Guttman <[EMAIL PROTECTED]> writes:
>> i think reading the file may have issues like finding it. or doc strings
>> for each sub vs. parsing that out of the whole pod. i just bothers me to
>> have to read that file for stuff
Uri Guttman <[EMAIL PROTECTED]> writes:
> MP> pod2usage is the call I THINK you are refering to. Who cares if it is
> MP> slow? I'll bet that if you are writting to the screen or a file, THAT's
> MP> the slow part, not traipsing through the file parsing for POD. It might
> MP> make an int
Uri Guttman <[EMAIL PROTECTED]> writes:
> some people have mentioned help strings as special parts of a sub
> declaration like gnu lisp has. this could be more support for that type
> of thing. but i don't want it to be too strange.
Hmm...
sub foo ($$;@) :lvalue
"Documentation string h
On Tue, 08 Aug 2000 20:49:38 -0400, Matthew Persico wrote:
>pod2usage is the call I THINK you are refering to. Who cares if it is
>slow?
YA extension to perldoc?
--
Bart.
> "MP" == Matthew Persico <[EMAIL PROTECTED]> writes:
>> there are 2 ways i know how to do it now and both suck in different
>> ways. the first is to read the pod from the source file for the module
>> you are in. it think the pod2XXX parser author has a module which does
>> this. of
Uri Guttman wrote:
>
> here's an interesting request. i want perl code to have decent access to
> some or all of the pod associated with that code.
>
> so, why do we need a way to get at pod (or other doc strings) in the
> code? one reason to have it comes from my work on stem. i want a remote
>
