Object::Realize::Later and Class::LazyObject require a lot of work on the part of the lazy object's author. Our module can be used with classes that don't even know they're being loaded lazily. For example, you could lazy-load DBI with this module.

We differ from Data::Lazy because we're not tied and we're not specific to data structure. We're specific to classes and objects.

The laziness is effected by substituting a lazy constructor for the real constructor(s). Our constructor is sub new { bless @_ }. (No, we don't expect to be inherited from.) Then, when any method is called or any direct access is attempted or any overloaded operator is used, we build the object, then redispatch the requested access/method/overload.

So, the benefits are that we defer all construction until such a time as you absolutely need the object. Potentially, if you don't use the object, it never gets constructed. There is a slight penalty for the first access to the object, but it's very slight (almost negligible).

I think the word Proxy goes away in favor of LazyLoad. Better?