libera/#commonlisp - IRC Chatlog
Search
3:08:28
beach
1. As jackdaniel pointed out, there is unfortunately a lot of aversion against GPL-like licenses, and it seems to be very bad in the Common Lisp community.
3:08:32
beach
2. I want SICL modules to be used by other implementations, no matter what license those implementations have chosen to use.
3:08:33
beach
3. Code like that of SICL is not unique in that other code bases do the same thing, so there is less need to protect it. I think the FSF has some special exceptions for language processors.
5:41:16
kakuhen
for instance, you will see a lot of calls like (ensure-directory-pathname "ccl:foo;")
5:41:33
kakuhen
is this some relic from the classic mac os days or is there something meaningful with this convention?
5:44:23
specbot
Syntax of Logical Pathname Namestrings: http://www.lispworks.com/reference/HyperSpec/Body/19_ca.htm
5:48:35
kakuhen
That seems correct, but I'm not entirely sure. In the function CREATE-IDE-BUNDLE, for instance, you have a string SOURCE defined as "ccl:cocoa-ide;ide-contents;". This corresponds to .../ccl/cocoa-ide/ide-contents on my actual drive.
5:50:55
conjunctive
Hello, has anyone worked with lisp-binary? Trying to understand how I should represent padding in this DSL.
6:55:05
kakuhen
Doesn't this break the standards? The hyperspec states the function "determines the pathname that corresponds to the user's home directory on host," but CCL always ignores the host.
7:43:30
pjb
kakuhen: note that this is not pathname hosts, but network hosts. Since there is absolutely nothing specified making the link between pathnames and network, it really lies entirely into implementation specific domain.
7:46:00
pjb
kakuhen: but even assuming an implementation that would deal with some kind of network file system. With most network file system in use nowadays (say, NFS and Samba, possibly various cloud FS, such as DropBox, iCloud, etc), you don't get to choose on what host your user-homedir-pathname is on. This is the local system that decides, and your home path is always relative to the local file system, even if it's remotely mounted.
11:59:25
pve
Hi, can someone speak about how systems were loaded in CL back in the day? I know there was MK:DEFSYSTEM, but was it used right from the start, or did people just have ad-hoc solutions before it emerged? Did lisps before CL have their own defsystems?
12:00:41
xach
pve: i've seen a number of old projects with a file named something like load.lisp that has a script that loads the software.
12:01:21
Duuqnd
I know Symbolics had their own DEFSYSTEM thing so I'm guessing before ASDF there were lots of DEFSYSTEM implementations.
12:03:49
jackdaniel
the standard mentions (as deprecated) interfaces require and provide that are meant to load "modules" (whatever that means :)
12:04:40
mfiano
I remember using something like clbuild (?) or something or another before QL existed/was popular
12:05:02
xach
clbuild was a way to get things - it didn't introduce a new way to things, it used asdf
12:05:07
jackdaniel
so this is deprected in its inception mechanism for loading programs composed of multiple (or one) files
12:05:55
jackdaniel
there was also sbt that was part of ecl at some point of time (years before I've used it)