Yuval Kogman wrote:
Since CANDO is a multimethod, IMHO this can be safely extended to
allow:
$object.can(Class);
$object.can(Role);
to better support duck typing.
Why would you not use .does or .isa there? Are you wanting this to go
through all of the Class/Role's methods
On Fri, Jun 16, 2006 at 10:51:24PM -0500, John M. Dlugosz wrote:
: Anyway, as passionate as I was about resumption, or at least making it
: not impossible to implement resumption, at the next ANSI meeting the
: terminate-only camp made compelling arguments.
Well, interestingly, I used to be in
> Larry Wall profounded:
> On Fri, Jun 16, 2006 at 11:51:09AM +0930, Tom Lanyon wrote:
> : On Thu, Jun 15, 2006 at 10:12:12PM -0400, Matt Todd wrote:
> : > I really like these. I think you're on to something. I'm
> definitely in
> : > favor of Momi Wiki, or just Momi.
> :
> : Just 'Momi' sounds goo
I was involved in the C++ standardization process, and argued for
resumption as opposed to termination only in exceptions. I was somewhat
of a pioneer, implementing C++ exceptions for my team to use before
commercial compilers had them. After all, why start a new project with
an old paradigm?
If anybody is interested on this list,
the slides and the examples of my 2 days course are available here:
http://www.szabgab.com/perl_in_test_automation.html
regards
Gabor
Synopsis 12 specifies that:
.can interrogates any class package's CANDO multimethod for
names that are to be considered autoloadable methods in the
class
but aside from that is just a name -> method iterator mapping.
Since CANDO is a multimethod, IMHO this can be safely e
