freenode/#clim - IRC Chatlog
Search
17:12:33
beach
karlosz: What parts of SICL are you thinking of adding? I would think the most useful part would be a Cleavir-based compiler, but perhaps you are thinking of some other things? A simple Cleavir-based compiler should not be too much work, but it would be wise to consult with Bike and drmeister to find out exactly what needs to be done.
17:27:14
onion
how come there is no macro being used here? : https://github.com/robert-strandh/CLIMatis/blob/master/X11-colors.lisp ^_^
17:30:09
onion
which could also have written the macro , and (use-the-macro '((black 0.0 0.0 0.0) (snow 1.0 0.98 0.98))) that makes (defconstant +SYM+ (make-named-color SYM VAL)) for each elem..
17:32:34
jackdaniel
and what would be the gain? a little more complicated sed/awk script for no real benefit (imho)
17:33:51
jackdaniel
(I mean - we all know macros, sure, but this is not code which is shared across basically anything, and having macro for a sake of having a macro and shaving a few bytes isn't very convincing)
17:40:03
jackdaniel
I think it boils down to the question what is the code and what is an intermediate representation
17:45:45
onion
heh why bother ? the original rgb.txt is a lot more simpler, why not just read that in directly ? just add sed and awk *and* cl to it... ?
17:46:35
beach
I for one would like to use it for an OS that does not have sed and awk. Perhaps the Mezzano people feel the same way.
17:48:05
onion
that would make sense. can't rgb.txt be parsed easily with CL? rather than also keeping another copy of it, say if the file gets out of sync for whatever reasons
17:50:51
beach
nyef: By the way, the partial inlining paper was accepted. And thanks to you, one of the referees remarked on the "elegant proof of correctness".
18:08:56
karlosz
beach: since the goal of gsoc is to have a deliverable by the end of the smmer, im thinking of splitting the work into achievable goals
18:09:21
karlosz
i know that getting the modular library functions like the sequence functions would be pretty easy
18:11:00
karlosz
i think that type informed optimizations would be very useful to have, since clisp doesn't have any
19:23:34
beach
karlosz: Sorry, this is the time of day that I spend time with my (admittedly small) family. And today was exceptional, because I had my favorite author over for lunch and work on our articles.
19:27:44
beach
karlosz: In order to answer your questions, I probably need to discuss details about how CLISP is implemented, and that might take some time.
19:28:20
karlosz
beach: that is fine. i am mostly trying to pitch the proposal with the clisp people at the moment
19:29:22
karlosz
by the way, i contributed to sicl eons ago, so i think i can find my way in the meantime :)
4:10:55
jack_rabbit
hmmmm.... Does the clim copy/paste stuff include a "copy from clim" functionality?
4:12:16
jack_rabbit
I don't understand X selection ownership stuff that well, but It looks like when you make a selection, XLIB:SET-SELECTION-OWNER is called. I thought that did the trick for creating a past-able thing.
4:12:41
jack_rabbit
I can select things, and paste things into mcclim, but I can't copy *from* mcclim.
4:23:42
loke
I'm trying to render a mathematical fraction. I have an output record representing the top part, and and other output record representing the bottom part. I now need to render the top part, centred, as well as the bototm one, with a line between. Sounds simple, and I've managed to figure out how to get the dimensions of the output records so that I can compute the coordinates for centering.
4:27:16
beach
loke: The way you do this is to go to the bauhh site, type output-record in the apropos window, and then look at the list. You will then see (setf* output-record-position), Generic Function.
4:27:49
beach
loke: I am perfectly willing to look it up for you. But I am telling you so that you can do it when I am not around.
4:29:54
loke
Even if I could, I likely wouldn't have found it, since I didn't realise the position was a propery of the output record itself. I thought you painted an output record at a given position, thus I assumed that the STREAM-ADD-OUTPUT-RECORD function would have a :POSITION parameter or something to that effect.
4:34:53
beach
:x-position :y-position ... All subclasses of either output-record or displayed-output-recrod must handle these ... initargs. So you are right, the position is not a property of the stream it is contained in, but of the output record itself.