libera/#sicl - IRC Chatlog

3:06:42 beach` ** NICK beach

3:12:35 beach yitzi: SICL is not yet using Salmagundi, so go ahead and use the main branch.

10:14:28 yitzi beach: gotcha. I've already made some progress. I've got a client based extrinsic interface with list and bucket hash tables working.

12:06:05 beach Excellent!

12:08:37 yitzi Is the code for salmagundi in SICL? Are you just not using the extracted version yet?

12:09:44 beach The latter.

12:10:47 beach The code might be identical to that in SICL, except for package names and such.

12:10:57 yitzi Gotcha

12:11:03 beach In other words, I haven't done any real work on it.

12:13:25 yitzi Do mind if I use lower case directory names? Mixed case source names create a lot of entries in the logical pathname translation tables.

12:13:41 beach No, go ahead.

12:13:44 yitzi thx

12:14:15 beach Not that I understand why more entries would be created.

12:17:29 yitzi When you package a CL like Clasp you need to embed source code references for functions, etc. Its easier to use logical pathnames for those versus physical pathnames. Physical pathnames recorded in an executable or packaged software will often be tagged as a security risk. ....

12:18:55 yitzi Every physical path that contains characters not permitted in logical pathname or mixed case on file systems that are case sensitive end up needing a translation because of the limitations of logical pathnames.

12:19:23 beach I see.

12:19:55 yitzi Its not a big deal. In Clasp we auto generate the translation table. I just don't see the reason to add to it unless for a good reason.

12:20:04 beach Another reason to include the source code in the image as I plan to do for SICL, rather than referring to file names.

12:21:02 yitzi Don't get me wrong. I think logical pathnames are pretty cool. I just wish they were case preserving.

12:21:43 beach I understand.

12:28:12 beach What reason does Clasp have not to include source code in the image? I already showed by a back-of-envelope calculation that the memory used by the source code is minimal.

12:29:34 beach Including the source in the image makes sure the source is the exact one that was made to create the resulting executable code.

12:31:08 yitzi We ship the source code outside the image. Memory isn't a concern. Clasp is also C++ and it mixes Lisp and C++ source code references. So much of the debugging source code references are to C++ locations.

12:31:42 beach I see.

12:32:27 yitzi But I agree with you in general about including the source code.

12:32:43 beach Thanks.