> mostly agreed. i'd go for it's /often/ better to quit. and the downside > of the library not quitting is now you get to add a bunch of error > code to /sys/src/cmd.
Well, you _could_ modify /sys/src/cmd so that it checks all library return codes and _sysfatal()s as and when required, as a preliminary. It would be a small (relatively speaking) alteration that can be improved later. Lucho's right in that the library should _never_ terminate on error, he is wrong in that this can only apply in an ideal world where all returns from library functions are checked. But we may be compounding his error by not auditing /sys/src and adding error checking where it ought to be present and removing Plan 9's contribution to this state of affairs. Then Plan 9 gets to hold a bigger chunk of the high moral ground and also stops encouraging this approach. Is it even conceivable (haven't had my coffee yet) that we could have a library that reports all instances where user code _does_ not check for error returns? ++L
