freenode/#lisp - IRC Chatlog
Search
5:57:41
drmeister
(ql:quickload "something" :verbose t) doesn't produce an error - and it doesn't provide any more info.
6:29:50
bjorkintosh
I wondered if he was using the C part or the Template or the OO bits or these days, even the functional part
6:30:34
jack_rabbit
bjorkintosh, My favorite joke has become that C++ is now functional, but just barely. ;)
6:30:57
jackdaniel
drmeister: that'd make a good urban legend: programmer starts debugging particularily hard bug -when he's done and comes out of his basement nothing is the same, he can't recognize anything from both real and virtual world
6:33:18
jack_rabbit
bjorkintosh, unfortunately, if history is anything to go by, both C++ and Java will probably continue to bolt semantics for whatever the latest trend is.
6:35:12
bjorkintosh
archivists will one day simply have to look at the different c++ versions to determine what the cutting edge in computer science was.
11:04:58
Shinmera
Does anyone have a collection of implementation-dependent tests to determine whether a symbol denotes a type? I know how to test for conditions, structures, and standard-objects, but not types otherwise.
11:50:47
Bike
that's difficult. implementations can vary which types are also classes, and how they do type macroexpansion, and so on
12:00:13
Shinmera
I need it in order to determine whether a type-definition should be emitted in my documentation system.
12:00:35
Shinmera
Bike: Right. I don't even need to type expand though, just to know whether a symbol names a type at all.
12:01:44
Bike
it sounds like you only need to know about user deftypes, in which case typexpand would do it
12:01:53
beach
It sounds like it would be a very useful library to have. And it would include TYPE-EXPAND.
12:02:34
Bike
https://github.com/Bike/introspect-environment/blob/master/ccl.lisp#L82 all internal symbols and shit too
12:03:53
Shinmera
pierpa: subtypep is a much more complex operation than simply testing whether a type exists.
12:09:28
Bike
it doesn't mention any errors, it just says the arguments are type specifiers, which means using non type specifiers is UB, rather than defined to be an error
14:26:57
k-stz
puchacz: if you check out the sbcl source, the exit-code is just a slot in a "process defstruct", which is nil on initilazation. The code also looks easy to understand at first glance