freenode/lisp - IRC Chatlog
Search
14:56:08
edgar-rft
SICP teaches programming in general using Scheme examples, but it's not necessarily only for Scheme or Lisp
14:57:33
jackdaniel
while they belong loosely to the same family of programming languages, they are very different (both design- and community- wise)
14:57:44
edgar-rft
clockboi: no worries, there's lots of historical quirks in Lisp, don't be afraid to ask :-)
15:02:15
phoe
if you want to, you can do all of SICP in Common Lisp; the most important difference you will encounter is FUNCALL which does not exist in Scheme but is necessary in Common Lisp
15:12:46
beach
clockboi: There are books specifically for Common Lisp, in case you already know the basics of programming in general.
15:20:25
p_l
clockboi: also, consider that the amount of scheme you're supposed to know to finish SICP is quite small
15:39:20
docl
I just did SICP 1.1 in CL, one thing I noticed was define doesn't exist, instead you have to do defun for functions. and the paren structure for that is slightly different.
15:40:15
beach
Also, using DEFUN inside a function means something different from using DEFINE to define a function inside another one in Scheme.
17:21:31
gothnbass
Tracking down a bug relating to `html-template:fill-and-print-template`. Does anybody know of a non-obvious dependency on `pwd`? It works just fine if I'm running from the parent directory of `/templates`, but breaks with a `format` error otherwise.
17:21:32
dim
I like PAIP intro chapter about Common Lisp for people who already know how to write some code
17:31:15
gothnbass
Never mind; I found it. I'm an idiot, and I hard-coded that path into TMPL_INCLUDE statements in the templates.
22:09:16
pillton
The CMUCL installation instruction doesn't specify how to get a GnuPG key to check the digests of the releases.
22:31:10
easye
Actually, getting "fine" GPG keys these days is hard. <https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f>
2:00:54
g0d_shatter
does anyone know if there are any bindings somewhere for manipulating GDB, with common lisp? not debugging common lisp WITH gdb, but manipulating GDB debugging something else, specifcally the debugger state, the information about the program being debugged, as there is with Guile Scheme