On 06/17/2011 06:49 PM, Kevin Wright wrote:
Agreed :)
Phrases like "callback style" or even just "asynchronous" would
probably be more useful in this context, as they better reflect the
intent of the code.
A few days ago I updated the draft to just call for "similarities" with
continuations (and that the design is "inspired" by CPS). Given that
you're there, a final question: should I put an UML stereotype to my
callback classes, do you think <<continuation>> would be wrong? At this
point, I think it would be imprecise. Probably <<callback>> is better.
--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
fabrizio.giud...@tidalwave.it
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to javaposse@googlegroups.com.
To unsubscribe from this group, send email to
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
