freenode/#lisp - IRC Chatlog
Search
11:21:51
AnononA
hi all i just got my self a steel series keyboard that has keys for macros and i have come accross this link http://techblog.steelseries.com/golisp/language-ref.html#macros
11:22:14
AnononA
now im i right to believe that this is what my keyboard supports for writing macros in the macro editor
11:51:01
beach
AnononA: Also, this channel is dedicated to Common Lisp. If you want to discuss other Lisp dialects, you may want to visit the specific channels for those dialects, or ##lisp for general discussions about Lisp-like languages.
12:50:23
_death
AnononA: doesn't look like "googles version of lisp", just another toy lisp implemented in go
12:54:54
Satou
Hello, I am really really new to Lisp, currently getting introduced to a CLisp course. Do you guys use it on a daily basis? if yes, what sort of projects do you do with it?
12:56:39
nydel
Satou: welcome. please consider a intro to commonlisp book. i would recommend Practical Common Lisp, here for you: http://www.gigamonkeys.com/book/ -- we use LISP for everything. everything.
12:57:31
nydel
jackdaniel is right. also many prefer SBCL to CLISP. that is steel bank common lisp. i prefer it.
12:57:33
Satou
I understand that there are a lot of Lisp dialects, and Clojure and Scheme seem to be the ones most used
12:58:21
Satou
maybe not, as I am new to this language and to functional programming, I might be wrong.
12:59:19
Satou
I know that functional doesn't really depend on the language, you could write functional in anything.
12:59:24
nydel
jackdaniel: i always wished someone had told me "CL != FUNCTIONAL PROGRAMMING" in the very beginning.
13:00:57
nydel
i don't know a thing about scheme or clojure. those are dialects other than CL. as random-nick said, the different CL implementations listed by jackdaniel are not different dialects.
13:01:08
Satou
I'm also interested in what are sort of the limits of CL. I've understood to some extent how the usage of variables could lead to side effects.
13:01:44
jackdaniel
scheme has more focus on encouraging functional programming (scheme too), usual Common Lisp program mutates state a lot
13:02:00
minion
Satou: please see gentle: "Common Lisp: A Gentle Introduction to Symbolic Computation" is a smoother introduction to lisp programming. http://www.cs.cmu.edu/~dst/LispBook/
13:02:01
random-nick
but do note that there are big differences between CL implementations, just like with any other programming language
13:03:18
nydel
however CL does adhere to a standard across implementations. a topic we will not discuss at the moment! because it's saturday, baby!
13:07:46
beach
Satou: Common Lisp is a somewhat unusual choice if what you want to do is functional programming. By restricting yourself to that particular paradigm, you are not using the full potential of the language. And people who want to use functional programming typically choose a purely (or nearly so) functional language like Haskell or ML.
13:20:49
nydel
cliki.net is a good resource for packaged examples of things people do with commonlisp currently(ish). also quicklisp.org will teach you how to quickly load most systems listed at cliki. you might get a sense of the 'limits' (rather something like 'topography') of the language that way.
13:52:56
Shinmera
_death: I can't reproduce that Staple error you got. Other package inferred systems compile for me.
14:01:57
Shinmera
The screenshot tells me that asdf:system-source-directory somehow returns a system, rather than a path.
14:06:07
_death
asdf manual says "ASDF does not provide a turnkey solution for locating data (or other miscellaneous) files that are distributed together with the source code of a system. Programmers can use system-source-directory to find such files. Returns a pathname object. The system-designator may be a string, symbol, or ASDF system object."
14:06:41
Shinmera
Yeah, it's a plain function too, so it's not like something could have customised its behaviour directly.
14:10:30
_death
every file has its own system, but a file's system (type package-inferred-system) has its source-file slot set to NIL
14:14:43
Shinmera
Huh. Weird, since I tested it with another thing that supposedly uses package-inferred-systems and that worked fine.
14:15:46
_death
system-source-file docstring is "Return the source file in which system is defined." .. and I guess it's nil because there is no source file as these systems are generated at runtime
14:16:35
Shinmera
In order to make Staple well-usable for p-i-s there needs to be some more work done, but it should at least not crash anymore.
14:21:39
_death
works ok now.. also, better wrap "~&~%The following systems could not be processed cleanly:~%~a" with ~@[...~]
15:38:18
learning101
I am in a dilemma. I recently got a job in javascript profile and I have to become good in it, but what i really want is to learn lisp or haskell. Is it possible to learn both simultaneously?
15:53:29
beach
flip214: Thanks for the feedback on the papers. I think we will work on it this coming Wednesday.
16:01:53
flip214
But I have to admit I cheated - I read 9 or so before the submission deadline and was lucky, only 2 of them got updated.
17:16:23
rme
Presumably this is because the spec says "If the at-sign modifier is used with ~<...~:>, the entire remaining argument list is passed to the directive as its argument."
17:26:59
pjb
The way ~< is specified is clear: the argument is mandatory (it's the second argument to pprint-logical-block).
17:34:40
rme
Yes, so ccl is rightfully expecting an argument, and is right to complain about its absence.
17:42:11
rme
I'm starting to think ccl is probably wrong here. If the @ modifier is present, it seems like it ought to be OK if the "remaining argument list" is nil.
18:09:23
stacksmith
pjb: what's the deal with prog2? CLHS says "prog2 evaluates first-form, then second-form, and then forms, yielding as its only value the primary value yielded by first-form." How does that differ from prog1?
18:26:00
pjb
The thing is that since the specification is not formal, and is known to contain bugs, some level of consensual interpretation is left to the implementations. But it is better if all implementors agree on thos litigious points. Unfortunately, on some important parts, they don't. Eg. they could agree on how to do pathnames (both physical and logical) on POSIX systems, but they don't. :-(
18:30:21
stacksmith
pjb: oh are you saying that they indeed do return 2? I read it as 'I wish they would all return 2' ...
18:31:30
stacksmith
loli: I know. I was asking pjb to clarify a statement earlier that I misunderstood.
19:44:48
puchacz
hi; slime on slow device please. I am getting [Interrupted: time limit exhausted] on fuzzy completion
20:15:54
jackdaniel
I've wrote some rendering approximation illustrations with McCLIM: http://hellsgate.pl/files/c885c815 (I'll make it one of clim-examples after adding some interactivity to it)
20:36:05
flip214
puchacz: well, why not do the auto-completion against a faster system, and just run the code on the slow target system anyway?