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 668 — 40 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? 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 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
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
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-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
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?) 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?) 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 (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: 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: 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
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 23 of 34 — ← Prev page 1 … 21 22 [23] 24 25 … 34 Next page →
| 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]
| From | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| Date | 2026-08-15 10:01 +0100 |
| Subject | Re: Macros |
| Message-ID | <27264.10961.451730.952075@parhasard.net> |
| In reply to | #61484 |
Ar an ceathrú lá déag de mí Lúnasa, scríobh Paul Rubin: > 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 Thanks, glad to have read that. -- ‘As I sat looking up at the Guinness ad, I could never figure out / How your man stayed up on the surfboard after fourteen pints of stout’ (C. Moore)
[toc] | [prev] | [next] | [standalone]
| From | Stéphane CARPENTIER <sc@fiat-linux.fr> |
|---|---|
| Date | 2026-08-15 12:58 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <6a806273$0$11459$426a74cc@news.free.fr> |
| In reply to | #61484 |
Le 14-08-2026, Paul Rubin <no.email@nospam.invalid> a écrit : > 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 This url is not that news and I never saw it anywhere. Maybe you already sent it but as my ISP is broken, I don't see all the messages. So it's the first time I see this link. Many thanks for this. It tells me things about me which don't concern you. But it told me things about LISP which always eluded me. The fact is that LISP is almost never used is the real life. I know stump, nyxt and guix are LISP programs, but they represent less than 0.[n]01% of users (I have no clue about the number of zeros represented by n here, but I'd say you can put a big number). Because if I know that LISP inspired a lot of things actually used in other programming languages, I know that nobody actually is learning LISP or computer history or anything that could explain why so many messages about LISP are shared compared with the number of people using it in a day to day basis. I'm not a programmer, but as computer science is allowing me to get things in my stomach (and as a French guy, what I put in my stomach is very important don't belittle that part), I have to follow up on what's happening in computer world. And I found a lot of things about LISP. Don't get me wrong. I find something like 1% of blogs/articles/whatever related to LISP. You can think it as small, but compared to what LISP is used in real life, it's huge. For each article/blog/whatever about C or C++ or COBOL, I can see at least ten articles/blog/whatever about LISP. And it's something. And I wondered about it from a long, long time. And this links explains a lot, thanks. -- Si vous avez du temps à perdre : https://scarpet42.gitlab.io
[toc] | [prev] | [next] | [standalone]
| From | Anton Antimo <anton@safunu.org> |
|---|---|
| Date | 2026-08-16 15:27 -0300 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <87tsot3opc.fsf@safunu.org> |
| In reply to | #61486 |
Stéphane CARPENTIER <sc@fiat-linux.fr> writes: [...] > I'm not a programmer, but as computer science is allowing me to get > things in my stomach (and as a French guy, what I put in my stomach is > very important don't belittle that part), I have to follow up on what's > happening in computer world. And I found a lot of things about LISP. > Don't get me wrong. I find something like 1% of blogs/articles/whatever > related to LISP. You can think it as small, but compared to what LISP is > used in real life, it's huge. For each article/blog/whatever about C or > C++ or COBOL, I can see at least ten articles/blog/whatever about LISP. > And it's something. Interesting.
[toc] | [prev] | [next] | [standalone]
| From | Anton Antimo <anton@safunu.org> |
|---|---|
| Date | 2026-08-16 15:26 -0300 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <874igt53cp.fsf@safunu.org> |
| In reply to | #61480 |
tfb <tfb@work.it.out> writes: > I think it's worth understanding what macros actually mean. [...] I think that's a pretty good description of the whole thing. Thanks for writing and posting it.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-08-22 00:00 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116aor8$1ubeu$1@paganini.bofh.team> |
| In reply to | #61480 |
tfb <tfb@work.it.out> wrote:
> 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.
Let me mention some decision of the polibiuro that I do not like.
1) I am a Unix man and doing
(compile-file "foo/bar.lisp" :output-file "baz/bar.fasl")
I want output to live is file "baz/bar.fasl" relative to current
directory. But polibiuro decided differently. I solve this in
Blub way, that is writing wrapper function that converts
"baz/bar.fasl" to absolute path and then calls 'compile-file'.
2) Program that I am developing has a user language which is implemented
converting user input to Lisp and then using 'eval' to evaluate it.
That is good, but there is a catch: from users point of view "T"
is a perfectly good variable name. But polibiuro decided that
it is reserved. I could try to work around this using packages,
but this has serious drawback. So I solve this in Blub way,
that is convertion replaces "T" by a different name.
3) I would like to so symbolic computation with arbitrary symbols.
For my purpose a symbol is always different from a list. But
polibiuro decided that "NIL" is identical to the empty list.
I would like "NIL" to be a constant symbol which when evaluated
gives empty list. That I could fix with packages. But there is
a catch: I want my symbols to print in natural way, without
package prefix and the same for empty list. And for that I did
not found a solution.
4) In a function I would like RETURN to return a current function,
even if there are blocks inside. I think that a macro could help
with this, but this would be rather hairy macro needind to walk
trough arbitrary Lisp code. So in Blub spirit I live with the
problem.
5) I create symbols from strings. For my sanity I want symbols
in source exactly (including case) to match strings used to
create symbols. But I dislike shouting, so I would prefer lower
case symbols in my source. I can partially solve this: I can
create a package called "common-lisp" (in lower case) and populate
it with lower case versions of symbols from "COMMON-LISP". That
somewhat works for functions, that is I can assign to 'symbol-funtion'
to get the same function as for corresponding symbol in "COMMON-LISP".
I could probably handle macros and special forms in similar way.
And probably constants too. I probably could handle variables
using symbol macros. But there is a trouble with functions: functions
in "COMMON-LISP" expect upper case keywords. To have lower case
keywords I would have to replace each Common Lisp function by a
wrapper which converts keyword arguments. And presumably, Lisp
printer would print "expanded" version of my code, so I would
loose correspondence with my sources. So ATM in Blub spirit
I decided that it is too much work to change the language.
BTW: IIUC Allegro CL has resonable solution to this. But I am
using free Lisp-s and unwilling to swich to closed source
system.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-22 01:23 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116atlm$olsn$2@dont-email.me> |
| In reply to | #61528 |
On Sat, 22 Aug 2026 00:00:42 -0000 (UTC), Waldek Hebisch wrote: > Let me mention some decision of the polibiuro that I do not like. > > 1) I am a Unix man and doing > > (compile-file "foo/bar.lisp" :output-file "baz/bar.fasl") > > I want output to live is file "baz/bar.fasl" relative to current > directory. But polibiuro decided differently. I solve this in > Blub way, that is writing wrapper function that converts > "baz/bar.fasl" to absolute path and then calls 'compile-file'. Note how the defaults for input-file are filled in from *input-pathname-defaults*, but the same does not apply to output-file: <https://www.lispworks.com/documentation/HyperSpec/Body/f_cmp_fi.htm>. This is what I mean by Common Lisp being full of baggage for catering to non-POSIX operating systems which are all extinct now. > 2) Program that I am developing has a user language which is > implemented converting user input to Lisp and then using 'eval' to > evaluate it. That is good, but there is a catch: from users point of > view "T" is a perfectly good variable name. But polibiuro decided > that it is reserved. I could try to work around this using packages, > but this has serious drawback. So I solve this in Blub way, that is > convertion replaces "T" by a different name. Or alternatively, you shouldn’t be equivalencing user-defined variables directly to Lisp variables. > 3) I would like to so symbolic computation with arbitrary symbols. > For my purpose a symbol is always different from a list. But > polibiuro decided that "NIL" is identical to the empty list. I would > like "NIL" to be a constant symbol which when evaluated gives empty > list. You want more than one empty-list object? I think that is traditionally treated as a “singleton” (not just in Lisp), which means the answer is “no”.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-08-22 12:07 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116c3ef$254du$1@paganini.bofh.team> |
| In reply to | #61530 |
Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
>
>> 3) I would like to so symbolic computation with arbitrary symbols.
>> For my purpose a symbol is always different from a list. But
>> polibiuro decided that "NIL" is identical to the empty list. I would
>> like "NIL" to be a constant symbol which when evaluated gives empty
>> list.
>
> You want more than one empty-list object? I think that is
> traditionally treated as a “singleton” (not just in Lisp), which means
> the answer is “no”.
No, a single empty list object. I just want symbol NIL to be
a real symbol distingushable from empty list. Consider
* (setf a '( 1 ))
(1)
* (cdr a)
NIL
* (symbolp (cdr a))
T
* (eq (cdr a) 'NIL)
T
It would be better is the second line gave empty list, not a symbol.
More important third and fourth line both should return false.
OTOH the following still should hold
* (eq (cdr a) NIL)
T
* (if (cdr a) "bad" "good")
"good"
And compare the above to
(setf b (cdr a))
NIL
* (eq (cdr a) 'b)
NIL
* (eq (cdr a) b)
T
b is ordirnary symbol, after assignment evaluating b gives empty
list, but _symbol_ b is different than empty list. The same
should hold for NIL.
If you think a bit current behaviour is highly unintuitive and
requires some trickery to implement but is mandated by the
Common Lisp specification.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-22 22:24 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116d7ji$1gcgq$2@dont-email.me> |
| In reply to | #61533 |
On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote: > I just want symbol NIL to be a real symbol distingushable from empty > list. But this is a fundamental part of the traditional way that Lisp works: an “empty list” isn’t really a list at all, it is just a pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the need for a special symbol to denote it. In Python, on the other hand, an empty list is constructed with an expression like “[]”, an empty tuple with “()”, and both of these are distinct from the “None” object.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-08-22 23:08 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116da5p$27baf$2@paganini.bofh.team> |
| In reply to | #61535 |
Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
> On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:
>
>> I just want symbol NIL to be a real symbol distingushable from empty
>> list.
>
> But this is a fundamental part of the traditional way that Lisp works:
> an “empty list” isn’t really a list at all, it is just a pointer that
> points nowhere (in C: NULL; in Lisp: NIL). Hence the need for a
> special symbol to denote it.
No, you do not need special symbol to denote empty list, "()" works
fine:
* ()
NIL
And I do not want to upset people that write NIL to get empty
list, writing NIL would still give you empty list.
Concering tradition, I suspect that basically the same behaviour
appears in newer Lisp system "because it was always done that way".
But it seem to be rather specific to Lisp, there are other system
having similar handling of lists and I know of no other repeating
Lisp misfeature.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-22 23:22 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116davv$1gcgq$6@dont-email.me> |
| In reply to | #61536 |
On Sat, 22 Aug 2026 23:08:44 -0000 (UTC), Waldek Hebisch wrote:
> Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
>>
>> On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:
>>
>>> I just want symbol NIL to be a real symbol distingushable from
>>> empty list.
>>
>> But this is a fundamental part of the traditional way that Lisp
>> works: an “empty list” isn’t really a list at all, it is just a
>> pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the
>> need for a special symbol to denote it.
>
> No, you do not need special symbol to denote empty list, "()" works
> fine:
>
> * ()
> NIL
But that equivalence is the very thing you were complaining about.
Whereas in Python:
ldo@theon:~> python3
Python 3.14.6 (main, Jun 10 2026, 18:54:31) [GCC 15.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> [] == []
True
>>> () == ()
True
>>> () == None
False
>>> [] == None
False
> Concering tradition, I suspect that basically the same behaviour
> appears in newer Lisp system "because it was always done that way".
It has to do with the implementation. A list consists of cons
structures linked together via pointers. An empty list consists of no
cons structures, hence there is nothing to point to.
> But it seem to be rather specific to Lisp, there are other system
> having similar handling of lists and I know of no other repeating
> Lisp misfeature.
I can think of one: multiple-value-return. This requires the creation
of a whole mechanism involving data structures that are not really
data structures.
Python and JavaScript have a simpler approach to the same concept:
destructuring assignment.
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-08-23 00:23 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116dehm$2cs8g$1@paganini.bofh.team> |
| In reply to | #61537 |
Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
> On Sat, 22 Aug 2026 23:08:44 -0000 (UTC), Waldek Hebisch wrote:
>
>> Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
>>>
>>> On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:
>>>
>>>> I just want symbol NIL to be a real symbol distingushable from
>>>> empty list.
>>>
>>> But this is a fundamental part of the traditional way that Lisp
>>> works: an “empty list” isn’t really a list at all, it is just a
>>> pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the
>>> need for a special symbol to denote it.
>>
>> No, you do not need special symbol to denote empty list, "()" works
>> fine:
>>
>> * ()
>> NIL
>
> But that equivalence is the very thing you were complaining about.
I am affraid you do not understand what I want. I can do the
following:
* (shadow "NIL")
T
* (defconstant nil ())
NIL
* (eq 'NIL NIL)
COMMON-LISP:NIL
* NIL
COMMON-LISP:NIL
* ()
COMMON-LISP:NIL
*
So, I can have my NIL that is different than empty list, but which
when evaluated gives empty list. After that I can distinguish
"my" symbols from lists. The problem which I can not solve is
that empty list is printed as 'COMMON-LISP:NIL' instead of '()'.
And Common Lisp functions still will treat empty list as a symbol.
>> Concering tradition, I suspect that basically the same behaviour
>> appears in newer Lisp system "because it was always done that way".
<snip>
> It has to do with the implementation. A list consists of cons
> structures linked together via pointers. An empty list consists of no
> cons structures, hence there is nothing to point to.
Actually, in Common Lisp empty list is almost a cons cell. Namely,
you can do:
* (car nil)
NIL
* (cdr nil)
NIL
*
Usually it is implemented by special data in memory that looks like
a cons cell, with CAR and CDR that point to itself. Function that
check for NIL simply compare address with address of NIL.
Common Lisp arranges data structure representing NIL so that it
also looks like a symbol. Quite possible that this led to some
simplification in first implementation (say skipping explicit case
for empty list in printing code). But it actually is a buden
for modern implementations. Not a big burden, but implementers
must make sure that layout of cons cell and layout of symbols
are compatible enough. Or alternatively sprinkle generated code
with checks for special case of empty list which would likely
decrease performance.
>> But it seem to be rather specific to Lisp, there are other system
>> having similar handling of lists and I know of no other repeating
>> Lisp misfeature.
>
> I can think of one: multiple-value-return. This requires the creation
> of a whole mechanism involving data structures that are not really
> data structures.
multiple-value-return is a different story. One can easily get
equivalent effect with explict stack. And one can implement
multiple values using a stack + markers. But AFAICS motivation
for multiple values is to generate more efficient code and more
efficient implementation will return first few values in
machine registers. That saves allocation of intermediate container
that would became garbage after return. In other words,
multiple values require extra effort from implementation and
programmers using them, but leads to more efficient code.
One can debate if the effect is worth the effoet. OTOH nothing
forces you to return multiple values from your functions.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-08-23 15:47 -0400 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <877blgty9a.fsf@gmail.com> |
| In reply to | #61533 |
antispam@fricas.org (Waldek Hebisch) writes: > Lawrence D’Oliveiro <ldo@nz.invalid> wrote: >> >>> 3) I would like to so symbolic computation with arbitrary symbols. >>> For my purpose a symbol is always different from a list. But >>> polibiuro decided that "NIL" is identical to the empty list. I would >>> like "NIL" to be a constant symbol which when evaluated gives empty >>> list. >> >> You want more than one empty-list object? I think that is >> traditionally treated as a “singleton” (not just in Lisp), which means >> the answer is “no”. > > No, a single empty list object. I just want symbol NIL to be > a real symbol distingushable from empty list. Consider I usually use deconstant or define symbol macro. (deconst +eof+ '+eof+) ; SLIME 2.27 CL-USER> (defconstant +eof+ '+eof+) CL-USER> +eof+ +EOF+ CL-USER> (defconstant +eol+ '(nil . nil)) +EOL+ CL-USER> +eol+ (NIL) CL-USER>
[toc] | [prev] | [next] | [standalone]
| From | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| Date | 2026-08-23 21:57 +0100 |
| Subject | Re: Macros |
| Message-ID | <27275.24221.13350.260382@parhasard.net> |
| In reply to | #61542 |
Ar an tríú lá is fiche de mí Lúnasa, scríobh steve g.: > antispam@fricas.org (Waldek Hebisch) writes: > > > Lawrence D’Oliveiro <ldo@nz.invalid> wrote: > >> > >>> 3) I would like to so symbolic computation with arbitrary symbols. For > >>> my purpose a symbol is always different from a list. But polibiuro > >>> decided that "NIL" is identical to the empty list. I would like "NIL" to > >>> be a constant symbol which when evaluated gives empty list. > >> > >> You want more than one empty-list object? I think that is traditionally > >> treated as a “singleton” (not just in Lisp), which means the answer is > >> “no”. > > > > No, a single empty list object. I just want symbol NIL to be > > a real symbol distingushable from empty list. Consider If your priority is purity, there is not reason for end-of-list to be a symbol. (defconstant end-of-list (let ((result (cons 0 0))) (setf (car result) result (cdr result) result))) That’s a constant for which (car end-of-list) will give end-of-list as will (cdr end-of-list). Your implementation will need to handle circularity with grace. This makes the implementation of #'listp simpler; it just becomes #'consp. You would need to use #'endp to detect the end of the list, but that’s recommended anyway. Nothing is compatible with this and you will have constant work if you wish to use your lists like that. But, yes, it’s more semantically pure. > I usually use deconstant or define symbol macro. > > (deconst +eof+ '+eof+) > > ; SLIME 2.27 > CL-USER> (defconstant +eof+ '+eof+) > > CL-USER> +eof+ > +EOF+ > > CL-USER> (defconstant +eol+ '(nil . nil)) > +EOL+ > CL-USER> +eol+ > (NIL) > CL-USER> -- ‘As I sat looking up at the Guinness ad, I could never figure out / How your man stayed up on the surfboard after fourteen pints of stout’ (C. Moore)
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-23 22:21 +0000 |
| Subject | Re: Macros |
| Message-ID | <116frp8$29a3t$4@dont-email.me> |
| In reply to | #61544 |
On Sun, 23 Aug 2026 21:57:01 +0100, Aidan Kehoe wrote: > If your priority is purity, there is not reason for end-of-list to > be a symbol. There is this assumption, is there, that “list” must mean the traditional Lisp implementation in terms of two-field cells, so processing always involves a lot of pointer-chasing? I don’t think there is any such assumption in Python, just for example. Expressions of the form “[...]” are said to construct “lists”, but the underlying implementation is more likely to be a flex array (to use Algol 68 terminology).
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-08-23 22:37 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116fsne$2h3iu$3@paganini.bofh.team> |
| In reply to | #61542 |
steve g <Sgonedes1977@gmail.com> wrote:
> antispam@fricas.org (Waldek Hebisch) writes:
>
>> Lawrence D’Oliveiro <ldo@nz.invalid> wrote:
>>>
>>>> 3) I would like to so symbolic computation with arbitrary symbols.
>>>> For my purpose a symbol is always different from a list. But
>>>> polibiuro decided that "NIL" is identical to the empty list. I would
>>>> like "NIL" to be a constant symbol which when evaluated gives empty
>>>> list.
>>>
>>> You want more than one empty-list object? I think that is
>>> traditionally treated as a “singleton” (not just in Lisp), which means
>>> the answer is “no”.
>>
>> No, a single empty list object. I just want symbol NIL to be
>> a real symbol distingushable from empty list. Consider
>
>
>
> I usually use deconstant or define symbol macro.
>
> (deconst +eof+ '+eof+)
>
> ; SLIME 2.27
> CL-USER> (defconstant +eof+ '+eof+)
>
> CL-USER> +eof+
> +EOF+
>
> CL-USER> (defconstant +eol+ '(nil . nil))
> +EOL+
> CL-USER> +eol+
> (NIL)
> CL-USER>
Yes, I can get half way by using packages and shadowing real NIL. But
in such approach Common Lisp still considers empty list to be a symbol
and prints it a symbol. More radical approach as above means that
I can no longer use standard Common Lisp functions so I need to add
"buggy and slow implementation of half of the Common Lisp" to my
program.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-08-23 23:47 +0000 |
| Subject | Re: Macros (was Re: Resources to learn common lisp?) |
| Message-ID | <116g0qj$2apg7$2@dont-email.me> |
| In reply to | #61546 |
On Sun, 23 Aug 2026 22:37:36 -0000 (UTC), Waldek Hebisch wrote: > More radical approach as above means that I can no longer use > standard Common Lisp functions so I need to add "buggy and slow > implementation of half of the Common Lisp" to my program. Some have proposed coming up with more modern Lisps as an alternative to Common Lisp. Are any of them realistic yet?
[toc] | [prev] | [next] | [standalone]
| From | Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> |
|---|---|
| Date | 2026-08-12 13:18 +0800 |
| Message-ID | <RmTeS.214701$la89.42778@fx06.ams4> |
| In reply to | #61340 |
On 09/08/2026 4:52 PM, tfb wrote: > Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote: >> >> I've found the Common Lisp macro system annoying enough that I rarely >> use it. I'm OK with functions most of the time, and CLOS the rest of >> the time. And only resort to macros when I can't do anything else in >> the situation. >> > > It is so weird that people use a language whose defining feature is the > incremental construction of languages and then say they don't use that > feature. I mean, I'm aware people do that, but it's just so fucking weird. > No the subject of /weird/, I've also found it highly bizarre, if not outright disturbing, that people don't use do ... while(); in C. It's an eminently useful structured programming pattern. On the subject of Common Lisp, I find it more than disturbing when a codebase lacks the basic usage of hash tables. https://www.sbcl.org/manual/#hash-table-extensions Happy coding disturbing things! -- Johann | email: invalid -> com | http://www.myrkraverk.com/blog/ I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
[toc] | [prev] | [next] | [standalone]
| From | bixbox <noreply@example.invalid> |
|---|---|
| Date | 2026-08-12 10:16 +0200 |
| Message-ID | <115ha5n$kncd$2@dont-email.me> |
| In reply to | #61405 |
Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes: > On 09/08/2026 4:52 PM, tfb wrote: >> Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote: > No the subject of /weird/, I've also found it highly bizarre, if not > outright disturbing, that people don't use do ... while(); in C. It's > an eminently useful structured programming pattern. Finally, every time that I open a PR with that pattern I get questioned and frown. It's such disturbing. > > On the subject of Common Lisp, I find it more than disturbing when a > codebase lacks the basic usage of hash tables. > > https://www.sbcl.org/manual/#hash-table-extensions unless you find some code base that use hash table all over the place. :) bix
[toc] | [prev] | [next] | [standalone]
Page 23 of 34 — ← Prev page 1 … 21 22 [23] 24 25 … 34 Next page →
Back to top | Article view | comp.lang.lisp
csiph-web