>>>>> "JNP" == Joshua N Pritikin <[EMAIL PROTECTED]> writes:
JNP> What is wrong with this:
JNP> $watcher->{data} = ...; #?
that breaks the OO rules. one shoudl never assume knowledge about the
internal stucture of an object. there should be a method/attribute for that.
JNP> Yah, that's still a problem.
just add another method/attribute like you did with timeput_cb. no logic
behind it just something to hold private data. this makes subclassing
very easy.
#####################
seperate idea (which i feel is bogus)
>> i feel the user has to keep track of these higher level objects and not
>> event.pm. there is no reason to offer these class level things unless
>> they are requested. make them a subclass or sister/helper class and then
>> we get the autodestruct feature. probably too hard to do now, but what
>> do you think of it?
JNP> I'm not sure I follow your thinking. What do you mean?
>> does anyone use all_watchers or similar class level calls?
JNP> Again, I'm not sure what you're driving at.
i will try to explain my blathering some other time. i am not sharp
enough this morning to do it. but i feel i may be wrong as you have to
have class level structures just to keep the list of watchers that do a
I/O poll and timers and stuff. having written event systems, i forgot
that you can't have a scope exiting destroy (for sure not in c!). so my
idea is bogus.
uri
--
Uri Guttman --------- [EMAIL PROTECTED] ---------- http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page ----------- http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net ---------- http://www.northernlight.com
