Re: Re: multiple __DATA__ && __END_

hi jeffa

Thanks for your answer, well I have 2 problems I work for a company with only so little respect to perl that meens that most of CPAN modules arn't installed here include inline. The second problem is that the app I'm writing should be deliver to customers as one binary file with no installation tree what so ever , just download it and use it. so I don't have any file that I can open, so I keep all my text in a .pm __DATA__ segment .

well now I need to write help for the app and I 8 the thought that I have to create about 10 packages for that.

So do you have something else in mind? :)

Michael
no theam yet ,SIR !!

Comment on Re: Re: multiple __DATA__ && __END__

Replies are listed 'Best First'.
Re: Re: Re: multiple __DATA__ && __END__ by diotalevi (Canon) on Nov 20, 2003 at 16:03 UTC
Ah. Without using modules you are restricted to a single __DATA__ per source file. You could store a Storable serialized object there though and that would give you arbitrary complexity. Storable is in the core perl distribution so your customers should have it. Or... if you need to package up a binary you should check out PAR to create the executable. Just keep in mind that you can't prevent (ever) your customers from being able to read your code.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: multiple __DATA__ && __END__
by diotalevi (Canon) on Nov 20, 2003 at 16:03 UTC

Ah. Without using modules you are restricted to a single __DATA__ per source file. You could store a Storable serialized object there though and that would give you arbitrary complexity. Storable is in the core perl distribution so your customers should have it.

Or... if you need to package up a binary you should check out PAR to create the executable. Just keep in mind that you can't prevent (ever) your customers from being able to read your code.

[reply]