freenode/#lisp - IRC Chatlog
Search
8:47:55
beach
I am guessing that tools like that are going to turn out to be invaluable for debugging pane hierarchies. At the moment I just use Clouseau on the application frame, but that is quite a tedious technique.
8:49:59
jackdaniel
I've already found some bugs thanks to that (because it is easier to "see" the problem than deduce it)
8:50:49
jackdaniel
person with enough time could hack it into something for prototyping clim application layouts too I suppose
9:03:51
blisp[m]
Lol that reminds me of a quote from Pineapple Express. Have you ever seen the back of a dollar bill man well have you ever seen the back of a dollar bill on weed
9:05:02
Shinmera
SBCL, CLISP, and LispWorks also work, but aren't available as apps, as far as I know.
9:07:29
blisp[m]
Im just curious is there are any FreeBSD users in here you know why there's no clisp in ports
9:09:16
blisp[m]
Well honestly no real reason just that I started with it and I was surprised to see that it wasn't there
9:13:29
blisp[m]
Beach, what's the status of your list OS is it working well enough to provide any significant advantage over a non list OS especially for doing tasks that lisp was made for? And lastly what's the chances that it would support something like opencl?
9:14:19
blisp[m]
Are you still wanted to be super purist I would just write my own opencl implementation in lisp but I don't like to reinvent the wheel all the time
9:16:46
blisp[m]
Weird so I thought mezzano was yours. Steven looks like it's under active development
9:17:25
blisp[m]
I remember you telling me many years ago that you were riding a common list operating system I was asking about that
9:59:14
pjb
blisp[m]: clisp runs on FreeBSD. That the FreeBSD people don't care for making a clisp package is their problem. You can just fetch the sources of clisp and compile it on any system you care to use.
10:19:08
Pierpa
Afaiu, LW sells a runtime for Android and then a regular LW can deliver apps for it. It's not a development system which runs on android.
10:45:16
Younder
Ubuntu is boring, but well maintained and reasonably secure. I like Qubes OS, but the lack of NVIDIA support is unacceptable to me.
12:08:23
Younder
1200 EUR for a Hobbyist LispWorks edition witch you can't use commercially, has no maintenance and no service.. These people need a reality check!
12:12:42
Younder
Now you pay 1400 EUR for a professional version for which you have at lets a chance to make the money back. It they had sold the Hobbyist version for 200 EUR, then a hobbyist decides to take the product commercially and pays 1200 EUR ekstra for that, now that would make sense.
12:14:51
Younder
Shinmera, It is not like other company's charge that much. They seem stuck. They sell in small quantity so the need to charge a lot. Because of their high price they don't make many sales. Catch 22
12:27:08
Shinmera
You don't know their audience, their sales, their structure, nothing. You're an outsider.
12:30:22
pjb
Younder: if you compare the price/features of MoCL, I would say that Hobbyist LispWorks Ed is worth it.
12:49:28
beach
ebzzry: It would be very strange if there were a channel on Freenode dedicated to a commercial software product.
13:24:42
Younder
phoe, yeah, old, faithful, professional customers. Their product is after all quite good.
13:41:35
Pierpa
There's software which costs 500000 EUR per seat, it's much simpler than a cl development system, and which I suspect that sells more copies than lw...
14:11:40
__Myst__
Can you provide an example? For some reason, I have the conception that most things in LISP are immutable.
14:12:15
__Myst__
I'm obviously not trying to get 100% semantics because that would be hard + this is just a toy project
14:13:40
random-nick
what happened with the person that was writing a Common Lisp interpreter as an assignment?
14:16:14
minion
__Myst__: look at pcl: pcl-book: "Practical Common Lisp", an introduction to Common Lisp by Peter Seibel, available at http://www.gigamonkeys.com/book/ and in dead-tree form from Apress (as of 11 April 2005).
14:16:16
__Myst__
Is there a good guide on the "internals" so to speak of CL so I can better learn this stuff?
14:16:17
Younder
Reading up would help. 'List in small pieces' by Quinnec covers design of scheme and lisp compilers and interpreters.
14:17:15
__Myst__
Might be interesting to first implement Scheme then once I got a proper version of that try CL
14:18:46
Shinmera
beach: Unfortunately quite a few people stumble in here thinking that it is in fact not monumental :/
14:19:57
random-nick
the only thing that might be difficult about scheme is closures and continuations
14:20:30
Shinmera
__Myst__: You might also be interested in MAL, though it is off-topic here. https://github.com/kanaka/mal
14:38:07
stacksmith
In terms of a technical challenge (as opposed to the drudgery of all the loose ends and the sheer volume)
14:44:58
jackdaniel
regarding full-blown continuations it is the fact that you store execution state as data
14:47:04
puchacz
hi, it does not feel right to use (format s "~a" it) to print character by character to a stream, where s is inside (with-output-to-string (s)....)
14:47:24
puchacz
I am sure there is something like print-character that does not print #\space but actual space
14:48:27
beach
stacksmith: There have been no surprises so far. But the hardest part is definitely the organization of the compiler so as to obtain good performance.
14:49:32
pjb
you can write a simple CL compiler easily enough, if you target a lisp VM. Take for example clisp. The compiler is a single source file.
14:52:35
stacksmith
beach: have you looked at Self? There were some nice ideas there, in-line polymorphic caches and such. At the time code size was troublesome, but that's not an issue anymore...
14:53:00
beach
stacksmith: I am aware of Self, but haven't studied the specific compilation techniques in depth.
14:53:25
beach
stacksmith: Yes, I am betting that code size is no longer a problem in order to simplify the compiler.
14:53:45
stacksmith
The polymorphic caches could accelerate dynamic dispatch, and they are pretty simple.
14:54:12
beach
stacksmith: I already invented a dispatch technique that is now used in Clasp, and SICL.
14:57:52
beach
This paper describes the nursery collector, in case you are interested: http://metamodular.com/sliding-gc.pdf
15:00:35
shka
i guess, so, haven't been in touch with academic publications ever since i finished master degree
15:01:07
beach
But ideas tend to come automatically when one works with a problem for a long period of time.
15:02:09
shka
recently i attempted to help my colleague with his thesis, and oh my god, he had like huge stock piles of papers all from circa 0.5 IF journals
15:03:14
beach
shka: True, there is a lot of bad writing out there, as Steven Pinker correctly points out.
15:06:36
beach
Some of them are bad, even though they took considerable effort to write. Again, as Steven Pinker points out. :)
15:07:43
beach
stacksmith: Oh and the other VERY HARD part is bootstrapping. I will figure it out eventually, but it is taking a lot of time.
15:11:59
stacksmith
Bootstrapping is always an issue... I think SBCL fork was largely about that - and look at the mess today.
15:12:37
beach
That is definitely what SBCL was about. I am trying to take things one step further by not using any C code at all.
15:17:35
beach
By using first-class global environments, I am hoping to avoid the technique that SBCL uses of renaming the packages. And by bootstrapping from a full Common Lisp, I can use the CLOS machinery for stuff that would otherwise require special code.
15:22:48
beach
Like, I can write (defclass symbol (t) ((%name ...) (%package ...)) :metaclass built-in-class)
16:01:47
drmeister
I want to define a type... (deftype molecule-type () '(member protein ligand ion solvent))
16:02:54
drmeister
I have a property-list slot in my MOLECULE class and I want to set the :TYPE property that way. That will lose type info.
16:03:59
drmeister
And not rely on a property list for something fundamental like this that can have one of a limited set of values.
16:23:21
drmeister
I think we are gonna want one for C++ methods. Or we have something to define reader, writer and read-write accessors.
17:10:33
jsjolen
Hi! Is there a way to check where a Quicklisp provided system comes from? (I want to know if a particular system is from a fork or the original author)
17:11:05
jsjolen
I tried inspecting objects returned from ql:system-apropos-list but I didn't find the relevant data
17:13:16
Bike
hm, i don't know how to do it automatically, but it's all in https://github.com/quicklisp/quicklisp-projects/tree/master/projects
17:22:18
puchacz
I am getting error on this source: 0: [RETRY] Retry compiling #<IRONCLAD-SOURCE-FILE "ironclad" "src" "public-key" "ed448">.
17:34:18
Shinmera
Probably because keywords are usually reserved for either key-value pairs, or for specific tokens of their own. Lambda list keywords are markers of a different kind of structure.
17:47:32
puchacz
st00pid compiler..... I changed #() to #.(make-array 0 :element-type '(unsigned-byte 8)) and it works
18:13:05
stacksmith
Sanity check: I am considering writing a with- macro that creates an environment for dealing with a complicated data structure. I was considering swinging in the package native to it with (use-package) for the body... Am I asking for trouble?
18:16:24
stacksmith
Is there another way to do this? It seems reasonable to not have to type the package over and over inside an environments made specifically for that task...
18:19:44
Pierpa_
Your macro could substitute symbols in whatever package with other symbols in the correct package?
18:22:01
stacksmith
Actually not too bad, because I can use the same symbols in different environments for different structures that require similar treatment... Kind of generic protocol...
18:22:08
Shinmera
I wrote a library that does something like that. https://github.com/Shinmera/deferred
18:23:15
stacksmith
If I had a penny for every library I wrote that I never ended up using, I'd have not quite enough for a cup of coffee.
20:01:10
jcowan
I have heard it said that compiler macros are a Bad Thing (or at least do not deliver on their apparent promises), but I can't find the argument now. Does anyone have an idea where or who?
20:10:56
bjorkintosh
jcowan, is it this, perhaps? http://www.mschaef.com/blog/tech/lisp/defmacro-coupling.html
20:12:24
jcowan
bjorkintosh: I'll read that in detail, but I do remember it was specifically about define-compiler-macro, not defmacro in general.
20:16:31
loginoob
is there something in emacs so that i can rapidly access online documentation of any lisp function or variable with few keystrokes?
20:17:39
bjorkintosh
loginoob, are you already aware of this then? https://common-lisp.net/project/slime/doc/html/Documentation.html
20:18:28
loginoob
bjorkintosh: aware but never read it because its been only a week since i started learning lisp