Re: Issues with package location information on SBCL

On Mon, Feb 19, 2018 at 7:03 PM, Eric Timmons wrote: > I've also opened the following bug on SBCL to let them know about it: > https://bugs.launchpad.net/sbcl/+bug/1750466. This bug has been fixed upstream and should probably appear in SBCL 1.4.7. Since they got that fixed

Re: Issues with package location information on SBCL

On Tue, Feb 20, 2018 at 3:35 PM, Robert Goldman wrote: > This does seem to illustrate an issue with the current "export everything > that's in UIOP" strategy. > > Should we consider changing this policy? > 1- UIOP reexports everything that individual subpackages of UIOP

Re: Issues with package location information on SBCL

This does seem to illustrate an issue with the current "export everything that's in UIOP" strategy. Should we consider changing this policy? Or, if we have "internal" functions that we don't want to be visible through `UIOP/DRIVER`, should we simply not export them from the sub-packages and

Re: Issues with package location information on SBCL

On Mon, Feb 19, 2018 at 7:03 PM, Eric Timmons wrote: > Glad to help! I've also opened the following bug on SBCL to let them know > about it: https://bugs.launchpad.net/sbcl/+bug/1750466. > Thanks! > Also, I checked that nothing else in ASDF uses `parse-define-package-form`, >

Re: Issues with package location information on SBCL

Thanks a lot for fixing this issue! I opened a MR based on it: https://gitlab.common-lisp.net/asdf/asdf/merge_requests/92 —♯ƒ • François-René ÐVB Rideau •Reflection• http://fare.tunes.org To be an anarchist only means that you believe that aggression is not justified, and that states necessarily