> 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?
This thing was meant for discussion, not as a bug report.
I haven't be
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.
Than
??>> 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 th
> sorry, i didn't get -- what is "ABORT restart",
http://www.lisp.org/HyperSpec/Body/res_abort.html
> how does it lose the controller
After invoking this restart, the controller is gone. I don't know
exactly why, but I suppose the reason is that the current transaction
isn't aborted.
> how a
LPP> When an error occurs inside a txn, this restart will lose the
LPP> controller. It should be replaced by the ABORT-TRANSACTION restart
LPP> behaviour.
sorry, i didn't get -- what is "ABORT restart", how does it lose the
controller and how are you going to remove it?
___
