freenode/#lisp - IRC Chatlog
Search
19:25:58
lambdice
Xach: well i mean, lets say.. i wrote a game in common lisp, using cl-sdl2 and other stuff
19:26:52
Xach
Ok. I don't know how best to do that. but people do use lisp to make games, so maybe there is some insight from those people.
19:27:41
Xach
lambdice: it is usually far more challenging to make something someone else wants to run, than to actually make it available for them to run.
19:28:00
Colleen
Unknown command. Possible matches: 8, say, mop, time, tell, roll, help, deny, clhs, login,
19:28:57
pjb
lambdice: you may get more specific answer in #lispgames even for packaging your game releases.
19:30:07
lambdice
well lets say fo cl-sdl2 my first try was like, create an install.lisp, that will run quicklisp to install cl-sdl2
19:36:21
jmercouris
but it produces nice little standalone binaries, and it is easy to get started with
19:36:53
jackdaniel
lambdice: EQL may be used from any implementation via swank protocol. I've encountered such mention in its documentation
19:39:09
jackdaniel
lambdice: here you have a sub-paragraph giving overview on CL GUI solutions: https://common-lisp.net/project/mcclim/involve
19:41:03
jmercouris
It becomes a question of a Theseus type ship though, if we modify a GUI toolkit enough to interface it with lisp, is it still the same toolkit?
19:41:06
oleo
mcclim is the only one written in common-lisp and using only standard backends like clx
19:41:35
jmercouris
Again though, I guess it depends on what views you are trying to support, does McClim have a web-view for instance?
19:44:05
jmercouris
lol the way you phrased that it sounds like you are waiting to push changes that add instability :D
19:44:40
jmercouris
oleo: What OS? Also depending on how you install QT, it can really vary the stability
19:44:53
jmercouris
it also depends on how you are treating and handling the objects, some behaviors are allowed, but dangerous
19:47:42
oleo
anyway, mcclim works for me and does the things i expect of it albeit some features not working or not being implemented
19:48:47
oleo
one has to be already fluent in oop in order to understand all the hooks and judge if something is wrong (logic or otherwise)
19:50:14
oleo
for example there is a Drei/lisp-syntax.lisp in which there is a func named perenthesis-highlighter or so
19:52:13
oleo
i only replaced it with an ink, such that it draws stuff with some ink (which is the lighter version of my foreground ink, and my background ink is black)
20:13:59
emaczen
how would I create an initialized C array, i.e. type name[size] = {v1, v2, ... vsize}
20:18:14
oleo
they have very different ideas and expectations about types, sometimes you have to even intervene manually in cffi
20:39:49
oleo
https://common-lisp.net/project/cffi/manual/cffi-manual.html#with_002dforeign_002dobject
20:45:07
oleo
emaczen: and even if it's probably not an exported symbol, so not exposed and as such not an api function
21:00:47
chream_
Hi, I am having some troubles with emacs and ecl. When trying to load some systems it unexpectedly disconnects me from ecl and the server stops. The only info I get is from the swank server: Illegal instruction: 4. I seem to have traced the problem to cffi. Has anyone had this before? Also, one clue might be that I recently installed many native GNU command line tools on my mac. Has anyone had any troubles with this before?
21:02:00
chream_
Lastly, the systems apparently install fine when I tried outside emacs and slime. Might be a emacs problem then?
21:02:59
chream_
Also, everything works on other implementations. (works on sbcl, got an unrelated heap error for allegro)
21:09:54
Shinmera
Well if you use CFFI or other stuff that directly manipulates memory, you might corrupt the implementation badly, leading to a crash.
21:10:36
Shinmera
Might also be a bug in ECL, or the library not being adapted to certain ECL specific things.
21:12:07
jackdaniel
recent changes to slime (didn't find time to narrow them yet) shown some ECL problems. probably my last pull request to slime repository
21:27:13
asarch
Common Lisp has CLOS, Emacs has "Enhanced Implementation of Emacs Interpreted Objects"
21:47:57
aeth
I can't say this: (defstruct foo (bar (make-array +foo+ :element-type 'fixnum) :type (simple-array fixnum (+foo+))))
21:48:54
aeth
I can e.g. say this: (defstruct foo (bar (make-array (list +foo+ 4) :element-type 'fixnum) :type (simple-array fixnum (42 4))))
21:49:30
aeth
So I can get around the problem of make-array for 2D arrays where '(+foo+ 4) will obviously not work, but I can't get around the problem of type in a defstruct for any dimension arrays if there's a constant instead of a number for the size
21:50:14
aeth
The problem is that defstruct doesn't quote the type in :type so I can't e.g. `(,+foo+) or (list +foo+)
22:11:10
aeth
The best alternative if there's no workaround would probably be to define (gensym) types with the struct