libera/#commonlisp - IRC Chatlog
Search
21:52:51
phoe
nij-: you need to edit it to (cffi:defctype ssize-t #+cffi-features:x86 :int32 #+cffi-features:x86-64 :int64 #-(or cffi-features:x86 cffi-features:x86-64) (error "Unable to guess ssize-t."))
22:04:40
phoe
no, I think that either of these two keywords is going to stay; you'll want to put a different reader conditional in there I guess
22:16:31
NotThatRPG_away
Anyone know if 5AM test names must be globally unique? It has test suites, but it seems like one can look up a test by name, so maybe test names do have to be unique?
23:35:01
phoe
"compile-file transforms the contents of the file specified by input-file into implementation-dependent binary data which are placed in the file specified by output-file."
23:37:59
phoe
it's still more than assembly because you need tons of metadata to properly use the assembly code for compiled functions
23:39:24
thuna`
It would probably be conforming for an implementation to just do nothing with compile-file
4:49:52
hayley
src/code/load.lisp, look for (define-fop 17 :not-host (fop-load-code ((:operands header n-code-bytes n-fixup-elts))) ...)
5:41:09
beach
Speaking of which, I seem to remember that there are a lot of restrictions on the environment into which a FASL is loaded, compared to the one in which it was compiled, that it seems it has to be loaded almost immediately after being compiled. And if so, the advantage of creating a FASL file seems not that great.
5:41:32
beach
Plus, there are restrictions on the file compiler, such as some objects not being possible to serialize.
5:42:20
beach
But I can't remember the relevant section in the standard that talks about such restrictions.
7:16:46
jackdaniel
circular references require fiddling with make+load-form and make-init-form - in some cases it is not possible to serialize properly invocations to these functions
7:22:39
jackdaniel
regarding restrictions, I think that it is mostly about referenced objects - most notably packages
8:19:55
loke[m]
I have been trying to use postmodern-dao. I'm not a huge fan. I'm considering writing my own dao metaclass. Send help.
8:37:28
hayley
Prior to software engineering classes I would have answered "decentralised autonomous organisation". The former has...something to do with retrieving rows as objects from a relational database. Now I forgot.
8:37:30
jackdaniel
beach: make-load-form page of the standard; all "externalizable" objects may be referenced, but creation forms can't contain circles - to handle them initialization forms were introduced
8:38:03
hayley
In the Spring framework for Java, you have a "model", "service", "repository" and our instructor would call one of the latter two of those the "DAO" and I can't bloody remember which, because no one else on the planet does.
8:38:13
beach
jackdaniel: I was referring to the restrictions that I seem to remember about what's in the environments.
8:39:05
jackdaniel
ah, no; I don't remember the section, that's more from memory how fasls work in ecl
8:46:03
specbot
Additional Constraints on Externalizable Objects: http://www.lispworks.com/reference/HyperSpec/Body/03_bdd.htm
8:55:07
jackdaniel
I wouldn't say that these restrictions are severe enough to say that "fasl must be loaded almost immediety after being compiled [...]"
8:58:19
jackdaniel
on the other hand this restriction is one of major factors regarding the speed of loading fasls - all symbols and packages must be resolved during the load time
9:02:50
jackdaniel
yes, for example loading asdf.fas on ecl takes a few seconds (compared to 50ms without it) - a lot of it is about creating symbols if I remember correctly, but also creating classes etc
9:04:37
jackdaniel
(save-lisp-and-die greatly mitigates this kind of issues, a feature ecl doesn't have sadly)
9:06:23
beach
I wasn't referring to just the difference in performance between the two. I was referring to the role that loading code represents to either the user of a program or a project. And yes, I was assuming that the image would be saved in a final application.
9:14:08
beach
jackdaniel: Also I am confused. Are you saying loading asdf.fas (which I assume is a FASL file) takes a few seconds? But then what does 50ms refer to?
9:20:26
jackdaniel
usually people require asdf at startup; I was referring to startup: without asdf - up to 50ms, with asdf - a few seconds; so I was referring the startup time
9:22:34
jackdaniel
regarding how useful it is to have precompiled fasl - startup of an environment for developing a program that has precompiled dependencies than loading and compiling everything from scratch; admittedly if someone never restarts the lisp process then it is only a minor nuisance