libera/#clasp - IRC Chatlog
Search
14:03:08
kpoeck
::notify drmeister: I found the source of my problem compiling with c++20. It is in boost format, specifically here: https://github.com/boostorg/format/blob/b849028e5ea79ad46c2f8a1d88c9e5512c1f1a97/include/boost/format/alt_sstream_impl.hpp#L41 . The allocate with two parameters is undefined in c++20, see
14:03:08
kpoeck
https://en.cppreference.com/w/cpp/memory/allocator/allocate . This is long fixed in boost, but not in the version that came with my distribution. I corrected the 4 calls to allocate and it now compiles fine
14:05:35
yitzi
kpoeck: Do you know if the ANSI tests do anything in regards to logical pathname upper/lower case testing?
14:06:52
kpoeck
::notify drmeister: But now I have trouble with asttooling::AstVisitor_O. Seems to have been removed in commit c41691edbd3ef8d5f9ba535f9c50e32defbce63b , but seems still be referenced in clasp_gc.cc. Do you perhaps have a locally modified copy of clasp_gc.cc?
14:08:37
kpoeck
yitzi don't know, be will check. I have often been bitten by the limited chars that are allowed in logical-pathnames
14:11:09
kpoeck
Doesn't seem so, nothing in https://gitlab.common-lisp.net/ansi-test/ansi-test/-/blob/master/pathnames/logical-pathname.lsp
14:11:41
yitzi
Yeah, its just weird b.c. CLHS 19.3.1.1.7 seems to imply that namestrings in logical pathnames are upcased. All implementations appear to do this except CCL which preserves case. That is why I was wondering if the ANSI tests check this.
14:17:24
kpoeck
I don't think you misread that. I also thought that not all characters are allowed, but can't find that section now
14:18:57
kpoeck
See https://franz.com/support/documentation/current/doc/variables/excl/s_additional-logical-pathname-name-chars_s.htm
14:19:30
kpoeck
As specified by the ANSI spec, words in logical pathnames must consist of alphabetic characters, decimal digits, and the minus sign. Not allowed are characters such as underscore (#\_)
14:23:00
kpoeck
The section is https://franz.com/support/documentation/current/ansicl/subsecti/syntaxof.htm
14:23:53
yitzi
Yeah, CCL seems really weird. Like it preserves case in translate-logical-pathname also. Maybe just ask over in #ccl sometime. Maybe there is a reason for it.
14:24:54
specbot
Syntax of Logical Pathname Namestrings: http://www.lispworks.com/reference/HyperSpec/Body/19_ca.htm
14:25:10
kpoeck
In your clasp enviroment, which version of python do you have? I have errors in waf starting python 3.8
14:26:11
yitzi
On arch I have 3.9.1 ... but I haven't built for a while. What errors are you getting?
14:30:31
kpoeck
I have to switch back to python3.8 to reproduce the error. Happened with ./waf configure.
14:47:25
drmeister
I'm working with bike's changes to the scraper to integrate them into clasp - that changes how we deal with clasp_gc.cc
14:47:47
kpoeck
https://github.com/clasp-developers/clasp/blob/main/src/main/clasp_gc.cc is 28 days old
14:48:31
drmeister
Because I have a new one being generated in the 'scrape' branch and I'll backport that to the 'main' branch.
14:50:33
drmeister
Is it allowed to preserve case when translating logical pathnames to physical pathnames?
14:54:39
yitzi
Downcasing in translate-logical-pathnames appears to be implementation dependent according to CLHS.
14:55:11
yitzi
Keep in mind this was only a discussion about CLASP vs CCL. CLASP is just fine in its behavior.
15:02:11
yitzi
drmeister: I am now using those ubunto clasp packages in my CLJ testing on GitHub actions to test PR, etc. Just thought you'd like to know.