freenode/#lisp - IRC Chatlog
Search
19:29:38
pve
charles`: you might want to investigate using readtables instead of clobbering cl:eval, if you're going to pursue that further
19:42:01
charles`
pve: I'll look into it, but I wouldn't call it clobbering; it is more like a thin wrapper that calls the original cl:eval.
19:55:53
pve
charles`: I understand, but it's not something you would want to do if you intend to release it as a library.
23:02:57
Josh_2
Normally I would add a key like :pathname "src" and all my code would go in 'src' and then my files are found relative to src, however I want to have a module which contains static files, if I use :pathname isn't it going to look in src?
23:10:06
phoe
like, when you have (:module "foo" ... (:module "bar" ... (:file "baz"))) then you'll end up with a relative path name #p"foo/bar/baz" that ASDF will use to look for the resultant file
23:11:41
Josh_2
Well asdf didn't complain but I'm not sure if it worked or not because It's a :static-file
23:30:44
mfiano
Josh_2: the toplevel asdf form is itself the root module. You can use any properties in children modules.
0:03:02
charles`
I made my type-functions be able to have package local definitions as well as package local enabling, but I'm still rebinding cl:eval
0:47:13
Josh_2
If I use lists to store some config info in a file is read-from-string a safe means or retrieving it? I am pretty sure there are some 'more secure' versions around
0:57:58
mfiano
It's not going to help with READER-ERRORs, but it will mostly prevent read-time evaluation. Just don't read "1f999" or something.
1:51:05
charles`
Xach: my utility doesn't work on for compile, the compiler gives style-warnings for undefined functions (rightfully so).
1:55:40
Xach
it seems like a real challenge to implement, so i look forward to any interesting implementation ideas you may have