freenode/#lisp - IRC Chatlog
Search
22:53:59
aeth
jcowan: I think the idiomatic way to solve that problem in modern CL would be to compute the directory containing the foo.asd file that describes the system foo and then have ASDF recognize that directory (would that be by pushing it to asdf:*central-registry*? not sure here)
22:56:18
jcowan
I see two problems, or perhaps only one: you can't sandbox what you load easily, and you don't know how to interface with it except by convention or reflection.
22:58:04
aeth
Sandboxing is apparently impossible in current implementations. Iirc, beach is working on an implementation that permits sandboxing as one of its goals.
22:58:07
aeth
https://github.com/robert-strandh/SICL/blob/e19613c61d8797a9ea586e3c513efdaeb0860d68/Papers/Global-environments/sec-benefits.tex#L92-L119
23:48:01
griddle
I've got a quick question. I've been working on implementing a small lisp interpreter and I'm interested in how '(...) and (quote (...)) relate
0:09:52
jcowan
If you had a sandbox, you could statically examine what it does and see if you are willing to load it into the live image, but of course there are no guarantees about what crimes it might commit dynamically.
3:17:45
r0sebush
question from a sbcl newbie.. What's is the best method to include libraries, like cl-ppcre into your lisp code for production release? .sbclrc or include (ql:quickload ...) in your code base?
3:39:49
gendl
2. When ready for release, use (asdf:operate 'asdf:monolithic-compile-bundle-op <your-application-system-name>)
3:40:24
gendl
that will produce one big .fasl with your whole application including its depended-upon stuff, presumably in the right order.
3:40:52
gendl
then start a fresh sbcl image, load this .fasl, then dump image. (I'm not sure the specifics of that with sbcl). ASDF also has built-in operators for doing that.
3:41:43
gendl
See this ancient blog post which needs to be updated/added to: http://gendl.blogspot.com/2013/03/saving-images-with-asdf3.html
3:43:37
gendl
it was suggested earlier today that someone needs to make a do's-and-don'ts for production application release and maybe a how-to. It's something which should be pretty routine and well known at this point but doesn't seem to be.
5:45:44
no-defun-allowed
- use burgled-batteries to interface python module that interfaces opencv for images
6:22:44
no-defun-allowed
still, most of this box-mangling and vision stuff would read better in lisp but common-cv is just a very fine wrapper over C unfortunately