> Hmm, you added call to 'handleBreakQuit' just before 'spadThrow'. > Have you tried to modify 'spadThrow' instead. In fact in > my private tree I have: > > spadThrow() == > if $interpOnly and $mapName then > putHist($mapName,'localModemap, nil, $e) > $BreakMode = 'throw_reader => throw_to_reader() > handleLispBreakLoop($BreakMode) > > so if that hange goes in then you will get quit in all places > that you add (and possibly a few more). ATM I still have to > verify/ensure that we enter break loop only when we want > to, but eventually I want to commit it.
Well, there were two reasons for my handleBreakQuit(msg) in these places. 1) Changing spadThrow was to dangerous, because it is used in a lot of places and I had no idea how changing it would influence (slow down) the compilation process. 2) Initially I wanted to get an idea in which places the errors are detected (therefore the "msg"), but I no longer insist on that. So if you think your code is fine then SpadUnit is probably also happy with it. As for the line ... (rc ~= 0) and $BreakMode = 'quit => EXIT_-WITH_-STATUS(rc) that you suggested for i-syscmd.boot. That may even be unnecessary, because if aldor compilation fails, a message will be triggered (which eventually calls spadThrow). However, I wouldn't get the actual exit code from Aldor then. I'm not yet using anything other than 0 or not 0, but one never knows. Ralf -- You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/fricas-devel. For more options, visit https://groups.google.com/d/optout.
