view release on metacpan or  search on metacpan

README  view on Meta::CPAN

                #poe@magnet

                <buu> Apocalypse: Hey, while you're at it, can you make it so all file access operators in perl operate on virtual directories?
                <Apocalypse> buu: hm you mean overriding readdir(), stat()?
                <buu> Yes.
                <Apocalypse> as of now you would have to explicitly use the filesys::virtual::async::inmemory object and do operations on it -> $fsv->readdir(), $fsv->open(), etc
                <buu> But I don't want to!
                <buu> =]
                <Apocalypse> but that would be a fun side project to try and figure out how to hijack CORE:: stuff
                <buu> Yes!
                <Apocalypse> hmm you could locally scope the hijack, pass a $fsv object to the module init, and have it transparently replace all file operations in the scope with $fsv->method calls
                <Apocalypse> why would you want it? pure laziness? haha
                <buu> Apocalypse: For buubot..
                <Apocalypse> mmm for now you can just use fsv::inmemory until somebody with enough wizardry does the overrides :)
                <Apocalypse> I'll file that away in my TODO and see if I will return to it someday hah
                <buu> Exccelent.

SEE ALSO
    Filesys::Virtual::Async

SUPPORT

lib/Filesys/Virtual/Async/inMemory.pm  view on Meta::CPAN

	#poe@magnet

	<buu> Apocalypse: Hey, while you're at it, can you make it so all file access operators in perl operate on virtual directories?
	<Apocalypse> buu: hm you mean overriding readdir(), stat()?
	<buu> Yes.
	<Apocalypse> as of now you would have to explicitly use the filesys::virtual::async::inmemory object and do operations on it -> $fsv->readdir(), $fsv->open(), etc
	<buu> But I don't want to!
	<buu> =]
	<Apocalypse> but that would be a fun side project to try and figure out how to hijack CORE:: stuff
	<buu> Yes!
	<Apocalypse> hmm you could locally scope the hijack, pass a $fsv object to the module init, and have it transparently replace all file operations in the scope with $fsv->method calls
	<Apocalypse> why would you want it? pure laziness? haha
	<buu> Apocalypse: For buubot..
	<Apocalypse> mmm for now you can just use fsv::inmemory until somebody with enough wizardry does the overrides :)
	<Apocalypse> I'll file that away in my TODO and see if I will return to it someday hah
	<buu> Exccelent.

=back

=head1 SEE ALSO