Re: [Pharo-project] [Seaside] Problem with announcements in Seaside when using Pharo 1.3

Another problem with the fork not mentioned yet, is the assumption all subscriber actions will have been carried out by the time next statement occurs. fork:'ing breaks that, and you can't make the assumption true without conflicting with the reason to fork: in the first place. Another argument in favor of only forking on unhandled exceptions I guess :) @#after: gripe in previous post: meh, ansi... -- View this message in context: http://forum.world.st/Problem-with-announcements-in-Seaside-when-using-Pharo... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.