freenode/lisp - IRC Chatlog
Search
2:15:23
nyef
What SBCL API changes? SBCL's public API didn't change in any way that requires changes to other software. And private API changes are a matter of "what the heck are you doing poking around in there?!?"
5:13:39
beach
I added four new tasks to the Lisp Guild: https://github.com/Lisp-Guild/lisp-todo/projects/1
5:14:08
beach
These tasks are related to the "Cluster" assembler (I might rename it one day), mainly for x86 at this point.
5:15:45
beach
Cluster is "the assembler with a difference" because it gets rid of the issue of surface syntax by defining an assembly program as a list of instructions represented as standard instances, i.e. instances of classes defined by DEFCLASS.
5:18:00
borei
everyday something new ! and it's very cool features. Looking at CFFI (my proj requires some graphics - opengl, idealy VTK, but it's C++, so a bit more chanlanging), so here what i found, and question is more theoretical then related directly to lisp porgramming
5:18:43
borei
it's pretty easy to call C function from lisp - load shared library define funtion with required signature and point to C-function - done
5:20:04
beach
ACTION strongly suggests that people program in Common Lisp rather than in some inferior language.
5:21:02
loke``
borei: It does, but it doesn't have to in order to be able to handle callbacks (for example, CLISP doesn't do native compilation and ABCL compiles to the JVM, but both handle CFFI)
5:21:36
shrdlu68
beach: Interesting. So will will there be a directory for other architectures? ARM, PPC, etc?
5:23:22
beach
borei: We choose to work on certain things and not on others. I have chosen to work on things where I need only Common Lisp.
5:25:24
beach
borei: I know I am weird. I actually try to improve the situation of Common Lisp with respect to development tools and libraries. Most people prefer to develop games or websites for their personal satisfaction. Not that I don't get personal satisfaction from what I work on, of course.
5:27:01
beach
borei: It is a bit strange to me to have a channel dedicated to Common Lisp, and then to have a very significant number of people wanting to use C or C++, and a significant number of questions about why their programs crash when they use FFI to program in other languages.
5:27:48
fouric
shrdlu68: tbf "just got started" can include people who've been working with it for years, given how deep CL is taken to be
6:13:03
jackdaniel
if you had some troubles with McCLIM or have any feedback (i.e something didn't work), I'd love to hear about it
6:13:30
jackdaniel
to not clutter this channel, preferably on #clim – if you have any more problems, just come by and ask, somebody may know the answer
6:17:38
didi
Hum. CLtL2 says to append the suffix "p" to type predicates, but `defstruct' appends "-p".
6:26:00
didi
So `string-lessp' is a special case for `lessp', which respects the initial rule for "-p".
7:42:14
axion
Does anyone know of a macro someone has written which extends DEFUN to add a declaim for ftype/inline?
7:42:46
axion
I have written one, but I cannot work through the edge case that is the syntax for &key arguments in an ftype proclaimation
7:50:29
axion
The problem is I want to inform the DECLAIM of the type of the keyword arguments in the form they are expected in such as: &key (:min single-float) (:max single-float)
7:51:47
Bike
this is supposed to mean that the argument is called out-vec, the key arg is :out-vec, the default value is 1, and it's typed as an "axvec"?
13:20:20
beach
Should be (documentation name 'structure) or (documentation (find-class 'name) 'type)
13:24:10
ogamita
Notice that there are macros that allows you to define classes using the same syntax as defstruct, if that's the reason.
13:26:23
axion
beach: I have been over this a few times here. It's to have typed structs, that compile down to arrays except with named slots for accessing elements.