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.

Then only open for read?

--
I'm not belgian but I play one on TV. On dit que je parle comme un belge aussi.

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...