Re^2: getting more from __DATA_

yup, thats pretty like it.

With no disrespect to unwitting pawns or evil masterminds, I was going for more user-friendly than "It is possible that this module may overwrite the source code in files that use it". ;-)

Providing full-on writable handles is neat, but a little heavy - at least for my needs.

time was, I could move my arms like a bird and...

Comment on Re^2: getting more from __DATA__

Replies are listed 'Best First'.
Re^3: getting more from __DATA__ by belg4mit (Prior) on Mar 25, 2005 at 13:05 UTC
Then only open for read? `-- I'm not belgian but I play one on TV. On dit que je parle comme un belge aussi.`	[reply]
Re^4: getting more from __DATA__ by Ctrl-z (Friar) on Mar 25, 2005 at 15:47 UTC
Sure. And what about the backing-up, source-filtering, redirecting of CORE functions and 600 lines of fairly convoluted code? My initial idea was to simply keep large strings out of the source code - tied handles could still be implemented easily: `use Tie::DATA(':foo', sub{ return($_[0], IO::String->new($_[1])); });` [download] time was, I could move my arms like a bird and...	[reply] [d/l]