Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose quicklisp location to user #33

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

cab-1729
Copy link

Allow for different quicklisp location.

@vindarel
Copy link
Contributor

There might be an issue if we wanted to quickload some libraries in our init file right?

@cab-1729
Copy link
Author

There might be an issue if we wanted to quickload some libraries in our init file right?

init file? I don't get it. Please forgive me, I'm a little new to Lisp.

@vindarel
Copy link
Contributor

I'm a little new to Lisp.

it's great you send PRs already :)

I should have said sbcli's config file.

we load one:

(if (probe-file *config-file*)
  (load *config-file*))

with your PR we load quicklisp afterwards.

What if we want to quickload a library in our config file, before quicklisp is loaded?

(there might be an issue, I don't have the answer)

@cab-1729
Copy link
Author

If the user intends to to use quickload in the sbclirc shouldn't he have to load quicklisp in the same file separately?
If the user does so then there would be no issue.
It makes sense for a user to load dependencies in the same file they are being used, rather than relying on it being already loaded in another dependency. I think this is a general programming practice.
For example, this is the reason why we use #ifndef header guards in C. To stop a dependency from being loaded more than once, because the programmer is expected to load each dependency in each file it is used even if those files are compiled together. I hope I'm making sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants