freenode/#sicl - IRC Chatlog
Search
15:23:37
ck_
everything I've been saying was an attempt to brighten your mood. It could be so much worse... Sorry that I couldn't communicate my point more clearly
15:24:01
splittist
(I think I'm old enough to remember when Data Processing was a name for the whole field of endeavour.)
15:24:01
heisig
I try not to work myself up about "Next Generation CL" anymore. Most proponents of such a thing maintain zero implementations, so they will face the same fate as R6RS.
15:24:51
beach
ck_: Thanks! I am better already. I am going to take a break for a sauna. That usually fixes many things. Back in 20 minutes or so.
15:31:31
shka_
I think that the thought process of "libraries make programmers productive, so the best language is the one that makes libraries programming the quickest and easiest" is completely logical
16:03:59
jackdaniel
all that said, it would be cool if cl had (possibly optional) standardized protocols for threading, networking, unicode and (of course) mop; but it is not a pressing issue given all points are addressed by vendor modules
16:17:17
shka_
on the other hand, if cl had threading and networking from the day 0, it would likely be obsolete by now
21:45:42
no-defun-allowed
Re-reading the document, I wonder if they've investigated what assumptions the compiler writers make, and what is idiomatic Common Lisp.
21:46:53
no-defun-allowed
e.g one should basically never have to write SLOT-VALUE, so foo.bar syntactic sugar is just encouraging one to write bad code, and RAII (oh, why the hell are we suggesting RAII and manual memory management in the new standard now?) and continuations probably would not mix.
21:53:53
no-defun-allowed
We either already have "first-class macros", as you can grab the macro function and pass it around, like any old object, or by Matt Might's definition, it would be non-trivial to modify a compiler to implement them efficiently. And finalization is usually a last-ditch effort for handling remote resources; I wouldn't bother. And the high performance socket stuff is definitely _not_ using BSD sockets, so I hope we don't