[Seaside] Seaside 2.9 & dynamic variable

[Julian Fitzell]

Ironically, not necessarily. Squeak's debugger, at least, doesn't
necessarily use the process that was running the code when an error
occured to step through it, which means the process variable isn't
set.

The new exception handler code does however catch a Notification
indicating that the WACurrentRequestContext process variable was not
set and resumes with the correct value. This allows you to step over
code that uses that process variable in most cases. There is also a
slight modification in the Seaside-Squeak-Development package to make
inspecting things that depend on the current request context work from
the Debugger.

We're trying to make this better so do please let us know if you run
into problems of this sort with 2.9.

Julian

On Thu, Nov 13, 2008 at 4:51 PM, Sophie (itsme213) <itsme213 at hotmail.com> wrote:
> Has 2.9 changed how it does dynamic variables to some form of thread-local
> variables? If so, does that mean I can stop in the debugger and see those
> variables more easily? In 2.8 they were often visible through session, which
> was not accessible in the debugger.
>
> Thanks!
>
>
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>