[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 a win.
You mean like __END__ (or something similar)?
> i have a new use for this, which is getting help text from long
> lived objects (which could be remote). that will not be a
> fatal/final
If you want pod2usage to be able to be told not to exit,
thats trivial to add. I can do it if you like.
> message. i would like the speed to be decent and going to a file (and
> parsing the pod and filtering) is not a good solution IMO.
IMHO that has nothing to do with pod2usage of Pod::Usage or
even Pod::Parser. All you need here is some kind of IO::String
that conforms to the IO::Handle interface. Pod::Parser (and
its subclasses like Pod::Usage) don't insist on being given
a file-handle. If you pass it something that is a tied-handle
or which understands the getline() method, it will use that
just fine and dandy. It does not have to be a file.
(That doesn't mean speed won't still be an issue due
to parsing alone, but that should eliminate the file i/o).
--
Brad Appleton <[EMAIL PROTECTED]> http://www.bradapp.net/
"And miles to go before I sleep." -- Robert Frost
