Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical

Re: Mixing documentation and data

by tmharish (Friar)
on Feb 01, 2013 at 07:07 UTC ( #1016463=note: print w/replies, xml ) Need Help??

in reply to Mixing documentation and data

Everything after __DATA__ is considered data.

Have you tried this:
package FOO::Messages; sub foo{} =head1 __DATA__ This is the data stuff here. =cut 1; __DATA__ data stuff here.

Replies are listed 'Best First'.
Re^2: Mixing documentation and data
by Anonymous Monk on Feb 01, 2013 at 07:26 UTC
    So you want to duplicate the data?
        But you can have pod after __DATA__
Re^2: Mixing documentation and data
by KurtZ (Pilgrim) on Feb 02, 2013 at 10:00 UTC

    In software engineering, Don't Repeat Yourself (DRY) is a principle of software development aimed at reducing repetition of information of all kinds!

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1016463]
[Corion]: Heh. After a bit of hacking, the Pg parser now "just" fails because some Win32 functions of Postgres aren't included in the lib I'm hacking up. Progress, I guess :)

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (5)
As of 2018-03-23 21:13 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (296 votes). Check out past polls.