Steve Bertrand wrote: > My last question, rephrased to be direct-to-the-point: > > Multi-part howto, or STFU if it's not possible request: > > - create a scalar to contain the memory address of a reference to a > complex data structure > > - store ONLY the memory address using 'Storable' (or some other mechanism) > > - create a cyclical reference within the data structure > > - let everything referring to the data structure go out of scope > > - exploit the fact that Perl GC can't delete this memory allocation > (that is, without 'weaken') > > - re-create the reference to the data structure into a scalar, by > lifting the memory address from disk using 'Storable' (or some other > mechanism) > > - use the original data.
... I plan on playing with this tomorrow. After much searching, it doesn't look like many have tried to store/hide information in memory space in the same way I would like to. I'll take all feedback. If I get it to work, would a tangent like this after coding it up and some peer-review be worthy of a first CPAN entry? Am I getting too excited? If this hasn't been done, and if I get it to work, AND I was able to store the data within *encrypted* memory 'containers', would that make it more useful? Heh, I know it's plausible, as Perl leaks the un-collectible garbage as it is. I'm going to write something that can find, and re-use it. ...and I'm but an engineer, no where near a programmer :) I love Perl. Who knew that a programming language could teach someone so much about so many things, particularly people. The swiss-army-chainsaw. Perl. It's in you. Give it back. Steve
smime.p7s
Description: S/MIME Cryptographic Signature
