Hi, when using root interactively, an "exit()" doesn't do anything - fine, if it's the defined reaction. But when loading a library which has an exit() statement, root will quit. This seems inconsistent to me, as it looks to the user as if libraries are just "the fast version" of source files, and I believe the user expects there is no difference between interpreted and compiled code. Can we do something about this? Either make root quit on exit() or catch exit()s by root (although I wouldn't know how to do that)? I believe quitting root on exit() makes sense; it's something I have seen many new root users do trying to get out of root - which can be interpreted as either "lack of experience" or "straight forwardness" :-] What do you think? Cheers, Axel. _____ Axel Naumann, Kath Universiteit Nijmegen / NIKHEF, The Netherlands Experiment: D0 / Fermilab, USA. Phone: +1 (630) 840 8595 http://www-d0.fnal.gov/nikhef
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:41 MET