her those markers or C<=for test>/C<=begin test> for the
setup code that shouldn't be in the documentation.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
ot necessarily the output format).
I'm still pretty unconvinced that such a module can actually manage to do
anything really useful, based on my experience writing translators. I
know I need to expand on that feeling a bit more; I'll try to do that as
soon as I can find some time to do s
rmat.
Pod::Parser already comes close enough to this that I think the additional
marginal utility would be pretty small and not worth the speed hit from
the extra level of method call indirection.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
ld be able to define new members
> for each command they add: =bar needs a sub cmd_bar() {}.
Again, very little code needed for this.
I am interested in continuting to maintain the POD translators that I
wrote, and if this is the way that we want the wind to shift, I'll try to
help. But so far, again, I'm unenthused.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
uot;control"?
Kind of, but not formally. Right now, =item controls the next paragraph
only insofar as is necessary to do the formatting the translator needs to
do, which means not at all in Pod::Man but to some degree in Pod::Text.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
umented?
It's not, really. The problem is that a lot of the details are subjective
and tweaked to give the best output according to what people use POD to
intend. I keep meaning to write up some documentation of all of this but
as of yet haven't found the time.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Tim Jenness <[EMAIL PROTECTED]> writes:
> On 4 Aug 2000, Russ Allbery wrote:
>> [I'd love to know how the POD translator is supposed to do that.]
> It wouldn't. It would get one of those Pod::Hyperlink objects (part of
> Pod::ParseUtils) and do what it wants
st to get the C<=also> functionality (or whatever syntax), and for the
> sake of factoring out common code (which I would never bother to do if
> it weren't for doing the C<=also> stuff in the first place. "If it
> ain't broke...").
Understood... let me comment on that separately in your other message.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
g associated with some keyword
that special translators use. Viewed in that light, I can see the utility
(although I'd like to hammer down the definition; we've suffered a lot
from the fact that the way the argument to =for/=begin is treated is
rather ill-defined); it's worth considering whether =also is the best name
for it.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
der foo(1) in Pod::Man, for example.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
hyperlink support and those databases, but I think
putting it between the POD and the translator is a bad idea. Why not
provide it as utility functions for the translator to call instead?
Way too much OO going on here for my taste.
> This leaves us - AFAICS - with the speed discussion. I agree that for
> perldoc and pod2text one does not want to wait for any OO exercises.
(Note that perldoc by default uses pod2man, not pod2text.)
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
happy
to put such a pre-amble on all of my tests in my module distribution if it
didn't interfere with people running make test from the module
distribution. I just don't know what it should look like.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
arting with /afs, there are probably enough of us doing AFS
installs of Perl that it would end up being tested. (Yes, I know, patches
welcome. :))
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
eone would generalize the Pod::Parser test framework so
that it would work for Pod::Man as well and the other Pod::Text modules;
it already knows how to test Pod::Text. I'd happily include any such port
into podlators.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
e there also.
I'm currently working on Pod::Man, Pod::Text*, and Pod::ParseLink.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
Michael G Schwern <[EMAIL PROTECTED]> writes:
> I didn't know it was NCR UNIX. Wow. I've never even heard of that. I
> thought we were up against something fairly sane.
I've heard of it. I believe it's a fairly stock SVr4.
--
Russ Allbery ([EMA
16 matches
Mail list logo
