that lack methods or roles
Larry Wall wrote:
Jonathan Lang wrote:
: How would I declare a subtype of a class which messes with the
: dispatching mechanism to exclude certain methods and/or roles from
: it?
Er, uh...tell you what. Why don't you provide some sample code to
go with your
On Fri, 2004-04-23 at 21:44, Jonathan Lang wrote:
OK: I'm planning on creating a widget which must not make use of any of
the indicator functionality of the HList; I don't just want to not use the
functionality - I want to have its use forbidden (letting the optimizer go
ahead and toss out
Dov Wasserman wrote:
It's a valid question in general, but since you're designing this
functionality from the ground up (and not retro-fitting it in to
existing code), wouldn't the better approach be to create a non-GUI
HList class, and a GUI subclass that adds the indicator methods? Or
How would I declare a subtype of a class which messes with the dispatching
mechanism to exclude certain methods and/or roles from it?
=
Jonathan Dataweaver Lang
__
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for
On Fri, Apr 23, 2004 at 03:07:23PM -0700, Jonathan Lang wrote:
: How would I declare a subtype of a class which messes with the dispatching
: mechanism to exclude certain methods and/or roles from it?
Er, uh...tell you what. Why don't you provide some sample code to
go with your question, and
At 6:12 PM -0700 4/23/04, Larry Wall wrote:
On Fri, Apr 23, 2004 at 03:07:23PM -0700, Jonathan Lang wrote:
: How would I declare a subtype of a class which messes with the dispatching
: mechanism to exclude certain methods and/or roles from it?
Er, uh...tell you what. Why don't you provide
Larry Wall wrote:
Jonathan Lang wrote:
: How would I declare a subtype of a class which messes with the
: dispatching mechanism to exclude certain methods and/or roles from
: it?
Er, uh...tell you what. Why don't you provide some sample code to
go with your question, and we'll just
