freenode/#lisp - IRC Chatlog
Search
20:17:48
pve
aeth: I'm not tackling the smalltalk standard lib anytime soon.. currently I'm at "smalltalk syntax with CL machinery", so I basically wrapped many (most?) of the standard CL functions
20:28:39
pve
aeth: I'm going to upload the code to github soonish, but if you're interested, here are a couple of pictures I like to show people that hopefully give an idea of the current state:
20:31:39
pve
Just finished writing the indendation code for the emacs mode, which was much harder than I expected. I'm not ashamed to admit I spent waay to much time fiddling with it.
20:34:48
aeth
pve: So how do you get the interactive, image-based Smalltalk development environment that Smalltalk is famous for?
20:36:39
aeth
pve: I haven't done ASDF integration yet but I've probably lost a few days every now and then trying
20:38:37
aeth
it looks like you do everything in a [ ... ] reader macro, though, while I am trying for a slightly different technique, essentially trying to make the .scm files indistinguishable from ordinary Scheme files.
20:38:51
aeth
(and it has to have a custom reader, since there are minor points of syntactic incompatibility)
20:44:27
pve
I tried to make the asdf integration optional though, so an app/script is loadable without having to make an asd file
20:45:02
aeth
For me, ASDF integration is pretty mandatory afaik because that's the logical way to handle Scheme libraries, beyond just using packages.
20:56:35
pve
aeth: when you say "asdf integration" do you mean being able to do (asdf:load-system "my-scheme-lib")?
21:00:35
aeth
pve: maybe, but more importantly, actually handling the Scheme libraries as ASDF systems, e.g. https://gitlab.com/mbabich/airship-scheme/-/blob/master/scheme/base.sld
21:01:40
aeth
Notice how R7RS's define-library seems to cover both DEFPACKAGE and DEFSYSTEM in scope... In this case, (scheme base) could represent an underlying package scheme/base (or airship-scheme/scheme/base) and an underlying system airship-scheme/scheme/base
21:03:19
aeth
I could probably extend it to add declarations for description/version/author/maintainer/license/homepage/bug-tracker/source-control and make it map to DEFSYSTEM more clearly
21:03:39
aeth
It can also have (include "foo.scm") in the definition, which basically maps to :components
21:10:35
pve
i mean that with that code, the custom asdf components can be used in asd-files (in the second imgur picture, top right)
21:12:11
aeth
right, afaik, I would just have to parse (include "foo.scm") as defining a Scheme source file component, with the main complication being something like (include "bar/foo.scm") and other than that, everything cleanly maps either to DEFSYSTEM or DEFPACKAGE
21:16:15
aeth
The hard part might be getting Quicklisp to detect them as systems without (1) being a top-level .ASD file and (2) being a .ASD file at all, but package-inferred-system exists as a thing that creates an ASDF "sub"system for each file and it works fine, so there's probably a way to do it from the top level .ASD file
21:17:55
aeth
I've always seen it as defining a new thing... "module" or something? For each subdirectory.
21:18:34
aeth
it definitely does something fancy when package-inferred-system is being used, though, since it's all... inferred from names that match the paths
21:19:23
aeth
yeah, sorry for being unclear, I mean, I've never seen (:file "bar/foo") I've always seen it as defining something for "bar" and then putting "foo" under it
21:23:00
pve
yeah, usually the :module component is used when you have a subdirectory containing some code
21:26:59
pve
but did you know that asdf automagically looks for the definition of teh system foo/bar in foo.asd?
21:28:07
phoe
wait a second - in ASDF, (:file "foo/bar/baz/quux") means quux.lisp in a directory subtree foo/bar/baz/
21:37:54
aeth
pve: well, not quite, since that's one-system-and-package-per-file, while Scheme's library system is closer to "normal" CL, where you have a separate file listing all of the files to include
23:15:37
Fare
If sharks^WIP lawyers smell enough money to go after a new CL standard, we've already won.
23:16:23
Fare
At best they'll get us to rename the project and do a clean room rewrite. But they only would do that if there's a big enough community for the thing to matter.
3:11:08
Oladon
I've created an executable with SBCL's save-lisp-and-die, but am getting an "Internal error" and dropped into ldb as soon as I run it. Could someone help me debug? Error is: Internal error #11 "Object is of the wrong type." at 0x5297650a
3:50:55
Oladon
In case anyone cares, looks like the issue was https://bugs.launchpad.net/sbcl/+bug/1857920 -- upgrading to 2.0.7 fixed it
3:57:53
Lycurgus
there's a note on sbcl 2.0.6 that sb-mop and sb-pcl will in future no longer export defined symbols
3:58:51
Lycurgus
is that supposed to be inocuous because if you are using the defined functional protocol you don't need access to the symbols?
4:06:44
Bike
it says they won't be exported from sb-pcl. presumably they'll still be exported from sb-mop.
5:10:04
brettgilio
Hey. I am trying to use M-x slime-load-system, and it is returning me with this issue: Error (MEMORY-FAULT-ERROR) during printing: #<SB-INT:SIMPLE-READER-PACKAGE-ERROR {1003D5DDC3}>
5:30:35
beach
I mean, is this immediately after starting SBCL, or did you load some other stuff first?
5:31:56
beach
I see. And does it happen also when you load the system from the REPL, as opposed to going through SLIME?
7:10:39
VincentVega
Good day, all. I am having this really basic problem trying to access a struct field in a tree from the spatial-trees package. Here is a program and all the details, would be glad if someone could help: https://pastebin.com/p5QCCiWD
7:12:11
beach
Apparently, you are not supposed to use LEAF-NODE-ENTRY-DATUM, since it is not external.
7:13:09
beach
But if you know what you are doing and you want to use it anyway, do SPATIAL-TREES-IMPL::LEAF-NODE-ENTRY-DATUM with two colons.
7:18:19
VincentVega
beach: with two cols I get the error "The value ... is not of type SPATIAL-TREES-IMPL:LEAF-NODE-ENTRY" (strangely enough)
7:23:04
beach
But you are not supposed to use non-exported symbols, so I am guessing you are not using the system correctly.
7:32:47
phoe
brettgilio: memory fault errors shouldn't happen; which system is it, and does it also happen in newer SBCL versions?