Keep It Simple, Stupid | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
What about Object::Realize::Later, Class::LazyObject, or Data::Lazy? How would your module differ? How is this laziness effected anyhow? Is it going to make map Foo::Bar->new( foo => $_ ), LIST slimmer where Foo::Bar::new is something simple like return bless { @_ }, $class? What is the case where you'd realize benefits from this and at what point are those benefits lost? If you name your module after a proxy then I'd expect it to be something SOAP-like - your object stays around to relay stuff to and from the actual object which exists somewhere else. So don't use the term 'proxy' if the idea is about having something be lazy. In reply to Re: RFC: Object::Proxy (or somesuch)
by diotalevi
|
|