[Seaside] Completelly pharo hang with seaside3
estebanlm at gmail.com
Tue Feb 3 15:17:30 UTC 2015
#name is implemented in Pharo3 class side, and used internally.
it was a mistake that has to be fixed in Pharo4, but for now you should not use it.
Is not a problem of seaside, is a problem of pharo… and hopefully it will be fixed for Pharo4, sorry for the inconvenience.
> On 03 Feb 2015, at 16:13, David Carlos Manuelda <stormbyte at gmail.com> wrote:
> In some of my examples, I subclassed WAComponent in order to test things
> I discovered that if you implement on class side the method name with self
> subclassResponsibility, then, pharo completelly hangs.
> Maybe is not a bug and is something I should not be doing, but anyways, it
> is not worth to hang pharo completelly, can it be reviewed?
> It can be tested just with that, immediatelly when you accept your changes,
> your pharo UI is completelly stuck (no possible user interrupts, it is
> completelly died)
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside