Notices tagged with lisp, page 3
-
drysdam (drysdam)'s status on Sunday, 11-Nov-2012 22:32:55 EST
drysdam
!lisp = Lots of Identically Separated Parts -
arnebab (arnebab)'s status on Sunday, 11-Nov-2012 11:05:16 EST
arnebab
@rozzin #bash, !python, #ruby, #fortran and #assembler have less parentheses than #lisp. Except for python they all use the dreadful “end”… -
Joshua Judson Rosen (rozzin)'s status on Saturday, 10-Nov-2012 15:58:40 EST
Joshua Judson Rosen
I don't know of many languages that have fewer parentheses than #lisp; they mostly just have *more types of parens* and placement-rules. -
davidam (davidam)'s status on Saturday, 10-Nov-2012 08:20:11 EST
davidam
«Some joke #Lisp [means] "Lots of Irritating Silly Parentheses"; I [prefer] "Lisp Is Syntactically Pure"» → http://ur1.ca/avkk6 !emacs -
arnebab (arnebab)'s status on Saturday, 10-Nov-2012 08:08:06 EST
arnebab
«Some joke #Lisp [means] "Lots of Irritating Silly Parentheses"; I [prefer] "Lisp Is Syntactically Pure"» → http://ur1.ca/avkk6 !emacs -
salyavin (salyavin)'s status on Tuesday, 23-Oct-2012 14:56:57 EDT
salyavin
♻ @seanmcarroll: The #LISP machine at MIT, a pioneering effort in artificial intelligence. http://t.co/FXSRXrB7 !ai -
barryfm (barryfm)'s status on Friday, 21-Sep-2012 16:47:12 EDT
barryfm
@sirmacik Doesn't look very lispy to me. -
cwebber (cwebber)'s status on Friday, 21-Sep-2012 16:38:41 EDT
cwebber
Whoa, that looks awesome! -
sirmacik (sirmacik)'s status on Friday, 21-Sep-2012 15:31:50 EDT
sirmacik
What are !lisp.ers thoughts on lispyscript? http://lispyscript.com/ -
drysdam (drysdam)'s status on Wednesday, 19-Sep-2012 10:36:54 EDT
drysdam
= can take more than 2 operands but eq/eql/equal can't?? !lisp -
drysdam (drysdam)'s status on Friday, 14-Sep-2012 12:35:08 EDT
drysdam
I was hoping this was going to use tree diagrams. THAT would be both keeping the power and clearing the clutter of !lisp s-expressions -
barryfm (barryfm)'s status on Friday, 14-Sep-2012 09:58:57 EDT
barryfm
@arnebab I would rather have !lisp displayable in one's chosen syntax that have them mixed up in one language parser. -
arnebab (arnebab)'s status on Friday, 07-Sep-2012 06:51:41 EDT
arnebab
#Lisp with less brackets - but with the full power of !gnu #guile → http://www.youtube.com/watch?v=l9sFTOKa-cg — needs some work for !emacs -
cwebber (cwebber)'s status on Friday, 24-Aug-2012 11:53:42 EDT
cwebber
It is a myth in "full completion of that idea". But aspiring towards it leads to a cleaner infrastructure. -
jasonriedy (jasonriedy)'s status on Friday, 24-Aug-2012 11:34:30 EDT
jasonriedy
@cwebber Also, binding tightly to the object isn't how CLOS works. That drives me nuts in languages that conflate packaging with dispatch. -
jasonriedy (jasonriedy)'s status on Friday, 24-Aug-2012 11:33:41 EDT
jasonriedy
@cwebber That's the risk that comes from being the first standard. When others decide to work differently, you're stuck. -
barryfm (barryfm)'s status on Friday, 24-Aug-2012 11:33:36 EDT
barryfm
@cwebber Guile has (method object args) with common lisp like generic functions, so you can do (append vbox widget) -
jasonriedy (jasonriedy)'s status on Friday, 24-Aug-2012 11:32:50 EDT
jasonriedy
@barryfm @cwebber That there's only "one good way" is a myth even in Phyton, sorry. -
cwebber (cwebber)'s status on Friday, 24-Aug-2012 11:21:22 EDT
cwebber
I don't want (someclass-somemethod object args) or (callmethod object 'methodname args)... I want (object.method args)! -
cwebber (cwebber)'s status on Friday, 24-Aug-2012 11:20:22 EDT
cwebber
One heresy I really wish a lisp system had nailed down: *one* way to do OOP and (biggest heresy) dot notation.