[Sbcl-devel] --userinit processing

[Zach B. <xa...@xa...>]

If you pass a bogus file to "--userinit", sbcl silently falls back to
the default userinit file. I'd generally prefer to have sbcl stop;
failing to load a customized init file is serious. The comments in
toplevel.lisp suggest similar thinking:

      ;; (Why not wrap everything, even the stuff above, in this
      ;; restart? Errors above here are basically command line or
      ;; Unix environment errors, e.g. a missing file or a typo on
      ;; the Unix command line, and you don't need to get into Lisp
      ;; to debug them, you should just start over and do it right
      ;; at the Unix level. Errors below here are generally errors
      ;; in user Lisp code, and it might be helpful to let the user
      ;; reach the REPL in order to help figure out what's going
      ;; on.)

Would anybody object to a patch that causes sbcl to fail if either
--userinit or --sysinit specify files that fail a PROBE-FILE?

Zach