freenode/#lisp - IRC Chatlog
Search
15:17:59
beach
aindilis: For example, I just saw a recent paper by Adams on reading and writing floating-point numbers. There have been work in the past, but this one claims to be much better. Now every Common Lisp implementation needs those routines.
15:18:01
beach
But you can be sure that most implementations use their own code, perhaps their own technique as well, and possibly even a technique that is not as good as the published ones.
15:18:57
beach
So taking those articles, writing portable Common Lisp code with the techniques, comparing them and making the code available, would make it possible for many Common Lisp implementations to use this code and avoid duplicate maintenance.
15:21:20
aindilis
ah, now I understand, with the number of different versions of CL out there, you have this problem. I come from Perl originally so we didn't have that problem
15:22:41
aindilis
for instance, I heard it can be hard to get things running on SWI-Prolog to run on other Prolog, another language which has this kind of fractionalization
15:22:57
beach
They all have their specificities, but something like reading and writing floating-point is typically done in portable Common Lisp code.
15:24:32
beach
CLISP is written in C and uses a bytecode interpreter which makes it very portable but not that fast. ECL compiles to C and interoperates with C very easily. SBCL generates fast native code, CCL has a fast compiler. Clasp interoperates with C++. etc etc.
15:27:29
beach
The only way I see to fix that problem is to make sure that the new thing is faster, more portable, better documented, better tested.
15:46:42
pjb
I have an idea, let's write what we work on in a ~/.plan file, and let's the finger command fetch and dump this file…
15:49:08
ck_
hold on not so fast I need to copy this down -- "let's ... the finger ... command fetch and dump the file" ok got it
15:49:33
ck_
will proceed with this plan but I will make a feint to the north-east first I'll surround them
15:49:59
pjb
aindilis: there's the notion of conformance in CL. This is stronger than portable. Portable, is only a potential. conforming is definitive.
15:50:34
pjb
aindilis: If you write conforming code, then it is guaranteed that it will run the same in all conforming implementations. No work to do, no porting of portABLE code, or whatever.
16:13:06
Xach
My cron job failed last night, but not to worry, it's because a lightning storm knocked out power. time to get another ups...
16:20:45
ck_
Xach: I just read your conversation with a scammer. Wonder why they're all called Solomon.
16:31:36
ck_
ah, good news -- githubstatus.com says 'error rates have dropped'. I guess the levees are holding.
18:13:35
decent-username
Hi, does someone of you know how I could disable the quoting behaviour of paredit in Emacs? Right now when I type a backslash character it will quote the next key stroke, but I just want a simple backslash character.
18:17:03
ck_
decent-username: \ is probably bound to paredit-backslash. Bind it to self-insert-command or remove the binding to get the behaviour you're looking for
18:23:48
Xach
C-q <anything> will insert that thing rather than going through fanciness, it's a generic emacs feature.
18:24:09
decent-username
I'm not an elisp hacker, so I have no clue how to rebind keys. I just started writing some function for the paredit mode hook.
20:57:51
Guest5703
I'm wondering where it comes from, there seem to be references outside emacs lisp.
21:02:51
zhlyg
Gah, wrong terminal again.. did obarray provide a mechanism for symbol specialization?
21:08:05
housel
REMOB corresponds to http://www.lispworks.com/documentation/HyperSpec/Body/f_uninte.htm
21:20:02
zhlyg
housel: yes of-course, the symbols value vs its reachability/existence. Anyhow, thanks for the link. Those pre-CL lisps really seems to be the origin of the obarray concept.
21:22:32
zhlyg
Interesting style, is it to get temporary reachability of the special symbol X? (LET ((X ...)) ... (MAKUNBOUND 'X) ...) ;bad style
21:23:25
housel
https://www.dreamsongs.com/Files/HOPL2-Uncut.pdf page 12 says that before 1971 it was a list (and thus OBLIST)
21:28:37
zhlyg
housel: wow! thanks for digging that up! So the name is most probably a short for object-array.