freenode/#lisp - IRC Chatlog
Search
21:51:01
Kabriel
I am confused why this (format t "~14,6,2,,,,'eE" -9.999999747378752d-5) => -10.000000e-05 instead of -1.000000e-04?
21:51:34
Kabriel
pjb tested this on a variety of lisps, and apparently only sbcl and abcl give the wrong answer.
2:08:25
holycow
why i run lake migrate . i get the following error: Symbol "SYSTEM-VERSION" not found in the ASDF/INTERFACE package
2:09:29
holycow
can anyone point to resources online that i can read about HOW roswell and asdf work / interact with each other or the host environment?
2:50:06
ahungry
Are you familiar with nodejs/npm at all? asdf (another system definition facility) is a way to define packages, similar to package.json in node land. Quicklisp which you didn't mention is like npm - the tool to pull in remote dependencies for asdf to load. Roswell is closest to nvm I think (node version manager) - it wraps up all the lisp stuff into a ~/.roswell directory
3:36:58
no-defun-allowed
Maybe offtopic, but what's the best practice if I want to store upwards of 10,000 binary files (addressed by hash of contents)? Filesystems usually don't perform as well as usual when you use directories with that many tiles.
3:45:09
holycow
well, i have run email servers with more files than that but they have all subdivided the attachments into subdirs
3:46:05
holycow
i am just waisting your time, my apologies. i don't have any useful information for you. i just misread your original question and was curious.
3:46:47
no-defun-allowed
You're not wasting my time; I don't even have useless information to work with.
3:53:07
buffergn0me
no-defun-allowed: You can organize the files into sub-directories named after one or more digits in the hash. Should be pretty uniform.
3:54:32
holycow
i would say it does kind of depend on how big your files are and what kind of post processing you need to do. large files will force you into the obvious answer, how many small files will give you some room to play with
5:40:06
flip214
no-defun-allowed: while 2^20 files ain't that many, having them in a single directory is a bad idea - lookup performance and all that stuff.
5:40:39
flip214
I'd suggest keeping 3 or 4 levels of 8-bit divisions, that should bring the last level down to a good number.
5:40:47
no-defun-allowed
(And, well, that SQL can be run over a network trivially, whereas a filesystem is a little less portable.)
5:44:50
holycow
there is an arch page somewhere with red sections all over warning about bugs and features that don't work properly
5:46:22
flip214
no-defun-allowed: I guess something recent will be good enough. I've had a few problems in the 4.<low digit> aera, but none since then.
5:47:11
no-defun-allowed
I do lament fallocate, but my experience with btrfs is that's a load of shite and it's been rock solid.
5:49:51
no-defun-allowed
holycow: And I did read that page five years ago and did an analysis. Still sounds quite stable.
5:51:18
no-defun-allowed
I don't use some of the advanced features like checkpointing or RAID; but is even more off topic.
5:52:40
holycow
i used to replicate datacenters geographically using zfs. i can't go back to anything less and reading that btrfs arch writeup scared teh crap out of me. i could never use anything like that.
5:57:18
holycow
i could never ever use a file system where i've read users loowing entire datasets using simple file system management tools
5:58:43
holycow
yeah, no, you are actually correct. you have to match the solution to your needs and risk comfort level
6:51:34
flip214
COMPILE returns a second and third value for warnings and errors; can I get the conditions that are signalled directly? Something like *debugger-hook*?
9:16:52
phoe
the lisp dialects are similar in the beginning, though guile is a scheme and therefore much more functional-programming-oriented
9:18:08
phoe
once you know the basics of e.g. how S-expressions work, the evaluation model, lexical environments and lambdas, however, you'll be able to apply to any Lisp dialect with none or few modifications
9:21:21
beach
phoe: Also, be careful with that kind of information. As I recall, some of the first Scheme standards did not define its operators in terms of the result of READ, but instead as surface syntax, much like other languages. So then (x . (y)) was not equal to (x y).
9:22:13
beach
Perhaps that makes Scheme different language altogether, and not a dialect of Lisp, which as we know, is not a well defined term.