in reply to pod6 --- code+pod suggestion

Based on Synopsis 26, I'd say what you're asking for will already be possible. (Note that it's called Perldoc, not pod6.)

Synopsis 2 states:

any POD stream in the current file can be accessed via a filehandle, named as %=POD{'DATA'} and such. Alternately, you can treat a pod stream as a scalar via $=DATA or as an array via @=DATA.

which is pretty much exactly what I suggested in RFC 79, but since that isn't listed in Apocalypse 2, I don't know if it was ignored or if the idea was simply considered too obvious to require citation, or what.

We're building the house of the future together.

Replies are listed 'Best First'.
Re^2: pod6 --- code+pod suggestion
by Eimi Metamorphoumai (Deacon) on Dec 19, 2006 at 15:59 UTC
    Though that's useful, that doesn't seem to be the same thing. The OP was asking for a way to have code embedded in the docs, and still be treated as code. What you're talking about seems to be a way to access the docs as data from within code. Now, you might be able to get there from here (read the docs, parse out the code, and run eval), but at the very best that's ugly.
[reply]

      Oh, yeah, you're right.

      In that case I think it's safe to say that RFC 79 was implicitly rejected, if not outright ignored.

      We're building the house of the future together.
[reply]

In Section Meditations