Re^2: RFC: Object::Proxy (or somesuch)

What about Object::Realize::Later, Class::LazyObject, or Data::Lazy? How would your module differ?

Data::Lazy seems to be only for variables, this module would be for objects.

With Class::LazyObject and Object::Realize::Later you seem to be required to create a ::Lazy package of some kind, which later on would turn into a non-lazy version of itself. For my needs at least, this was too much overhead.

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?

I doubt you will get much gains in efficiency from simple constructors, but then why would you want to lazy load it anyway? The real goal (at least for me, I cannot speak for dragonchild) is the ability to have an object, which looks like a Duck, and quacks like a Duck, but is only really a Duck at the very last possible second.

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.

I disagree that proxy == SOAP-esque. The Proxy pattern is from the GoF Design Patterns book, and is just simply what you describe without the distributed part. I agree that proxy is not a good name, hence the reason for this meditation, we can't figure out a better one :)

-stvn

Comment on Re^2: RFC: Object::Proxy (or somesuch)

Replies are listed 'Best First'.
Re^3: RFC: Object::Proxy (or somesuch) by diotalevi (Canon) on Nov 19, 2004 at 19:31 UTC
Could you make this more general so you could make lazy expressions? So instead of getting a number back from `0 + $foo->bar` you get back a value which will defer running ->bar until it is actually needed? Sort of like promises from E. Maybe you could just name your module Object::Realize::Later::Lighter if the improvement is that you avoid having a ::Lazy package. Are you really proposing having so many lazy packages that avoiding adding a ::Lazy one is going to help? Partially I wonder because AFAICT, Object::Realize::Later is already sort of a standard when people solve this problem.	[reply] [d/l]
Re^4: RFC: Object::Proxy (or somesuch) by dragonchild (Archbishop) on Nov 19, 2004 at 19:42 UTC
In reading the docs for O::R::L, I was put off by the amount of book-keeping I, as the programmer, needed to do. Plus, I couldn't lazyload a class that didn't already have a bunch of crap defined for it. It also seems like so much overhead just to intercept the constructor call intercept the first usage get the heck out of the way What about calling it Class::Plugin::LazyLoad? That's actually the exact term for what it's doing, now that I think about it. As for deferring expressions, I can look at that. It wouldn't be in this module, though. That would be more of Expression::Plugin::LazyLoad ... or somesuch. Being right, does not endow the right to be rude; politeness costs nothing. Being unknowing, is not the same as being stupid. Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence. Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.	[reply]
Re^4: RFC: Object::Proxy (or somesuch) by stvn (Monsignor) on Nov 19, 2004 at 19:46 UTC
Could you make this more general so you could make lazy expressions? So instead of getting a number back from 0 + $foo->bar you get back a value which will defer running ->bar until it is actually needed? Sort of like promises from E. I dont think that would be possible due to the way that perl evaulates arguments. Maybe you could just name your module Object::Realize::Later::Lighter if the improvement is that you avoid having a ::Lazy package. Well, we also add a number of other features, including; handling overloaded ops, and handling direct access (`$obj->{field}` but not just hashs. Blessed arrays,scalars and subs as well.). In general the API and style is very different than Object::Realize::Later so I dont think it would fit. -stvn	[reply] [d/l]
Re^5: RFC: Object::Proxy (or somesuch) by diotalevi (Canon) on Nov 19, 2004 at 19:51 UTC
How about just naming the thing Object::LazyConstructor if that's what it really is. You defer loading the module and you defer calling the object constructor. You've more potential gain from deferring object constructors than a load of more mere perl code. That is, if you are creating lots of objects that have expensive constructors. Show us an example of the code you wished you had this feature for. Please.	[reply]
Re^6: RFC: Object::Proxy (or somesuch) by stvn (Monsignor) on Nov 19, 2004 at 20:20 UTC
Re^6: RFC: Object::Proxy (or somesuch) by dragonchild (Archbishop) on Nov 19, 2004 at 19:53 UTC


Pathologically Eclectic Rubbish Lister
	PerlMonks