Re: Module submission Return::Value

2002-02-24 Thread Jesse
What do I actually need to do to get Class::ReturnValue into the modules list at this point, then? Thanks, Jesse On Wed, Jan 30, 2002 at 09:28:03PM +, Tim Bunce wrote: > On Wed, Jan 30, 2002 at 10:36:18AM -0500, Jesse wrote: > > Well, this one isn't actually something that change

Re: Module submission Return::Value

2002-01-30 Thread Tim Bunce
On Wed, Jan 30, 2002 at 10:36:18AM -0500, Jesse wrote: > Well, this one isn't actually something that changes control flow. It's > more of an object with rich behaviour that a method can hand back to its > caller, who can work with it in more ways than your usual return value. Sure, but it's rol

Re: Module submission Return::Value

2002-01-30 Thread Jesse
Well, this one isn't actually something that changes control flow. It's more of an object with rich behaviour that a method can hand back to its caller, who can work with it in more ways than your usual return value. It is, like most things these days, intended to be a base class that an author

Re: Module submission Return::Value

2002-01-30 Thread Tim Bunce
On Tue, Jan 29, 2002 at 09:09:11PM -0800, William R Ward wrote: > [EMAIL PROTECTED] (Perl Authors Upload Server) writes: > > modid: Return::Value > > Return::Value is an object which encapsulates most of the standard > > behaviors for function/method return values. It allows a func

Re: Module submission Return::Value

2002-01-29 Thread William R Ward
[EMAIL PROTECTED] (Perl Authors Upload Server) writes: > modid: Return::Value > Return::Value is an object which encapsulates most of the standard > behaviors for function/method return values. It allows a function to > return an object that is treated as a boolean in boolean c