Uri Guttman wrote: > > but how will perl access that text? what perl var get the text in that > =for block? Well, the proposal was more about getting perl code into doco than getting doco into perl. > the proposal for a special here doc notation is possible but > that can be hard for pod to parse unless we restrict the format. Yes, that's an idea. Maybe what's needed is two distinct perl pod processor types, one which passes on the text literally to the compiler, and one which wraps it up like a string literal. The former type: =for pod The subroutine is defined as =for perl-code pod sub foo($\@%) { #... } The latter type: print =for perl-string pod Help is on the way. ; -- John Porter Aus tiefem Traum bin ich erwacht.
- RFC 79 (v1) Code which is both executable and POD. Perl6 RFC Librarian
- Re: RFC 79 (v1) Code which is both executable and... Michael Mathews
- Re: RFC 79 (v1) Code which is both executable... John Porter
- Re: RFC 79 (v1) Code which is both execut... Larry Wall
- Re: RFC 79 (v1) Code which is both ex... John Porter
- Re: RFC 79 (v1) Code which is bo... Uri Guttman
- Re: RFC 79 (v1) Code which i... John Porter
- Re: RFC 79 (v1) Code whi... Uri Guttman
- Re: RFC 79 (v1) Code whi... John Porter
- Re: RFC 79 (v1) Code which is both ex... Chaim Frenkel
- Re: RFC 79 (v1) Code which is both ex... Michael Mathews
- Re: RFC 79 (v1) Code which is both execut... Michael Mathews
- Re: RFC 79 (v1) Code which is both ex... Andy Dougherty
- Re: RFC 79 (v1) Code which is bo... John Porter
- Re: RFC 79 (v1) Code which is both ex... John Porter