What is the status of this bug/issue?
I'm losing track of all the bugs in the system. It would be very
helpful (and your bug is less likely to be forgotten) if you could
file Trac bugs against 1.0 for these reports?
It's easy enough to get a common-lisp.net account to sign onto Trac.
Thank you,
Ian
On May 7, 2008, at 6:24 AM, Alex Mizrahi wrote:
??>> sorry, i didn't get -- what is "ABORT restart",
LPP> http://www.lisp.org/HyperSpec/Body/res_abort.html
"Typically, in an interactive listener, the invocation of abort
returns to
the Lisp reader phase of the Lisp read-eval-print loop, though in
some batch
or multi-processing situations there may be situations in which
having it
kill the running process is more appropriate."
are you sure that it is a good idea to make it returning to a random
point
in program (after with-transaction) rather than to a command prompt
(what
people would expect)?
and if people want to abort transaction only, can't they just call
abort-transaction?
??>> how does it lose the controller
LPP> After invoking this restart, the controller is gone. I don't know
LPP> exactly why, but I suppose the reason is that the current
transaction
LPP> isn't aborted.
maybe we'll better fix this bug? non-local control transfer should
correctly
abort transaction.
i think "controller lost" is only possible when when something awful
happens
to the socket.
i can't reproduce "controller lost" via abort restart.
i.e. i run such code
(ele:with-transaction () (make-instance 'something) (error "barf"))
and when SLIME debugger opens, i choose ABORT restart, and it
returns to
REPL.
and works quite fine afterwards..
if you have that "controller lost" thing reproducible, please share
how to
reproduce this
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
_______________________________________________
elephant-devel site list
elephant-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/elephant-devel
