libera/#commonlisp - IRC Chatlog
Search
13:47:40
Guest74
drmeister: while the error is annoying, it seems to make logical sense, given the CL abstraction for pathnames, as dot files are singular.
13:49:31
drmeister
It sounds like there is a thought process behind what you said and I'd like to understand that.
13:49:48
Guest74
there can be many txt files but there is only one .sbclrc. So it make sense that .sbclrc is a name and not a type.
13:53:25
Guest74
actually, I really wish all implementations stored device information in pathnames.
13:57:11
drmeister
Guest74: Your point is that with pathnames `:type` is supposed to indicate a type of pathname and that doesn't quite fit with dot files being singular.
13:59:55
drmeister
In ecl `(namestring (make-pathname :type "clasprc"))` returns NIL - clasp copied that behavior until yesterday. I changed clasp yesterday to return ".clasprc" because I interpret the pathname-type as more of a pathname-"extension". I see your point however.
14:00:45
drmeister
It appears that I am not violating the Common Lisp specification - this is implementation dependent behavior.
14:02:21
drmeister
This came up because we tried to define the RC file using the logical pathname #P"home:.rc" and it didn't work.
14:04:42
Guest74
This is definitely one of those wscl things. It's hard to work with an abstraction that nobody can agree upon.
14:05:44
semz
Agree. I like the idea behind pathnames a lot but they end up rather awkward in practice because of this.
14:40:58
mfiano
Ugh, yes. Pathnames are awkward to work with at times. I usually use UIOP's abstractions just to have some common ground to work with. Too much implementation-dependent behavior and other gotchas that are better, though far from ideal, using UIOP.
15:36:51
minion
danisanti: please 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).
15:51:19
beach
danisanti: You can ask questions here too, but if they become too basic and too numerous, you will be directed to #clschool. But some basic questions are tolerated here.
23:35:41
dbotton
what is the best way to tell sbcl that on error to no debug but also not exit either?
0:33:52
White_Flame
dbotton: --disable-debugger is a cmdline option, but I think it will probably still exit. Where would you want it to execute from after printing error/stack?
0:35:37
White_Flame
but you say "I don't want to stop running", would you just want to hang or what?