Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp.
Uncategorized
9
Posts
4
Posters
9
Views
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under
~/quicklisp/local-projects/or~/common-lisp/? -
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under
~/quicklisp/local-projects/or~/common-lisp/?@amoroso I put my projects into the former and recommend it.
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under
~/quicklisp/local-projects/or~/common-lisp/?@amoroso the former, if you are using quicklisp and it's a local project.
-
@amoroso I put my projects into the former and recommend it.
@hajovonta Thanks.
-
@amoroso the former, if you are using quicklisp and it's a local project.
@AndreasDavour Right, a local project. Thanks.
-
Suppose I use SBCL to develop a Common Lisp project to be built with ASDF and loaded with Quicklisp. To simplify things and leverage defaults should the source tree go under
~/quicklisp/local-projects/or~/common-lisp/?@amoroso I’d put it into ~/common-lisp/ for ASDF compatibility, but I haven’t tried it with Quicklisp yet.
-
@amoroso I’d put it into ~/common-lisp/ for ASDF compatibility, but I haven’t tried it with Quicklisp yet.
@aartaka Thanks, others in this thread report it should work also under
~/quicklisp/local-projects/. -
@aartaka Thanks, others in this thread report it should work also under
~/quicklisp/local-projects/.@amoroso it does work indeed, just checked. Then it’s a matter of preference. And my preference is ~/common-lisp/, because using Quicklisp-specific dirs feels like (but, in this case, isn’t) vendor-lock. But that’s a me-thing, feel free to ignore.
-
@amoroso it does work indeed, just checked. Then it’s a matter of preference. And my preference is ~/common-lisp/, because using Quicklisp-specific dirs feels like (but, in this case, isn’t) vendor-lock. But that’s a me-thing, feel free to ignore.
@aartaka An interesting thought, thanks.
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
When you don't want to hang out. | More comics: https://rooniecomics.com/comics/tentatively
-
@martellum credo sia complicato perchè se vendevano con le scadenze taroccate allora legalmente chi comprava è a posto, certo se sei del mestiere e ti arriva certa roba qualche domanda dovresti fartela.
-
RE: https://mstdn.social/@hkrn/115604772184730195
The only sites that should cost this much are YouTube, Amazon, or Facebook
This is plain fraud
-
Damn, fact checks involving trivial mathematics seems hard. Even for journalists.
I bet you have all seen the alarmist and very viral-worthy claims that "Brazil cuts down tens of thousands of acres of rainforest to build a four-lane road for COP30".
Now, some articles also mention that the road is "more than 13 km" long. Let's be generous and say that it is 15 km. And let's say "tens of thousands" is actually just 15,000.
15,000 acres is 61 square kilometres.
For a 15 km long road to cover 61 square kilometres, how wide does it have to be? Four kilometres.
I rest my case.
(Note: Of course this doesn't mean that I would approve of large-scale destruction of the rain forest in general. But building 13 km of road, in a city with 1.4 million inhabitants, is not significant in the large scale of things.)
-
RE: https://mastodon.social/@Mastodon/115604090796158451
Oops. 👀 Someone might have already pressed the order button yesterday, before this post..
-
@filippodb non saprei ma comunque vanno denunciati e chiusi con i sigilli.
E un pensierino lo farei su chi avvertiva prima di fare controlli
-
@ilcomizietto Mi fai uno screenshot?
-
@mora Continua a comparirti "post in attesa" al posto del link.
