Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.lisp > #60742 > unrolled thread
| Started by | Mario Rosell <mario@mariorosell.es> |
|---|---|
| First post | 2026-02-20 22:53 +0100 |
| Last post | 2026-08-22 11:28 +0800 |
| Articles | 20 on this page of 762 — 42 participants |
Back to article view | Back to comp.lang.lisp
Resources to learn common lisp? Mario Rosell <mario@mariorosell.es> - 2026-02-20 22:53 +0100
Re: Resources to learn common lisp? Ben Bacarisse <ben@bsb.me.uk> - 2026-02-20 22:00 +0000
Re: Resources to learn common lisp? Mario Rosell <mario@mariorosell.es> - 2026-02-21 12:25 +0100
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-02-21 10:24 -0500
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-21 21:30 +0000
Re: Resources to learn common lisp? Mario Rosell <mario@mariorosell.es> - 2026-02-22 01:08 +0100
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-22 04:59 +0000
Re: Resources to learn common lisp? Madhu <enometh@meer.net> - 2026-02-22 10:59 +0530
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-22 21:48 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-08 12:43 -0400
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-08 12:41 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-08 20:02 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-09 00:23 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-09 06:28 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-09 06:32 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-10 12:27 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-11 17:33 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-10 12:16 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-09 06:53 +0000
Re: Resources to learn common lisp? Axel Reichert <mail@axel-reichert.de> - 2026-06-09 12:07 +0200
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-10 00:14 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-17 00:01 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-17 05:53 +0000
[OT] Disappearing documentation (was: Re: Resources to learn common lisp?) Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-17 09:06 +0100
Re: [OT] Disappearing documentation steve g <Sgonedes1977@gmail.com> - 2026-06-19 19:05 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 19:01 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-20 00:02 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-11 17:22 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 13:59 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 00:55 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-14 01:43 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 05:45 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-09 00:35 +0000
Re: Resources to learn common lisp? Anthk GM <anthk@disroot.org> - 2026-08-15 22:29 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-15 23:38 +0000
Buy the official standard from A.N.S.I. (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-16 11:25 +0800
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-08 12:37 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-09 00:33 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-09 00:22 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-09 01:22 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-09 06:17 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-09 06:50 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-10 12:40 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-11 00:26 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 22:10 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 21:37 -0700
Re: Resources to learn common lisp? Joerg Mertens <joerg-mertens@t-online.de> - 2026-06-17 12:04 +0200
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-17 11:17 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-17 13:57 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 01:06 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-18 09:17 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-18 13:32 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-18 14:21 -0700
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-19 08:12 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-19 04:27 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 21:24 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-20 13:00 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 07:55 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-18 12:53 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-18 21:28 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-19 15:08 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-19 22:32 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-20 13:56 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-21 14:57 -0700
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-22 09:11 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-24 22:14 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-25 11:20 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 09:47 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 23:21 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-29 19:00 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:34 +0000
Python blanks (was: Re: Resources to learn common lisp?) Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-02 08:39 +0100
Re: Python blanks ram@zedat.fu-berlin.de (Stefan Ram) - 2026-07-02 09:24 +0000
Re: Python blanks Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 21:10 +0000
Re: Python blanks Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-03 00:34 +0100
Re: Python blanks George Neuner <gneuner2@comcast.net> - 2026-07-03 02:10 -0400
Re: Python blanks Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-03 07:21 +0100
Re: Python blanks Paul Rubin <no.email@nospam.invalid> - 2026-07-03 01:47 -0700
Re: Python blanks Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-03 17:42 -0400
Re: Python blanks Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 04:15 +0000
Re: Python blanks yeti <yeti@tilde.institute> - 2026-07-03 12:51 +0042
Re: Python blanks Paul Rubin <no.email@nospam.invalid> - 2026-07-03 11:34 -0700
Re: Python blanks Lars Brinkhoff <lars.spam@nocrew.org> - 2026-07-04 04:03 +0000
Re: Python blanks Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 04:18 +0000
Re: Python blanks tfb <tfb@work.it.out> - 2026-07-09 11:34 +0000
Re: Python blanks ram@zedat.fu-berlin.de (Stefan Ram) - 2026-07-09 13:15 +0000
Re: Python blanks tfb <tfb@work.it.out> - 2026-07-09 13:24 +0000
Re: Python blanks antispam@fricas.org (Waldek Hebisch) - 2026-07-09 14:01 +0000
Re: Python blanks tfb <tfb@work.it.out> - 2026-07-09 14:39 +0000
Re: Python blanks antispam@fricas.org (Waldek Hebisch) - 2026-07-09 21:03 +0000
Re: Python blanks tfb <tfb@work.it.out> - 2026-07-09 21:23 +0000
Re: Python blanks Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-09 23:09 +0000
Re: Python blanks steve g <Sgonedes1977@gmail.com> - 2026-08-04 23:05 -0400
Re: Python blanks George Neuner <gneuner2@comcast.net> - 2026-08-06 09:57 -0400
Re: Python blanks Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-09 23:08 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-02 13:41 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 05:45 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-03 10:12 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-03 18:43 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 23:28 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-04 17:22 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 01:47 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 23:24 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-04 21:48 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 23:56 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 09:47 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-20 13:43 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-20 22:28 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-22 09:16 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 23:38 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-26 00:43 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 02:52 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 19:06 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-11 05:27 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 22:12 -0400
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-10 12:24 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-11 05:57 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-11 21:07 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-12 13:06 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-13 00:13 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-13 07:25 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-13 08:25 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-13 08:46 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-13 08:52 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 05:57 +0000
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-15 10:10 +0100
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 05:56 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-16 11:46 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 01:03 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-18 07:52 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 23:35 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 20:56 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-13 00:55 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-13 07:43 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 21:37 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 13:09 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 01:02 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-16 10:12 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 22:54 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-06-17 00:07 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-17 08:33 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 18:48 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 18:28 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-12 12:42 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 23:32 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-09 09:36 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-10 00:06 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-10 08:43 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-11 00:22 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-11 08:57 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-12 00:16 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 21:42 -0400
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-15 01:15 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-15 05:42 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-15 11:19 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-16 00:18 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-16 03:27 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 01:25 -0700
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-17 10:13 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-18 13:57 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 01:11 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-18 02:30 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 08:21 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-18 09:32 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 08:24 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 09:47 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:26 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-02 18:22 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 04:04 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-03 02:16 -0400
[OT] Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-03 07:29 +0100
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-03 10:18 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 03:51 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-04 09:23 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 01:46 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-04 21:44 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 05:17 +0000
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-05 08:43 +0100
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-06 05:13 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-05 01:03 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 12:31 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-11 14:55 -0400
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-05 08:42 +0100
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-05 11:02 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-06 01:10 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-06 05:21 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-07 11:52 -0400
Re: Resources to learn common lisp? cross@spitfire.i.gajendra.net (Dan Cross) - 2026-07-08 01:46 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-08 03:04 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-07 19:30 -0700
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-07 19:34 -0700
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-03 22:03 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 05:44 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-04 03:21 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 23:22 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 09:15 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-11 16:04 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-13 12:12 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-13 14:59 -0400
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-18 14:15 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 08:23 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 10:02 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:58 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 23:53 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-17 05:55 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-17 01:43 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 01:07 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 18:58 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-19 18:52 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-20 00:04 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-11 06:37 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 13:30 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 00:58 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-14 01:46 -0700
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-15 06:59 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-15 12:25 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 07:47 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-11 17:42 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-12 00:16 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-12 12:34 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-13 00:11 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-13 04:06 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 13:37 -0700
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-13 21:25 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 15:26 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 05:37 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-15 01:34 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-15 05:43 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-15 11:23 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-16 00:23 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-16 03:29 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-16 04:59 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 15:10 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-28 22:42 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 06:01 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:12 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:35 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 15:53 -0400
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-16 13:34 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-28 22:41 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 20:31 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:04 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 17:44 -0700
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-13 08:36 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 01:43 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-14 10:36 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 23:55 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-14 18:04 -0700
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-16 12:33 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 02:56 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-27 20:25 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 23:37 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 16:55 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 08:41 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 00:44 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 07:33 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 00:30 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:08 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-29 23:53 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:22 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-05 22:00 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-05 22:34 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-08 22:05 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 18:42 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-10 01:48 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-10 21:18 -0400
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-11 11:19 +0100
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-11 10:00 -0300
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-11 18:31 +0100
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-11 19:35 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-11 20:56 +0100
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-11 20:21 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-11 22:44 +0100
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-11 22:50 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-12 01:35 +0000
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-12 16:28 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-13 05:03 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-14 07:14 +0100
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-14 06:47 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-14 01:33 -0700
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-13 11:42 -0300
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-13 15:39 +0000
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-13 16:52 -0300
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 05:04 +0800
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-14 08:16 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-14 00:11 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-13 17:16 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-14 10:27 +0000
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-13 20:35 +0000
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-14 08:04 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-13 23:58 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-14 09:27 +0100
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-11 23:35 -0400
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-11 18:35 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-11 21:14 +0100
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-11 21:01 +0000
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-22 23:48 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-12 01:20 +0000
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-12 09:12 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-18 21:23 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-18 21:26 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-12 01:19 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 16:25 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-11 23:30 -0400
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-12 16:52 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-19 17:53 -0400
Re: Resources to learn common lisp? Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-24 09:46 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-28 17:43 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-11 20:39 -0700
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-12 23:23 +0100
Re: Resources to learn common lisp? cross@spitfire.i.gajendra.net (Dan Cross) - 2026-08-10 15:05 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-08 22:00 +0800
Re: Resources to learn common lisp? Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-08-08 14:14 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-09 20:34 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-08 14:45 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-09 02:18 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 18:47 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-11 11:38 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-13 18:59 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-15 21:12 -0400
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-14 08:20 -0300
Names for GenAI (was: Re: Resources to learn common lisp?) Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 13:30 +0100
Re: Names for GenAI ram@zedat.fu-berlin.de (Stefan Ram) - 2026-08-14 12:49 +0000
Re: Names for GenAI Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-29 09:51 +0100
Re: Names for GenAI Paul Rubin <no.email@nospam.invalid> - 2026-08-30 02:01 -0700
Re: Names for GenAI Anton Antimo <anton@safunu.org> - 2026-08-16 13:56 -0300
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-29 16:16 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 13:46 -0700
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-06-30 17:15 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 04:07 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 12:26 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-11 16:06 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-11 15:03 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-13 12:12 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-13 15:55 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-13 20:37 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:18 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-29 22:06 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:15 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-30 21:05 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-31 08:01 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-04 22:08 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-05 11:29 +0000
Re: Resources to learn common lisp? Madhu <enometh@meer.net> - 2026-08-05 23:46 +0530
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-06 19:41 -0400
Re: Resources to learn common lisp? Andreas Eder <a_eder_muc@web.de> - 2026-08-10 14:44 +0200
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 12:31 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:21 -0400
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-07-31 07:17 +0800
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-07-31 12:21 -0300
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-01 01:48 +0800
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-05 13:13 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-05 21:48 +0000
Re: Resources to learn common lisp? David Brown <david.brown@hesbynett.no> - 2026-08-06 09:05 +0200
Re: Resources to learn common lisp? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-06 11:33 -0700
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-06 15:49 -0300
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-06 20:23 -0400
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-08-07 09:36 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-07 11:58 +0000
Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-08-08 19:02 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 18:59 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 15:23 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-18 21:59 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 08:56 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-28 17:38 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 08:57 +0000
Reader macros (was: Resources to learn common lisp?) Stefan Monnier <monnier@iro.umontreal.ca> - 2026-08-09 11:51 -0400
Re: Reader macros Paul Rubin <no.email@nospam.invalid> - 2026-08-10 00:48 -0700
Manipulating C code at the AST level, in C (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-09 05:33 +0800
Re: Manipulating C code at the AST level, in C Paul Rubin <no.email@nospam.invalid> - 2026-08-10 01:11 -0700
Re: Manipulating C code at the AST level, in C cross@spitfire.i.gajendra.net (Dan Cross) - 2026-08-10 14:57 +0000
Re: Manipulating C code at the AST level, in C "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-10 13:10 -0700
Re: Manipulating C code at the AST level, in C Anton Antimo <anton@safunu.org> - 2026-08-10 17:41 -0300
Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-10 23:53 +0000
Re: Manipulating C code at the AST level, in C scott@slp53.sl.home (Scott Lurndal) - 2026-08-11 14:29 +0000
kqueues and port_create() (was: Re: Manipulating C code at the AST level, in C) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-12 07:51 +0800
Re: kqueues and port_create() Paul Rubin <no.email@nospam.invalid> - 2026-08-11 20:59 -0700
Re: kqueues and port_create() Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-12 13:07 +0800
Re: kqueues and port_create() Alan Bawden <alan@csail.mit.edu> - 2026-08-12 03:23 -0400
Re: kqueues and port_create() Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-12 07:50 +0000
Re: kqueues and port_create() Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-13 11:33 +0800
Re: kqueues and port_create() Paul Rubin <no.email@nospam.invalid> - 2026-08-12 02:22 -0700
Re: kqueues and port_create() Alan Bawden <alan@csail.mit.edu> - 2026-08-12 20:55 -0400
Re: kqueues and port_create() Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-13 11:37 +0800
Re: kqueues and port_create() "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-12 12:59 -0700
Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:26 +0100
D.N.S. in Common Lisp (was: Re: Manipulating C code at the AST level, in C) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-12 07:59 +0800
Re: D.N.S. in Common Lisp Anton Antimo <anton@safunu.org> - 2026-08-12 09:01 -0300
Making production games in Common Lisp (was: Re: D.N.S. in Common Lisp) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-13 11:20 +0800
Re: Making production games in Common Lisp Paul Rubin <no.email@nospam.invalid> - 2026-08-12 20:46 -0700
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-13 14:28 +0800
Re: Making production games in Common Lisp bixbox <noreply@example.invalid> - 2026-08-13 11:46 +0200
Re: Making production games in Common Lisp Anton Antimo <anton@safunu.org> - 2026-08-13 12:19 -0300
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 01:24 +0800
Re: Making production games in Common Lisp ram@zedat.fu-berlin.de (Stefan Ram) - 2026-08-13 17:39 +0000
Re: Making production games in Common Lisp Anton Antimo <anton@safunu.org> - 2026-08-13 20:58 -0300
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 13:42 +0800
Re: Making production games in Common Lisp Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:46 +0100
Re: Making production games in Common Lisp Anton Antimo <anton@safunu.org> - 2026-08-16 15:29 -0300
Re: Making production games in Common Lisp Paul Rubin <no.email@nospam.invalid> - 2026-08-13 17:31 -0700
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 14:04 +0800
Re: Making production games in Common Lisp Paul Rubin <no.email@nospam.invalid> - 2026-08-14 01:52 -0700
Re: Making production games in Common Lisp tfb <tfb@work.it.out> - 2026-08-14 10:27 +0000
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-15 01:19 +0800
Re: Making production games in Common Lisp (was: Re: D.N.S. in Common Lisp) tfb <tfb@work.it.out> - 2026-08-13 16:14 +0000
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 01:31 +0800
Re: Making production games in Common Lisp Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:52 +0100
Re: Making production games in Common Lisp tfb <tfb@work.it.out> - 2026-08-14 12:30 +0000
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-15 01:33 +0800
Re: Making production games in Common Lisp (was: Re: D.N.S. in Common Lisp) George Neuner <gneuner2@comcast.net> - 2026-08-15 19:44 -0400
Re: Making production games in Common Lisp Anton Antimo <anton@safunu.org> - 2026-08-16 15:06 -0300
Re: Making production games in Common Lisp Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-22 02:28 +0800
Re: Making production games in Common Lisp George Neuner <gneuner2@comcast.net> - 2026-08-21 15:23 -0400
Databases with Common Lisp (was: Re: Making production games in Common Lisp) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-22 07:54 +0800
Re: Databases with Common Lisp (was: Re: Making production games in Common Lisp) George Neuner <gneuner2@comcast.net> - 2026-08-22 18:13 -0400
Re: Databases with Common Lisp steve g <Sgonedes1977@gmail.com> - 2026-08-23 15:58 -0400
Dynamic scoping (was: Databases with Common Lisp) Stefan Monnier <monnier@iro.umontreal.ca> - 2026-08-23 23:08 -0400
Re: Dynamic scoping (was: Databases with Common Lisp) George Neuner <gneuner2@comcast.net> - 2026-08-24 10:24 -0400
Re: Dynamic scoping (was: Databases with Common Lisp) tfb <tfb@work.it.out> - 2026-08-24 19:29 +0000
Re: Dynamic scoping Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-25 10:26 +0800
Re: Making production games in Common Lisp Madhu <enometh@meer.net> - 2026-08-23 21:03 +0530
Re: Making production games in Common Lisp George Neuner <gneuner2@comcast.net> - 2026-08-24 01:42 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-06 18:05 -0700
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-09 05:26 +0800
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-08 18:37 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-09 08:52 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-08-09 11:50 +0100
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-09 23:01 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 19:09 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 15:23 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 15:23 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-09 20:36 +0000
What do you need from S.B.C.L? (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-10 05:32 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 19:02 -0400
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-10 00:56 +0100
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 15:30 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-08-12 16:31 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 17:07 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-08-12 17:20 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 14:28 +0800
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-10 00:54 -0700
Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-08-11 20:20 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-11 20:51 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-18 21:35 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-18 21:34 -0700
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-21 02:12 -0400
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-21 12:28 -0300
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 09:17 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 15:52 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-14 03:27 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-14 12:16 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-14 12:03 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 08:46 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:38 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 12:22 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 21:04 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 13:18 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 22:16 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 20:10 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-25 10:34 +0800
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-24 17:10 -0700
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-25 10:41 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-25 09:22 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-25 22:13 -0700
Re: Resources to learn common lisp? Madhu <enometh@meer.net> - 2026-08-26 11:33 +0530
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-26 15:43 -0300
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-26 18:23 -0700
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-08-27 14:43 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-27 13:01 -0700
Continuations via macros (was: Resources to learn common lisp?) Stefan Monnier <monnier@iro.umontreal.ca> - 2026-08-28 16:36 -0400
Re: Continuations via macros steve g <Sgonedes1977@gmail.com> - 2026-09-04 22:01 -0400
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-08-29 03:06 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-09-04 22:15 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-09-16 14:56 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-09-16 13:42 -0700
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-17 20:03 -0400
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-09-17 00:12 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-17 19:36 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-09-17 21:19 -0700
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-20 07:18 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-09-20 16:31 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-09-21 04:40 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-22 05:30 -0400
delimited continuations - was Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-22 11:24 -0400
Re: delimited continuations - was Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-22 19:03 +0000
Re: delimited continuations - was Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-09-24 19:48 +0000
Re: delimited continuations - was Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-24 20:53 +0000
Re: delimited continuations - was Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-24 21:13 +0000
Re: delimited continuations - was Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-24 21:21 +0000
Re: delimited continuations - was Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-09-27 08:02 -0400
Re: delimited continuations - was Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-09-29 17:03 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-27 20:39 +0000
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-28 17:29 -0300
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-26 19:06 +0000
Re: Resources to learn common lisp? bixbox <noreply@example.invalid> - 2026-08-27 07:57 -0400
Re: Resources to learn common lisp? Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2026-08-24 13:19 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-24 20:37 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-09-15 15:18 -0400
Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-14 12:51 +0000
Re: Macros (was Re: Resources to learn common lisp?) Paul Rubin <no.email@nospam.invalid> - 2026-08-14 12:08 -0700
Re: Macros Aidan Kehoe <kehoea@parhasard.net> - 2026-08-15 10:01 +0100
Re: Macros (was Re: Resources to learn common lisp?) Stéphane CARPENTIER <sc@fiat-linux.fr> - 2026-08-15 12:58 +0000
Re: Macros (was Re: Resources to learn common lisp?) Anton Antimo <anton@safunu.org> - 2026-08-16 15:27 -0300
Re: Macros (was Re: Resources to learn common lisp?) Paul Rubin <no.email@nospam.invalid> - 2026-08-26 00:56 -0700
Re: Macros (was Re: Resources to learn common lisp?) Anton Antimo <anton@safunu.org> - 2026-08-26 19:55 -0300
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 11:08 +0000
Re: Macros (was Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:41 +0800
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 12:31 +0000
Re: Macros (was Re: Resources to learn common lisp?) George Neuner <gneuner2@comcast.net> - 2026-08-24 09:56 -0400
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 19:29 +0000
Re: Macros (was Re: Resources to learn common lisp?) Anton Antimo <anton@safunu.org> - 2026-08-24 16:35 -0300
Re: Macros (was Re: Resources to learn common lisp?) Anton Antimo <anton@safunu.org> - 2026-08-16 15:26 -0300
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-22 00:00 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-22 01:23 +0000
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-22 12:07 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-22 22:24 +0000
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-22 23:08 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-22 23:22 +0000
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-23 00:23 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-25 00:13 +0000
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 10:17 +0000
Re: Macros (was Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:45 +0800
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 12:49 +0000
Re: Macros (was Re: Resources to learn common lisp?) George Neuner <gneuner2@comcast.net> - 2026-08-24 18:34 -0400
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-25 07:54 +0000
Re: Macros (was Re: Resources to learn common lisp?) Madhu <enometh@meer.net> - 2026-08-26 07:47 +0530
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-26 02:58 +0000
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 10:17 +0000
Re: Macros (was Re: Resources to learn common lisp?) steve g <Sgonedes1977@gmail.com> - 2026-08-23 15:47 -0400
Re: Macros Aidan Kehoe <kehoea@parhasard.net> - 2026-08-23 21:57 +0100
Re: Macros Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-23 22:21 +0000
Re: Macros Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:49 +0800
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-23 22:37 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-23 23:47 +0000
Re: Macros (was Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:51 +0800
Re: Macros (was Re: Resources to learn common lisp?) Paul Rubin <no.email@nospam.invalid> - 2026-08-24 16:59 -0700
Re: Macros (was Re: Resources to learn common lisp?) Paul Rubin <no.email@nospam.invalid> - 2026-08-24 01:24 -0700
Re: Macros (was Re: Resources to learn common lisp?) antispam@fricas.org (Waldek Hebisch) - 2026-08-24 12:02 +0000
Re: Macros (was Re: Resources to learn common lisp?) Paul Rubin <no.email@nospam.invalid> - 2026-08-24 16:45 -0700
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-25 07:54 +0000
Re: Macros (was Re: Resources to learn common lisp?) Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-25 00:18 +0000
Re: Macros (was Re: Resources to learn common lisp?) steve g <Sgonedes1977@gmail.com> - 2026-08-27 19:11 -0400
Re: Macros (was Re: Resources to learn common lisp?) tfb <tfb@work.it.out> - 2026-08-24 10:24 +0000
Re: Macros (was Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 19:44 +0800
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-12 13:18 +0800
Re: Resources to learn common lisp? bixbox <noreply@example.invalid> - 2026-08-12 10:16 +0200
Re: Resources to learn common lisp? Andreas Eder <a_eder_muc@web.de> - 2026-08-10 14:21 +0200
Re: Resources to learn common lisp? Kaz Kylheku <046-301-5902@kylheku.com> - 2026-08-11 22:14 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 14:37 +0800
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-08 19:08 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 19:12 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-11 11:45 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-13 19:25 -0400
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-10 10:48 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-10 23:55 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-10 21:25 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-11 12:20 -0400
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-08-12 13:06 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-12 17:16 +0000
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-13 12:46 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-31 22:46 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-01 07:38 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:26 -0400
Making a C compiler in Rust (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-21 13:06 +0800
Re: Making a C compiler in Rust (was: Re: Resources to learn common lisp?) "Kerr-Mudd, John" <admin@127.0.0.1> - 2026-08-21 11:34 +0100
Re: Making a C compiler in Rust (was: Re: Resources to learn common lisp?) Michael S <already5chosen@yahoo.com> - 2026-08-21 14:13 +0300
Re: Making a C compiler in Rust Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-22 02:23 +0800
Re: Making a C compiler in Rust Paul Rubin <no.email@nospam.invalid> - 2026-08-21 15:03 -0700
Re: Making a C compiler in Rust Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-22 07:24 +0800
Re: Making a C compiler in Rust Paul Rubin <no.email@nospam.invalid> - 2026-08-21 16:48 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-01 09:08 +0000
Re: Resources to learn common lisp? Paul <nospam@needed.invalid> - 2026-08-01 07:49 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-01 23:37 +0000
Re: Resources to learn common lisp? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-01 16:54 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-02 07:39 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:39 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-31 23:59 -0400
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-01 16:12 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:50 -0400
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-05 19:02 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-06 19:36 -0400
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-09 02:11 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-09 18:49 -0400
Short wave radio, French (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-19 13:03 +0800
Re: Short wave radio, French Cóilín Nioclásín Glostéir <thanks-to@Taf.com> - 2026-08-24 10:15 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-24 20:07 +0800
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-24 17:13 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-09-04 21:46 -0400
Re: Resources to learn common lisp? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-10 13:08 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-28 22:48 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 20:34 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 06:00 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 00:52 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 07:55 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 13:35 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 22:25 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 17:37 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 03:53 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:26 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-29 23:50 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-31 23:52 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-01 05:24 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 22:47 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-05 02:54 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-04 23:11 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-05 07:31 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-06 19:25 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-10 01:46 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-10 21:10 -0400
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-05 18:26 +0800
Re: Resources to learn common lisp? "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2026-08-05 13:05 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 23:34 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 00:07 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 01:49 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-06 05:23 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 09:26 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-07-09 12:04 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-07-09 14:42 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 19:33 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-07-09 21:29 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-10 07:37 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-07-10 10:17 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-10 03:35 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 17:32 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-29 23:48 +0000
Re: Resources to learn common lisp? George Neuner <gneuner2@comcast.net> - 2026-07-30 21:37 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-04 00:49 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-04 09:56 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 08:31 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 08:31 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 08:08 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 08:57 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 09:47 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 10:03 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 10:44 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 11:05 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:42 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 11:09 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:45 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:50 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:43 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:41 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 15:55 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-29 23:46 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:47 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:39 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-30 13:47 -0700
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-01 10:26 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-02 00:38 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-01 18:47 -0700
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-01 18:52 -0700
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-07-02 20:33 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 00:50 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 00:42 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 08:06 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 11:41 +0000
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-07-03 19:37 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-03 18:29 -0700
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-04 09:40 -0400
Re: Resources to learn common lisp? Alan Bawden <alan@csail.mit.edu> - 2026-07-08 19:07 -0400
boxing all integers (was Re: Resources to learn common lisp?) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-29 17:52 -0300
Re: boxing all integers (was Re: Resources to learn common lisp?) Lars Brinkhoff <lars.spam@nocrew.org> - 2026-08-30 06:43 +0000
Re: boxing all integers (was Re: Resources to learn common lisp?) Alan Bawden <alan@csail.mit.edu> - 2026-08-30 17:24 -0400
Re: boxing all integers (was Re: Resources to learn common lisp?) Kragen Javier Sitaker <kragen@canonical.org> - 2026-08-31 03:11 -0300
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-27 13:48 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 23:34 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 02:58 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-15 09:51 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-16 00:23 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 03:14 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 03:02 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-26 21:47 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 23:18 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 16:36 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-03 04:06 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-02 22:20 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 03:58 +0000
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-03 07:36 +0100
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 15:29 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-27 23:29 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 16:41 -0700
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 09:17 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-29 18:41 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-04 04:06 +0000
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-04 07:46 +0100
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-07-29 16:31 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-29 23:52 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-16 10:23 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 21:34 -0700
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-17 15:02 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 04:14 +0000
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-18 12:44 -0400
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 10:09 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-06-29 10:55 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 08:06 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-07-09 13:26 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-09 23:04 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-30 02:45 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-14 13:14 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-18 02:30 +0000
Re: Resources to learn common lisp? tfb <no_email@invalid.invalid> - 2026-06-16 11:46 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-18 15:34 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-19 07:01 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-19 11:41 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 23:38 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-28 23:42 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 13:58 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-29 22:19 +0000
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-28 22:37 -0400
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-28 20:42 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:08 -0400
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-06-29 08:27 +0100
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-29 00:42 -0700
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-06-29 14:35 +0100
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-06-29 23:27 -0400
Re: Resources to learn common lisp? Stefan Monnier <monnier@iro.umontreal.ca> - 2026-07-01 16:21 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:21 -0400
Re: Resources to learn common lisp? Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-01 08:57 +0100
Re: Resources to learn common lisp? Madhu <enometh@meer.net> - 2026-07-01 14:29 +0530
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-07-01 12:56 -0700
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-29 20:17 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-30 21:32 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-06-29 07:55 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-07-05 22:14 +0100
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-05 23:55 +0000
Re: Resources to learn common lisp? Aidan Kehoe <kehoea@parhasard.net> - 2026-07-06 08:04 +0100
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-07-06 08:00 +0000
Re: Resources to learn common lisp? Niocláisín Cóilín Glostéir <thanks-to@Taf.com> - 2026-08-04 18:35 +0000
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-05 05:46 +0800
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-07-09 09:57 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-06-13 13:22 -0700
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-14 01:55 +0000
Re: Resources to learn common lisp? tpeplt <tpeplt@gmail.com> - 2026-02-20 17:44 -0500
Re: Resources to learn common lisp? Mario Rosell <mario@mariorosell.es> - 2026-02-21 12:30 +0100
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-02-20 23:50 +0000
Re: Resources to learn common lisp? ram@zedat.fu-berlin.de (Stefan Ram) - 2026-02-21 00:24 +0000
Re: Resources to learn common lisp? Andreas Eder <a_eder_muc@web.de> - 2026-02-21 11:36 +0100
Re: Resources to learn common lisp? Mario Rosell <mario@mariorosell.es> - 2026-02-21 12:44 +0100
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-03-31 17:47 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-03-31 23:41 +0000
Re: Resources to learn common lisp? tpeplt <tpeplt@gmail.com> - 2026-04-01 13:23 -0400
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-06-16 21:59 -0400
Re: Resources to learn common lisp? Peri Didaskalou <pfd@torfree.net> - 2026-05-01 10:52 -0400
Re: Resources to learn common lisp? Peri Didaskalou <pfd@torfree.net> - 2026-05-01 10:57 -0400
Re: Resources to learn common lisp? Peri Didaskalou <pfd@torfree.net> - 2026-05-01 11:06 -0400
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-01 14:56 -0400
Re: Resources to learn common lisp? "Robert B. Carleton" <rbc@rbcarleton.net> - 2026-06-01 23:02 +0000
Re: Resources to learn common lisp? steve g <sgonedes1977@gmail.com> - 2026-06-02 21:32 -0400
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-03 03:16 +0000
Re: Resources to learn common lisp? kotorifan <mindyourownbiz@noemail.fuck> - 2026-08-02 16:42 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-02 22:53 +0000
Re: Resources to learn common lisp? Anthk GM <anthk@disroot.org> - 2026-08-13 13:40 +0000
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-13 23:46 +0000
Re: Resources to learn common lisp? tfb <tfb@work.it.out> - 2026-08-14 10:25 +0000
Re: Resources to learn common lisp? Paul Rubin <no.email@nospam.invalid> - 2026-08-02 16:56 -0700
Common Lisp Books (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-03 17:56 +0800
Re: Resources to learn common lisp? bixbox <noreply@example.invalid> - 2026-08-13 12:35 +0200
Re: Resources to learn common lisp? Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-14 01:36 +0800
Re: Resources to learn common lisp? steve g <Sgonedes1977@gmail.com> - 2026-08-19 17:57 -0400
Re: Resources to learn common lisp? Anton Antimo <anton@safunu.org> - 2026-08-20 10:16 -0300
Re: Resources to learn common lisp? Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-22 01:11 +0000
Abstract Syntax Trees in CorelDROW! (was: Re: Resources to learn common lisp?) Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> - 2026-08-22 11:28 +0800
Page 25 of 39 — ← Prev page 1 … 23 24 [25] 26 27 … 39 Next page →
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2026-09-20 16:31 -0400 |
| Message-ID | <jwvld8vad74.fsf-monnier+comp.lang.lisp@gnu.org> |
| In reply to | #61662 |
>>What Oleg (okmij.org) wanted instead was "one-shot" or "delimited" >>continuations, maybe closer to ordinary stackful coroutines. They still >>have to save and restore the stack, but only once. I've never tried to >>understand either type very carefully though. > > I've never figured out what makes "delimited" continuations different > from general continuations except that the implementation constrains > where a "delimited" continuation may be invoked. But that seems to be > a difference in usage rather than in kind. Full continuations are, conceptually, a copy of the whole stack, wrapped as a kind of function that never returns. Delimited continuations offer, conceptually, a copy of a chunk of the stack, wrapped as a kind of function that does return. === Stefan
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-09-21 04:40 +0000 |
| Message-ID | <118qcg2$3mnl1$1@dont-email.me> |
| In reply to | #61667 |
On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier wrote: > Full continuations are, conceptually, a copy of the whole stack, > wrapped as a kind of function that never returns. Delimited > continuations offer, conceptually, a copy of a chunk of the stack, > wrapped as a kind of function that does return. Why do you need to copy anything, beyond some very basic context info? Call frames just form a tree and are allocated on the heap. So the fact that a frame is referenced (directly or indirectly) from a continuation is sufficient to keep it from being deleted.
[toc] | [prev] | [next] | [standalone]
| From | George Neuner <gneuner2@comcast.net> |
|---|---|
| Date | 2026-09-22 05:30 -0400 |
| Message-ID | <brh4bltre7lha4or6gv3h7vurrga3tq0md@4ax.com> |
| In reply to | #61668 |
On Mon, 21 Sep 2026 04:40:34 -0000 (UTC), Lawrence D´Oliveiro <ldo@nz.invalid> wrote: >On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier wrote: > >> Full continuations are, conceptually, a copy of the whole stack, >> wrapped as a kind of function that never returns. Delimited >> continuations offer, conceptually, a copy of a chunk of the stack, >> wrapped as a kind of function that does return. > >Why do you need to copy anything, beyond some very basic context info? > >Call frames just form a tree and are allocated on the heap. So the >fact that a frame is referenced (directly or indirectly) from a >continuation is sufficient to keep it from being deleted. Not every implementation allocates frames on the heap. Since most functions don't create closures or continuations, it often is simpler to put their call frames on the [linear] CPU stack and let the normal call/return sequence deal with them. This has the advantage of speed because the CPU stack [or at least part of it] always is in cache. However, creating closures then involves copying whatever is needed from the stack to a heap allocation, and rewriting code to look in the allocation instead of in the stack. This is called "closure conversion" in the literature. Continuations require similar treatment, but may need to copy the entire CPU stack.
[toc] | [prev] | [next] | [standalone]
| From | George Neuner <gneuner2@comcast.net> |
|---|---|
| Date | 2026-09-22 11:24 -0400 |
| Subject | delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <qkv4blle152ff81vvpp7i8g967qfbiarji@4ax.com> |
| In reply to | #61667 |
On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier <monnier@iro.umontreal.ca> wrote: >> I've never figured out what makes "delimited" continuations different >> from general continuations except that the implementation constrains >> where a "delimited" continuation may be invoked. But that seems to be >> a difference in usage rather than in kind. > >Full continuations are, conceptually, a copy of the whole stack, wrapped >as a kind of function that never returns. >Delimited continuations offer, conceptually, a copy of a chunk of the >stack, wrapped as a kind of function that does return. > >=== Stefan I appreciate the explanation ... but I'm a bit dense and I don't see what delimited continuations give you vs just creating the equivalent closure. I look at continuations from the POV of a compiler writer: I see them as co-routines. Calling a co-routine is a "sideways" jump into a different call chain. If the co-routine is to finish and return, then obviously its originating call chain must be preserved. You mentioned above that DCs are wrapped in a function, so they can finish and "return" [for some definition]. But if the intent of keeping the stack is simply to allow the [co-routine] entry point to be in a nested function ... well then it seems that having the compiler perform closure conversion would get you to a result equivalent to the DC without needing to preserve the runtime call stack - which typically contains (lots of) extraneous state unrelated to the needs of the closure. Dunno. Perhaps implementations that heap allocate stack frames just don't bother with closure conversion, choosing instead to waste the address space and eat the extra GC processing. I don't see any clear win for DC here. What am I missing?
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <046-301-5902@kylheku.com> |
|---|---|
| Date | 2026-09-22 19:03 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <20260922112634.171@kylheku.com> |
| In reply to | #61674 |
On 2026-09-22, George Neuner <gneuner2@comcast.net> wrote:
> On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier
><monnier@iro.umontreal.ca> wrote:
>
>>> I've never figured out what makes "delimited" continuations different
>>> from general continuations except that the implementation constrains
>>> where a "delimited" continuation may be invoked. But that seems to be
>>> a difference in usage rather than in kind.
>>
>>Full continuations are, conceptually, a copy of the whole stack, wrapped
>>as a kind of function that never returns.
>>Delimited continuations offer, conceptually, a copy of a chunk of the
>>stack, wrapped as a kind of function that does return.
>>
>>=== Stefan
>
> I appreciate the explanation ... but I'm a bit dense and I don't see
> what delimited continuations give you vs just creating the equivalent
> closure.
Delimited continutaions close over the entire context/environment
between the capture point and some dynamic contour (the delimiting
prompt). The delimiting prompt can be in a parent function, or
grandparent, etc.
When we invoke ("revive") a delimited continuation, the execution inside
that continuation appears to pick up from the same point where the
continuation was captured. This code has available to it the original
callling environment up to the delimiting prompt.
Here is the cool/key part: when the revived delimited continuation
returns to its original callers, and finally bubbles out to the capture
contour, at that point it terminates. And whatever value that emerges
from the capture contour will be returned to the caller which revived
the continuation.
> I look at continuations from the POV of a compiler writer: I see them
> as co-routines. Calling a co-routine is a "sideways" jump into a
> different call chain. If the co-routine is to finish and return, then
> obviously its originating call chain must be preserved.
If we must preserve the entire call chain, then we have an "undelimited"
regular continuation. A regular continuation is like a delimited
continuation delimited by the dynamic top level of the enclosing form:
the top of the current thread.
The difference is that a regular continuation does not return when
it reaches its capture limit: the thread or process terminates there!
Like if you have some (defun startup () ...) main function and a
top-level form which calls (startup). If inside startup a continuation
is captured, and that continuation is then invoked, it will return all
the way to (startup) which terminates and then the image stops.
A delimited continuation doesn't stop the thread or image; it reaches
its contour, and then that value is returned to whatever invoked the
continuation.
One obvious application for delimited continuations provides a way to
help understand them. Using delimited continuations, a block of code
(surrounded by a delimiting prompt) can speculate about multiple ways of
resuming itself. Say that block of code is Boolean, in that it returns
true or NIL for success or failure. Inside the block, a delimited
continuation can be captured. Then the block can try invoking the
continuation for various values, until it obtains a true.
It's essentially saying, "If I continue my computation with the value
42, will that make me return true? Oops, no it deosn't. Okay then,
suppose I continue myself with the argument value 73? Still nope ..."
Code can perpetrate a search of its future executions, with different
values, to find some condition, like a success indication.
This is how John MacCarthy's "amb" operator can be implemented
with delimited continuations.
> You mentioned above that DCs are wrapped in a function, so they can
> finish and "return" [for some definition].
Return mean to bubble out of the last enclosing frame that was
included in the capture, and then return to the caller which
invoked the continuation.
Importantly: all those frames that were returned from remain live: the
continuation can be used again!
(That creates issues for scoped-based resource and other
scope-based things.)
> But if the intent of keeping the stack is simply to allow the
> [co-routine] entry point to be in a nested function ... well then it
> seems that having the compiler perform closure conversion would get
> you to a result equivalent to the DC without needing to preserve the
> runtime call stack - which typically contains (lots of) extraneous
> state unrelated to the needs of the closure.
>
>
> Dunno. Perhaps implementations that heap allocate stack frames just
> don't bother with closure conversion, choosing instead to waste the
> address space and eat the extra GC processing.
Delimited continuations don't require heap-allocated stack frames.
One possible implementation is that stack frames are just stack
allocated, and so nothing is different when DC are not used.
When a DC is captured, the actual captured
part of the stack is copied out to a heap object.
When a DC is revived, stack material is copied out of its
heap object to the current top of the stack: the stack is extended
with all those captured frames, and the topmost frame inside of
that is made current. As the DC finishes executing up to its
delimiting prompt, that material naturally pops off.
(But the heap copy remains, for repeated uses of the DC!)
Thus, a spaghetti stack is never required.
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-09-24 19:48 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <1193upr$3092m$1@dont-email.me> |
| In reply to | #61681 |
Kaz Kylheku <046-301-5902@kylheku.com> wrote: > > Delimited continutaions [...] You've just made delimited continuations make sense to me for the first time: thank you! > (That creates issues for scoped-based resource and other > scope-based things.) > If I understand this right (and this agrees with the mental model I've built from all the excised bits of your post) this means that you still need things like dynamic-wind with delimited continuations, and various resource-scoping problems are not solved by them. But they sound hugely better than standard Scheme-style continuations. If I didn't have a cat sitting on me I'd go up & play with them right away (I think Racket has them). -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <046-301-5902@kylheku.com> |
|---|---|
| Date | 2026-09-24 20:53 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <20260924133210.376@kylheku.com> |
| In reply to | #61687 |
On 2026-09-24, tfb <tfb@work.it.out> wrote: > Kaz Kylheku <046-301-5902@kylheku.com> wrote: > >> >> Delimited continutaions [...] > > You've just made delimited continuations make sense to me for the first > time: thank you! > >> (That creates issues for scoped-based resource and other >> scope-based things.) >> > > If I understand this right (and this agrees with the mental model I've > built from all the excised bits of your post) this means that you still > need things like dynamic-wind with delimited continuations, and various > resource-scoping problems are not solved by them. That is correct, because you can re-use a delimited continuation (meaning, invoke it as a function) so that you can replay its captured slice of future computation between the capture point and the delimiting prompt. The first resumption will blow out to the top, and unwind everything. I solved the problem without dynamic wind. The problem is not solved for raw delimited continuations. Rather, I provide tools for solving the problem for a coroutine/generator-like abstractions built on delimited continuation, which I call "suspended execution contexts". I provide an operator called "obtain" which creates a suspended execution out of its dynamic contents and returns a lambda. When we invoke the lambda, the interior of the suspension starts executing, until it hits a (yield ...). The yield transfers control to the original caller; the argument to the yield appears as the return value of invoking the suspension. The caller can then invoke the function again to resume the suspension, and pass it a value. That value bubbles out of the (yield ...) call: two-way communication. The suspension goes on to the next yield and so on. Eventually it bubbles out. The programmer has to have some way of indicating "this is the last yield, don't call this any more". These suspensions are based on DLC's. The original function is a DLC. The subsequent (yield ...) replaces the suspension's function with a brand new DLC capture. And every subsqeuent yield does the same. Every quantum of computation between two yields "rides" a new DLC. Exceptions, unwinding, dynamic scoped variable binding ... all the dynamic stuff works properly inside the suspension as it hops between yields with different DLC's. What happens is that the yield operation uses an unsafe form of dynamic control transfer which I named "abscond". By using abscond, yield can return control to the client context that is using the suspension. Three second demo of abscond: 1> (block foo (unwind-protect (return-from foo 42) (prinl "cleanup!"))) "cleanup!" 42 2> (block foo (unwind-protect (sys:abscond-from foo 42) (prinl "cleanup!"))) 42 sys:abscond-from is an alternative return-from; it looks exactly like it with the same convention, and uses a named block as its target. However, unwinding is not done by sys:abscond-from; as you can see the (print "cleanup!") int the unwind-protect is not happening. So to reiterate, I have not solved the resource problem for the low-level DLC's; there is no dynamic wind. But we have a working solution for thread-like abstractions built on top of DLC's. (Abstractions which do not reuse a continuation; do not repeat/replay the same captured computation.) I recommend that when a solution is built using raw DLC's, that dynamic state that tears down should be avoided; or else that the programmer invent an abstraction which solves the problem somehow. Dynamic resources which are not destroyed will work properly. For instance if we bind a dynamic variable (let ((*dyn-var* 42)) ...) inside a DLC, such that when the DLC finishes that variasble is unbound, when we re-enter the DLC, the variable will be correctly bound! This is because TXR Lisp uses deep binding for dynamic variables; the execution context has a pointer to a dynamic environment chain, and when we re-animate the DLC, that pointer is restored. Similarly other language-built-in resources that are dynamically set up like exception catches are also properly re-established. If you replay a DLC that has previously thrown an exception, that DLC can throw that exception again. However, any clean-up that mutates global state, like with-open-stream closing a stream, is permanent, making it a one-shot. > But they sound hugely better than standard Scheme-style continuations. If > I didn't have a cat sitting on me I'd go up & play with them right away (I > think Racket has them). They are controlled; like continuations with a leash. A regular continuation is like throwing a rock; but a delimited continuation is like a boomerang or yo-yo. A rock will return if someone throws it back, but a boomerang or yo-yo have a built in limit. The DLC gives us a clear contour where everything happens, such that the outside is not affected; a caller that sets up a contour for a DLC knows that the DLC cannot escape beyond that. And because it returns, it is a function; DLC's can be composed. We can (mapcar <some-dlc> list) etc. The DLC "thinks" it has the whole execution future ahead of itself, but it suddenly hits a brick wall at the delimited prompt, returning control to the caller, as well as the value that bubbled out. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <046-301-5902@kylheku.com> |
|---|---|
| Date | 2026-09-24 21:13 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <20260924140534.867@kylheku.com> |
| In reply to | #61689 |
On 2026-09-24, Kaz Kylheku <046-301-5902@kylheku.com> wrote:
> So to reiterate, I have not solved the resource problem for the
> low-level DLC's; there is no dynamic wind. But we have a working
> solution for thread-like abstractions built on top of DLC's.
> (Abstractions which do not reuse a continuation; do not repeat/replay
> the same captured computation.)
Here is a demo. We use a suspension to walk a cons-based tree
recursively and yield the items.
First, we just show how the items are yielded.
Then we repeat the exercise, but this time we turn on tracing
for the recursive function that does the tree walking.
We see how the tracing is correctly interleaved with our
calls to the suspension.
Because the suspension is absconding back to the top, all the trace stuff is
intact; it can be resumed like a thread to run its next time slice
and produce its next slice of trace output.
At the very end, it bubbles out, closing out all the traces, and
t is returned (because of the cond clause ((null obj))).
Each time we call [fn], a new delimited continuation is used,
which was prepared ahead of time by the previous yield-from
(or the initial obtain). The replacement of one delimited
continuation by another inside the fn object is destructive:
it has a single context, just like a thread's instruction pointer
being destructively updated.
$ txr
This is the TXR Lisp interactive listener of TXR 302.
Quit with :quit or Ctrl-D on an empty line. Ctrl-X ? for cheatsheet.
1> (defun yflatten-rec (obj)
(cond
((null obj))
((atom obj) (yield-from yflatten obj))
(t (yflatten-rec (car obj))
(yflatten-rec (cdr obj)))))
yflatten-rec
2> (defun yflatten (obj) (yflatten-rec obj))
yflatten
3> (defvar fn (obtain (yflatten '(1 2 (3 4 (5) 6)))))
fn
4> [fn]
1
5> [fn]
2
6> [fn]
3
7> [fn]
4
8> [fn]
5
9> [fn]
6
10> [fn]
t
11> (trace yflatten-rec)
nil
12> (defparm fn (obtain (yflatten '(1 2 (3 4 (5) 6)))))
fn
13> [fn]
(yflatten-rec ((1 2 (3 4 (5) 6)))
(yflatten-rec (1)
1
14> [fn]
nil)
(yflatten-rec ((2 (3 4 (5) 6)))
(yflatten-rec (2)
2
15> [fn]
nil)
(yflatten-rec (((3 4 (5) 6)))
(yflatten-rec ((3 4 (5) 6))
(yflatten-rec (3)
3
16> [fn]
nil)
(yflatten-rec ((4 (5) 6))
(yflatten-rec (4)
4
17> [fn]
nil)
(yflatten-rec (((5) 6))
(yflatten-rec ((5))
(yflatten-rec (5)
5
18> [fn]
nil)
(yflatten-rec (nil)
t)
t)
(yflatten-rec ((6))
(yflatten-rec (6)
6
19> [fn]
nil)
(yflatten-rec (nil)
t)
t)
t)
t)
t)
(yflatten-rec (nil)
t)
t)
t)
t)
t
20>
--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <046-301-5902@kylheku.com> |
|---|---|
| Date | 2026-09-24 21:21 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <20260924141728.576@kylheku.com> |
| In reply to | #61691 |
On 2026-09-24, Kaz Kylheku <046-301-5902@kylheku.com> wrote: > Each time we call [fn], a new delimited continuation is used, > which was prepared ahead of time by the previous yield-from > (or the initial obtain). The replacement of one delimited > continuation by another inside the fn object is destructive: > it has a single context, just like a thread's instruction pointer > being destructively updated. By the way, this is pretty awfully expensive. While, since we are Lisp programmers, we know the value of every [fn] call, we may not be aware of the cost. Making a delimited continuation is not cheap (in this implementation): we are consing up a new heap object which contains a snapshot of a slice of the run-time stack. Reviving it requires that memory to be copied to the current stack top, and various fix-ups to take place. This is a kind of "big gun" to solve a problem where that way of expressing it is worth the tradeoffj. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | George Neuner <gneuner2@comcast.net> |
|---|---|
| Date | 2026-09-27 08:02 -0400 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <2r0iblp5q8f2dm4v1ob7lorfg8reb9iqdt@4ax.com> |
| In reply to | #61681 |
On Tue, 22 Sep 2026 19:03:18 -0000 (UTC), Kaz Kylheku <046-301-5902@kylheku.com> wrote: ... about delimited continuations ... Hi Kaz, Apologies for the delay - it's been one of those weeks. I want to thank you for expounding on your explanation. I think I understand better now, but I'm going to have to play with it a bit. It would help greatly if I could look inside a compiler / runtime at a real implementation. Decsriptions are fine, but seeing it done is how I learn best. I know Racket has DCs, I just have no idea where in the code to look.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <046-301-5902@kylheku.com> |
|---|---|
| Date | 2026-09-29 17:03 +0000 |
| Subject | Re: delimited continuations - was Re: Resources to learn common lisp? |
| Message-ID | <20260928121459.651@kylheku.com> |
| In reply to | #61696 |
On 2026-09-27, George Neuner <gneuner2@comcast.net> wrote: > On Tue, 22 Sep 2026 19:03:18 -0000 (UTC), Kaz Kylheku ><046-301-5902@kylheku.com> wrote: > > ... about delimited continuations ... > > > Hi Kaz, > > Apologies for the delay - it's been one of those weeks. > > I want to thank you for expounding on your explanation. I think I > understand better now, but I'm going to have to play with it a bit. > > > It would help greatly if I could look inside a compiler / runtime at a > real implementation. Decsriptions are fine, but seeing it done is how > I learn best. The implementation I made is likely poorly comprehensible. It's a giant hack that directly manipulates the C stack, and (on reviving a continuation) does a conservative scan to fix up things that look like pointers. In the TXR source file "unwind.c", it starts at the definition of "struct cont". It is a small amount of code ending at the function uw_capture_cont. The function uw_push_cont_copy is also part of the implementation, outside of that code range. I will now take a moment to explain what these copy frames are about, and why they are needed. In compiled code, lexical variable bindings are on the stack, and so they get naturally copied when continuations are captured and revived: there is no sharing. However, in interpreted code, bindings are not stack allocated; they are dynamically allocated environment frames pushed onto their own environment stack by the evaluator. If our stack-copying continuation implementation deos not do anything special for these, a very Bad Thing will happen: continuations will share lexical variables: if a continuation mutates a variable, the original context as well as other instances of continuations which captured across that same context, will see the mutation! The solution is a copy-on-capture implementation: the interpreter (code in eval.c) installs copy handler frames when binding variables; these copy handlers will deeply copy the environment frames when a delimited continuation is captured, as well as when it is revived. -- TXR Programming Language: http://nongnu.org/txr Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal Mastodon: @Kazinator@mstdn.ca
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-27 20:39 +0000 |
| Message-ID | <116q7aa$1pm9l$3@dont-email.me> |
| In reply to | #61606 |
On Thu, 27 Aug 2026 14:43:07 -0000 (UTC), Waldek Hebisch wrote: > One way to implement continuations is to convert program to > "continuation passing style" and have garbage collection of the > stack. Continuation passing style means that you explicitely pass > next function to call to each function. And normally functions do > not return, simply tail-call to passed "continuation". The way I did this in GXScript was to implement stack frames as heap-based CallFrame objects, linked together in various ways. The interpreter context includes a pointer to the “current frame”, which in turn contains a pointer to the current procedure being executed, and the position within that procedure. Various transfer-of-control actions (return, yield etc) switch out the current frame for another by following relevant pointers in it to other frames. Conversely, entry into a new procedure means creating a new CallFrame around it, storing a pointer to the previously-current CallFrame in its “return_to” field, and setting the new frame as current. A Continuation object is a wrapper around a CallFrame which is cloned and kept as a template. The “enter()” method on the Continuation creates a new clone of the associated CallFrame template, and sets it as the current frame in the interpreter context. Nothing too complicated, really ... <https://gitlab.com/ldo/gxscript>
[toc] | [prev] | [next] | [standalone]
| From | Anton Antimo <anton@safunu.org> |
|---|---|
| Date | 2026-08-28 17:29 -0300 |
| Message-ID | <87v78u56qh.fsf@safunu.org> |
| In reply to | #61604 |
Paul Rubin <no.email@nospam.invalid> writes: > Anton Antimo <anton@safunu.org> writes: >>> Like try implementing Scheme continuations as macros in CL. >> Doug Hoyte does it in Let Over Lambda. > > I don't see how that is possible, other than by using the Turing > completeness of CL macros to implement Scheme, more or less. > Continuations automatically give you stackful coroutines and that > requires runtime support that's not built into CL. I haven't read that > book though. I got that wrong. It turns out TFB posted in Message-ID: <116ndfj$st1q$1@dont-email.me> two days ago that Paul Graham does in ``On Lisp''.
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-08-26 19:06 +0000 |
| Message-ID | <116ndfj$st1q$1@dont-email.me> |
| In reply to | #61598 |
[I have removed groups other than comp.lang.lisp, because some troll keeps adding them] Paul Rubin <no.email@nospam.invalid> wrote: > > Meh, if the old language can express the new idea at all, then the new > idea isn't that big of a change. Like try implementing Scheme > continuations as macros in CL. *On Lisp* does this (the code is rather questionable by today's standards but could be cleaned up). Based on some casual web searching there's at least one other person who has. And that's the point: languages which make this kind extension easy (which needs more than just functions between ASTs) remove barriers to the creation of new languages. Those new languages might be anything from CL (a much smaller Lisp with a bunch of fancy macros), CL with new binding or iteration or other constructs to entirely new languages like Coalton (statically-typed functional language) to whatever. I think that not having these barriers is a good thing. I'd really like to see a coherent argument *against* that position, which is not 'everyone will end up using their own idiolect', but I haven't so far. -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | bixbox <noreply@example.invalid> |
|---|---|
| Date | 2026-08-27 07:57 -0400 |
| Message-ID | <116p8ng$1eatb$2@dont-email.me> |
| In reply to | #61602 |
tfb <tfb@work.it.out> writes: > Paul Rubin <no.email@nospam.invalid> wrote: > >> >> Meh, if the old language can express the new idea at all, then the new >> idea isn't that big of a change. Like try implementing Scheme >> continuations as macros in CL. > And that's the point: languages which make this kind extension easy (which > needs more than just functions between ASTs) remove barriers to the > creation of new languages. Those new languages might be anything from CL > (a much smaller Lisp with a bunch of fancy macros), CL with new binding or > iteration or other constructs to entirely new languages like Coalton > (statically-typed functional language) to whatever. I think the elegance of lisp macro is that is nothing more that regular lisp syntax that transform homoiconic lisp, with just structural transformation, other language have a very poor macro system that is completely alien to the language himself. In my opinion C++ templates are a basically a simpler macro system but C++ templates have nothing to do with the core C++ in term of syntax and features. bix
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2026-08-24 13:19 -0700 |
| Message-ID | <116i90p$365ov$2@kst.eternal-september.org> |
| In reply to | #61568 |
tfb <tfb@work.it.out> writes:
> Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
>> I have no idea what you're talking about.
>
> You really don't, no.
>
> Hint: I am not talking about whether you know the language you are using
> well enough, but whether the language you are using provides the constructs
> you need to address the problem you are solving in it succinctly.
The person you're talking to has deliberately added cross-posts to
comp.lang.misc and comp.lang.c. If you must reply to this troll,
please limit your replies to comp.lang.lisp.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-08-24 20:37 +0000 |
| Message-ID | <116ia2a$36mfa$1@dont-email.me> |
| In reply to | #61581 |
Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote: > The person you're talking to has deliberately added cross-posts to > comp.lang.misc and comp.lang.c. If you must reply to this troll, > please limit your replies to comp.lang.lisp. > They did, didn't they. Sorry: my rather primitive newsreader makes that hard to see, but I should have noticed in any case. Sorry for wasting people's time (people who won't see this, but still, sorry). (I do have to wonder though: in the pop-psychology world, what term would be used for someone who adds a bunch of unrelated newsgroups in that way?) -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-09-15 15:18 -0400 |
| Message-ID | <87tsnql3wr.fsf@gmail.com> |
| In reply to | #61582 |
tfb <tfb@work.it.out> writes: > Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote: > They did, didn't they. Sorry: my rather primitive newsreader makes that > hard to see, but I should have noticed in any case. Sorry for wasting > people's time (people who won't see this, but still, sorry). I have been cought doing this myself. > (I do have to wonder though: in the pop-psychology world, what term would > be used for someone who adds a bunch of unrelated newsgroups in that way?) Nobody would read them. Some people are/were called spammers, flamers, market droids (automated advertisements). No big deal.
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-08-14 12:51 +0000 |
| Subject | Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <115n30i$2hot4$1@dont-email.me> |
| In reply to | #61467 |
I think it's worth understanding what macros actually mean. Most programming languages are dictatorships: a small, usually self-elected, self-important group of people designs a language, and thousands or millions of serfs have to suffer the consequences of their choices. Sometimes there is a pretense of some limited form of democracy: perhaps you, as a mere serf, can join the politburo and have a vote on what happens to the language. Sometimes this involves a payment to some nebulous standards organisation. Sometimes you can comment on suggested changes; sometimes people might listen to those comments. Sometimes the politburo is not largely made up of representatives (either explicit or implicit) of huge corporations who care not one jot about your interests. Changes, when they happen at all, take years. The language is ossified almost as soon as it exists. Almost always, for large systems, there will be tools built on top of the ossified substrate language which allow people to write programs in a way which actually matches their problem domain. Those tools are, in fact, *programming languages*, although they're usually implemented in an ad-hoc way by people who don't even realise that what they are doing is designing a programming language. They are therefore predictably horrible. If you have not used such an ad-hoc language you probably have not worked on a large system. Sometimes people make a better decision: they take an existing (usually dynamically typed as basically nobody likes static typing in the real world, usually either not compiled or dynamically compiled) language which has a good interface to the ossified substrate and expose functionality written in the ossified substrate to the more flexible surface language. NumPy and all its relations are the canonical example of this. That's at least better than the thing implemented using m4 on top of Fortran or whatever. But the thing written in m4 on top of Fortran is *still* better than using Fortran directly (and this is not because Fortran, today, is a bad language, which is is not, it's because it's an ossified language). Quite often what happens is that user or group of users of a language gets so fed up with this process that they design a new language which better meets their needs, perhaps starting with one of the ad-hoc languages above. That language then develops its own self-important politburo, becomes ossified. Recurse. Lisp chose something else. Lisp chose not to be a dictatorship, but to treat its users as adults capable of making their own decisions: decisions which were as good as the decisions of the politburo if not better. Decisions which, certainly, relfected the needs of the users making the decisions rather than some distant observer. Lisp looked at what *actually happens* in the world rather than in the heads of the politburo members, and it saw that what happened was the endless invention of new languages, either for specific problem domains, or just because the existing languages were so terrible. And it said, 'OK, let's make that a feature, not something you have to fight your way towards. Let's build a language whose defining feature is that it lets you build languages. Let's allow it to let you build languages *incrementally*, rather than putting some enormous barrier in your way. So you can take an existing language and define some extensions to it, and those extensions wil have exactly the same status as the original language does.' If you disagree with the decisions of the politburo you don't have to wait five years for the members to die and the decision to change, you can just make the system do what you want, today. Lisp understood that this means you have to make some compromises. The most significant is that the syntax of the language must have very low commitment to the semantics. That makes the language rather austere, but it means that you, the user of the language, get to say what the semantics is, without having to jump through some huge ring of fire and getting burned in the process. Lisp is a system built by people who understand how utterly stupid the claim that any programming language contains 90% of all the constructs anyone will ever need is. Lisp is a democracy. It is perhaps more than a democracy: it either is or is close to an anarchy. Anarchies obviously work only if their citizens are actually adults and if they are willing to cooperate with one another. But, well, Lisp assumes you are. If you're not an adult, or if you can't deal with cooperating with other people in the design of the language you're going to use, or if you like someone telling you what to do then, well, do what thou wilt. Lisp understands that a consequence of this anarchy is that different groups of users working on different projects will end up using differing languages, or dialects (*a shprakh iz a dyalekt mit an armey un flot*, famously), and it also understands that *that's what happens anyway*, except the languages and dialects people end up using are usually things created using tools whose only datatype is the string. Like I say: if you're happy to live as a serf in a dictactorship, or if you feel you might become a dictator, then that's OK. But please, stay the fuck away from those of us who want not to be serfs or dictators, and who want to make our own decisions in a community of our equals. -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2026-08-14 12:08 -0700 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <87v79co6zk.fsf@nightsong.com> |
| In reply to | #61480 |
tfb <tfb@work.it.out> writes: > Sometimes there is a pretense of some limited form of democracy: perhaps > you, as a mere serf, can join the politburo and have a vote on what happens > to the language. I haven't seen this url in a while but I guess it's time to post it again. https://www.marktarver.com/bipolar.html
[toc] | [prev] | [next] | [standalone]
Page 25 of 39 — ← Prev page 1 … 23 24 [25] 26 27 … 39 Next page →
Back to top | Article view | comp.lang.lisp
csiph-web