From: Christophe R. <cs...@ca...> - 2003-05-29 11:36:58
|
Rudi Schlatte <ru...@co...> writes: > Daniel Barlow <da...@te...> writes: > >> Rudi Schlatte <ru...@co...> writes: >> >>> * Export syscall-error, so conditions of this type can be handled >>> outside of the sb-posix package >> >> Well spotted. > > Another one, not so easily solved this time: the calls from > sb-posix;interface.lisp are exported, but the constants from > sb-posix;constants.lisp are not. Could perhaps sb-grovel be convinced > to issue export statements? Almost certainly. Isn't there another issue involved with specifically SB-POSIX? Remember, we're encouraging people _not_ to :USE the package, so in that sense exporting SYSCALL-ERROR isn't the whole story, I think. Something in me wants a package called SB-POSIX-INTERFACE or somesuch, which can be USEd, into which SYSCALL-ERROR would go and be exported from; SB-POSIX would be strictly for constants and functions associated with manual pages. Does that make sense? Christophe -- http://www-jcsu.jesus.cam.ac.uk/~csr21/ +44 1223 510 299/+44 7729 383 757 (set-pprint-dispatch 'number (lambda (s o) (declare (special b)) (format s b))) (defvar b "~&Just another Lisp hacker~%") (pprint #36rJesusCollegeCambridge) |