Hi guys, i was just wondering if some notification mechanism ( signal/slot
alike ) was planned in perl 6, like they already are in glib and qt ?
Or is it maybe better if implemented in some perl6 module (don't think so)
??
Or maybe this matter has already been discussed and is now
Sam Vilain wrote:
Associations *are* fundamental object things. Presenting them in terms of
attributes is the real hack.
Associations *are* fundamental things, but I don't think they are part
of an object.
They describe relationships between objects and should exist independantly
and
Hi guys, i was just wondering if some notification mechanism (
signal/slot alike ) was planned in perl 6, like they already are in
glib and qt ?
class Signal {
has @.dest;
method emit($code) { $code($_) for @.dest }
method attach($obj) { push @.dest: $obj }
}
class
--- Andy Wardley [EMAIL PROTECTED] wrote:
Associations *are* fundamental things, but I don't think they are
part of an object. They describe relationships between objects and
should exist independantly and orthogonal to them.
Agreed. Is there any reason that shouldb't be done with something
At 6:27 PM + 3/6/03, Yannick Le Saint wrote:
Hi guys, i was just wondering if some notification mechanism ( signal/slot
alike ) was planned in perl 6, like they already are in glib and qt ?
I'm not exactly sure what you're looking for, since I'm not too
familiar with qt or glib, but if you
At 2:08 PM +1300 3/7/03, Sam Vilain wrote:
As long as mechanisms are put in place to allow modules to bypass object
encapsulation and private/public constraints, and given that Parrot will
have no XS,
It wouldn't be wise to jump from Parrot won't do perl 5's XS scheme
to Parrot won't have a way
On Sat, 08 Mar 2003 06:58, Dan Sugalski wrote:
At 2:08 PM +1300 3/7/03, Sam Vilain wrote:
As long as mechanisms are put in place to allow modules to bypass
object encapsulation and private/public constraints, and given that
Parrot will have no XS,
It wouldn't be wise to jump from Parrot
# New Ticket Created by Jason Gloudon
# Please include the string: [perl #21508]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=21508
This adds still more ops and re-organizes register use to avoid potential
On Fri, Mar 07, 2003 at 11:38:41PM +, Jason Gloudon wrote:
# New Ticket Created by Jason Gloudon
# Please include the string: [perl #21508]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt2/Ticket/Display.html?id=21508
This adds
Joseph F. Ryan wrote:
Leopold Toetsch wrote:
I don't have a docs/macros.pod. I guess my version of imcc is old (-:
The update your parrot please. A lot of these issues are documented and
solved.
For instance, in the interests of speed, it would be nice if perl6
builtins written in perl6
10 matches
Mail list logo
