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-14 01:36 +0800 |
| Articles | 20 on this page of 628 — 38 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? 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? 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? 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
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: 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? 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: 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
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
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
Page 5 of 32 — ← Prev page 1 … 3 4 [5] 6 7 … 32 Next page →
| From | yeti <yeti@tilde.institute> |
|---|---|
| Date | 2026-07-03 12:51 +0042 |
| Subject | Re: Python blanks |
| Message-ID | <87v7awl1fb.fsf@dear-messner.dont-email.me> |
| In reply to | #61130 |
George Neuner <gneuner2@comcast.net> wrote: > from "Open heart with Guido Van Rosuum" > https://impythonist.wordpress.com/2014/02/16/open-heart-with-guido-van-rosuuma-lost-interview-of-python-creator-part2/ > > || The choice of indentation for grouping was not a novel concept > || in Python; I inherited this from ABC, but it also occurred in > || occam, an older language. I tried ABC and its integrated editor just was annoying. It only allowed to enter what was expected at the current cursor position and indentation always was on autopilot. I did not know a way to use an external editor for ABC. Maybe I just did not find it in its docs. But it was meant to be like an all-in-one solution even abstracting file access away from the user. Interesting and strange at the same time, but IMO hard to get used to. When Python-0.x appeared I at least could use the editor of my choice, but being forced to use indentation still annoys me today no matter which language demands it. I'm indenting my code in nearly all languages, but I dislike if it is more than pure aesthetics. . Just for a smile: Bython Python with braces. Because Python is awesome, but whitespace is awful. <https://github.com/mathialo/bython>
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2026-07-03 11:34 -0700 |
| Subject | Re: Python blanks |
| Message-ID | <87a4s7ylb5.fsf@nightsong.com> |
| In reply to | #61136 |
yeti <yeti@tilde.institute> writes: > Python with braces. Because Python is awesome, but whitespace is awful. "Although some people have initial resistance to the ( indentation as block structure | parentheses) most come to ( accept | deeply appreciate ) them." Peter Norvig, Python vs Lisp comparison (May 2000) https://www.norvig.com/python-lisp.html
[toc] | [prev] | [next] | [standalone]
| From | Lars Brinkhoff <lars.spam@nocrew.org> |
|---|---|
| Date | 2026-07-04 04:03 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <7wjyrbv1t6.fsf@junk.nocrew.org> |
| In reply to | #61137 |
Paul Rubin claims Peter Norvig wrote: > "Although some people have initial resistance to the ( indentation as > block structure | parentheses) most come to ( accept | deeply > appreciate ) them." You don't have to deeply appreciate them. Most programming languages are workable unless you are too hung up about perceived flaws. (I normally wouldn't have posted this smug remark, but I feel it's appropriate in comp.lang.lisp.)
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-07-04 04:18 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112a1ig$3scqc$7@dont-email.me> |
| In reply to | #61147 |
On Sat, 04 Jul 2026 04:03:33 +0000, Lars Brinkhoff wrote: > Most programming languages are workable unless you are too hung up > about perceived flaws. I managed to annoy a PHP aficionado in another group by pointing out how crap that particular language is.
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-07-09 11:34 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112o0vr$bouu$1@dont-email.me> |
| In reply to | #61137 |
Paul Rubin <no.email@nospam.invalid> wrote:
> yeti <yeti@tilde.institute> writes:
>> Python with braces. Because Python is awesome, but whitespace is awful.
>
> "Although some people have initial resistance to the
> ( indentation as block structure | parentheses)
> most come to ( accept | deeply appreciate ) them."
>
> Peter Norvig, Python vs Lisp comparison (May 2000)
> https://www.norvig.com/python-lisp.html
>
And he's right. I've written lots of Python, and I have a fairly deep
hatred of the language as a result. But indentation as block structure is
entirely a non-issue for me: it's entirely fine. This is not a thing which
is wrong with Python.
What I do find amusing us when some bozo turns up and reformats
(defun foo (...)
(...
...
(...
(... ...))))
As
(defun foo (...)
(...
...
(... ...)
)
)
I mean, for
def foo (...):
if ...:
if ...:
...
do they leave two lines which are blank except for suitable numbers of
leading spaces after the definition?
--
tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | ram@zedat.fu-berlin.de (Stefan Ram) |
|---|---|
| Date | 2026-07-09 13:15 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <parentheses-20260709141223@ram.dialup.fu-berlin.de> |
| In reply to | #61197 |
tfb <tfb@work.it.out> wrote or quoted:
>What I do find amusing us when some bozo turns up and reformats
>(defun foo (...)
> (...
> ...
> (...
> (... ...))))
>As
>(defun foo (...)
> (...
> ...
> (... ...)
> )
>)
I'd not call a change a "reformat" when a gentleman changes
the number of parentheses and who knows what else ("...").
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-07-09 13:24 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112o7e6$dpuh$1@dont-email.me> |
| In reply to | #61203 |
Stefan Ram <ram@zedat.fu-berlin.de> wrote:
>
>
> I'd not call a change a "reformat" when a gentleman changes
> the number of parentheses and who knows what else ("...").
>
Yeah, I fucked up, but but you get the point.
--
tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-07-09 14:01 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112o9kb$3cs6m$1@paganini.bofh.team> |
| In reply to | #61197 |
tfb <tfb@work.it.out> wrote:
> Paul Rubin <no.email@nospam.invalid> wrote:
>> yeti <yeti@tilde.institute> writes:
>>> Python with braces. Because Python is awesome, but whitespace is awful.
>>
>> "Although some people have initial resistance to the
>> ( indentation as block structure | parentheses)
>> most come to ( accept | deeply appreciate ) them."
>>
>> Peter Norvig, Python vs Lisp comparison (May 2000)
>> https://www.norvig.com/python-lisp.html
>>
>
> And he's right. I've written lots of Python, and I have a fairly deep
> hatred of the language as a result. But indentation as block structure is
> entirely a non-issue for me: it's entirely fine. This is not a thing which
> is wrong with Python.
>
> What I do find amusing us when some bozo turns up and reformats
>
> (defun foo (...)
> (...
> ...
> (...
> (... ...))))
>
> As
>
> (defun foo (...)
> (...
> ...
> (... ...)
> )
> )
>
> I mean, for
>
> def foo (...):
> if ...:
> if ...:
> ...
>
> do they leave two lines which are blank except for suitable numbers of
> leading spaces after the definition?
In many cases there is quantitative difference. Consider the following
simple function:
NRTreplaceAllLocalReferences(form) ==
$devaluateList : local := []
NRTputInLocalReferences(form)
It gets translated to:
(DEFUN |NRTreplaceAllLocalReferences| (|form|)
(PROG (|$devaluateList|)
(DECLARE (SPECIAL |$devaluateList|))
(RETURN
(PROGN (SETQ |$devaluateList| NIL) (|NRTputInLocalReferences| |form|)))))
Since the second is mechanically generated using output of Lisp printer
is OK. But hand written version probably would use 5 indentation levels:
(DEFUN |NRTreplaceAllLocalReferences| (|form|)
(PROG (|$devaluateList|)
(DECLARE (SPECIAL |$devaluateList|))
(RETURN
(PROGN
(SETQ |$devaluateList| NIL)
(|NRTputInLocalReferences| |form|)))))
That is still managable, but there is some temptation to make structure
clearer. And since Lisp version has a lot of parentheses why do not
take advantage of them to make structure more visible?
Of course, hand written version almost surely would get rid of
'RETURN' and following 'PROGN', but in general Lisp tend to need
a lot of indentation levels and structure may get more complicated.
Consider:
(defun c_args_as_string (arguments)
(cond
((null arguments) "")
(t (let ((res (c_type_as_string (nth 1 (car arguments)))))
(dolist (el (rest arguments))
(setf res (concatenate 'string res ", "
(c_type_as_string (nth 1 el)))))
res)))
)
I do not say it is great code, but I find it easier to handle than
more traditional Lisp style.
I am not a big fan of indented syntax, but for me it is in not
a big trouble. And when using indented syntax I feel less pressure
to put end markers on syntactic constructs (compared to Lisp or C).
Part of the reason is that in indented syntax indentation can not
be misleading, while in Lisp there is always some danger that
author of the code has indented it in incorrect way. But
possibly it is just normal human inconsistence.
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-07-09 14:39 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112obr1$f7en$1@dont-email.me> |
| In reply to | #61206 |
Waldek Hebisch <antispam@fricas.org> wrote: > > > Consider: > > (defun c_args_as_string (arguments) > (cond > ((null arguments) "") > (t (let ((res (c_type_as_string (nth 1 (car arguments))))) > (dolist (el (rest arguments)) > (setf res (concatenate 'string res ", " > (c_type_as_string (nth 1 el))))) > res))) > ) > > I do not say it is great code, but I find it easier to handle than > more traditional Lisp style. > OK, that's just weird. Everything is fine and you've got lots of close parens at the ends of lines in the standard way, but then something breaks and you have the final close paren on its own at the left margin. I can't even begin to understand what motivates that. But the same question: if you wrote it in Python, would you leave an extra little blank line for that weird closing paren? -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | antispam@fricas.org (Waldek Hebisch) |
|---|---|
| Date | 2026-07-09 21:03 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112p2a4$3eqo2$1@paganini.bofh.team> |
| In reply to | #61207 |
tfb <tfb@work.it.out> wrote:
> Waldek Hebisch <antispam@fricas.org> wrote:
>>
>>
>> Consider:
>>
>> (defun c_args_as_string (arguments)
>> (cond
>> ((null arguments) "")
>> (t (let ((res (c_type_as_string (nth 1 (car arguments)))))
>> (dolist (el (rest arguments))
>> (setf res (concatenate 'string res ", "
>> (c_type_as_string (nth 1 el)))))
>> res)))
>> )
>>
>> I do not say it is great code, but I find it easier to handle than
>> more traditional Lisp style.
>>
>
> OK, that's just weird. Everything is fine and you've got lots of close
> parens at the ends of lines in the standard way, but then something breaks
> and you have the final close paren on its own at the left margin. I can't
> even begin to understand what motivates that.
If you look at rational factors: I need to see where given piece of
code ends. In bigger function with multiple blocks inside I would
put some parentheses in separate lines to signal ends of blocks.
There is also issue of seeing what is changed. Code frequently
gets added at end of existing functions. Separate "end"
parenthesis means that in such case old lines are unchanged and
only new lines get added. Version with parentheses at end of
line needs to move closing parentheses from old line to new
one.
I trying to be conservative with putting end parentheses on
separate lines. One, doing this on too many constructs would
add too many extra lines. Second, putting such parentheses
in too many places would limit their value, they would be no
longer good cue. Third, really small pieces of code are
managable without extra cues, it is bigger pieces when it
matters. Fourh, I want to limit dissatisfaction of Lispers
used to traditional style in case they need to work on code
that I write.
> But the same question: if you wrote it in Python, would you leave an extra
> little blank line for that weird closing paren?
First, I write very little Python, but I make a lot of use of
other compiler using indentation based syntax. In code that I
write I normally put blank line between functions (that regardless
of indentation based syntax, I do the same in Lisp and C). I
experimented with putting 2 blank lines between functions, but
currently it seems that 1 blank line works better for me. I do
not put blank lines between blocks. Transition between block is
a good place to put comment if I need one but I do not put comments
just to mark end of a block. I may decide that I need such comment
if a block is really large, but I do not remember writing such
block.
BTW: I apply rule "no tabs except when requied by syntax" and
"no trailing white space".
--
Waldek Hebisch
[toc] | [prev] | [next] | [standalone]
| From | tfb <tfb@work.it.out> |
|---|---|
| Date | 2026-07-09 21:23 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112p3g3$nnak$1@dont-email.me> |
| In reply to | #61210 |
Waldek Hebisch <antispam@fricas.org> wrote: > > If you look at rational factors: I need to see where given piece of > code ends. It ends when the next top-level definition starts at the left margin. Same thing fir Python. How hard can it be? I mean, may be if you're using ed to type in your code? But I give up: weird-paren cranks may be unique to Lisp but they're still cranks. -- tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-07-09 23:09 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112p9nq$p5ou$6@dont-email.me> |
| In reply to | #61210 |
On Thu, 9 Jul 2026 21:03:02 -0000 (UTC), Waldek Hebisch wrote: > I trying to be conservative with putting end parentheses on separate > lines. One, doing this on too many constructs would add too many > extra lines. Second, putting such parentheses in too many places > would limit their value, they would be no longer good cue. So long as beginning and ending parentheses are at the same indentation level, they can still provide a very useful cue.
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-08-04 23:05 -0400 |
| Subject | Re: Python blanks |
| Message-ID | <87ldaltgfi.fsf@gmail.com> |
| In reply to | #61210 |
antispam@fricas.org (Waldek Hebisch) writes: > tfb <tfb@work.it.out> wrote: >> Waldek Hebisch <antispam@fricas.org> wrote: >>> >>> >>> Consider: >>> >>> (defun c_args_as_string (arguments) >>> (cond >>> ((null arguments) "") >>> (t (let ((res (c_type_as_string (nth 1 (car arguments))))) >>> (dolist (el (rest arguments)) >>> (setf res (concatenate 'string res ", " >>> (c_type_as_string (nth 1 el))))) >>> res))) >>> ) >>> >>> I do not say it is great code, but I find it easier to handle than >>> more traditional Lisp style. >>> >> >> OK, that's just weird. Everything is fine and you've got lots of close >> parens at the ends of lines in the standard way, but then something breaks >> and you have the final close paren on its own at the left margin. I can't >> even begin to understand what motivates that. > > If you look at rational factors: I need to see where given piece of > code ends. In bigger function with multiple blocks inside I would > put some parentheses in separate lines to signal ends of blocks. > There is also issue of seeing what is changed. Code frequently > gets added at end of existing functions. Separate "end" > parenthesis means that in such case old lines are unchanged and > only new lines get added. Version with parentheses at end of > line needs to move closing parentheses from old line to new > one. Hear Hear! IMHO python looks like pascal. Pascal is a great language but do not mess up the begin/end statements! The semicolons should be standard. I have the same issue with GO. This is starting to remind me of sendmail.cf :) > I trying to be conservative with putting end parentheses on > separate lines. One, doing this on too many constructs would > add too many extra lines. Second, putting such parentheses > in too many places would limit their value, they would be no > longer good cue. Third, really small pieces of code are > managable without extra cues, it is bigger pieces when it > matters. Fourh, I want to limit dissatisfaction of Lispers > used to traditional style in case they need to work on code > that I write. > >> But the same question: if you wrote it in Python, would you leave an extra >> little blank line for that weird closing paren? [ ... ] > "no trailing white space". Hear hear!
[toc] | [prev] | [next] | [standalone]
| From | George Neuner <gneuner2@comcast.net> |
|---|---|
| Date | 2026-08-06 09:57 -0400 |
| Subject | Re: Python blanks |
| Message-ID | <n4497ltpmlspmmrrkijemeoptre4b8pmh9@4ax.com> |
| In reply to | #61294 |
On Tue, 04 Aug 2026 23:05:53 -0400, steve g <Sgonedes1977@gmail.com> wrote: >antispam@fricas.org (Waldek Hebisch) writes: > >> tfb <tfb@work.it.out> wrote: >>> Waldek Hebisch <antispam@fricas.org> wrote: >>>> >>>> >>>> Consider: >>>> >>>> (defun c_args_as_string (arguments) >>>> (cond >>>> ((null arguments) "") >>>> (t (let ((res (c_type_as_string (nth 1 (car arguments))))) >>>> (dolist (el (rest arguments)) >>>> (setf res (concatenate 'string res ", " >>>> (c_type_as_string (nth 1 el))))) >>>> res))) >>>> ) >>>> >>>> I do not say it is great code, but I find it easier to handle than >>>> more traditional Lisp style. >>>> >>> >>> OK, that's just weird. Everything is fine and you've got lots of close >>> parens at the ends of lines in the standard way, but then something breaks >>> and you have the final close paren on its own at the left margin. I can't >>> even begin to understand what motivates that. >> >> If you look at rational factors: I need to see where given piece of >> code ends. In bigger function with multiple blocks inside I would >> put some parentheses in separate lines to signal ends of blocks. >> There is also issue of seeing what is changed. Code frequently >> gets added at end of existing functions. Separate "end" >> parenthesis means that in such case old lines are unchanged and >> only new lines get added. Version with parentheses at end of >> line needs to move closing parentheses from old line to new >> one. > >Hear Hear! I also like to demarcate code /blocks/ vertically - be it with parentheses or curly braces or begin/end. > IMHO python looks like pascal. Pascal is a great language but >do not mess up the begin/end statements! The semicolons should be >standard. I have the same issue with GO. This is starting to remind me >of sendmail.cf :) I liked Modula 3 much better ... Pascal with most of its issues fixed. But there still were begin/end to demarcate lists of statements. Begin/End didn't bother me at all - code is meant for humans to read as well as computers to run. Pascal and its follow-on languages are easy to read ... and unlike C/C++ there is only one syntax to dereference a pointer. But Python looks more to me like Logo than like Pascal. And it's performance is pitiful if you don't liberally make use of libraries written in C. YMMV. >> I trying to be conservative with putting end parentheses on >> separate lines. One, doing this on too many constructs would >> add too many extra lines. Second, putting such parentheses >> in too many places would limit their value, they would be no >> longer good cue. Third, really small pieces of code are >> managable without extra cues, it is bigger pieces when it >> matters. Fourh, I want to limit dissatisfaction of Lispers >> used to traditional style in case they need to work on code >> that I write. >> >>> But the same question: if you wrote it in Python, would you leave an extra >>> little blank line for that weird closing paren? > > > >[ ... ] >> "no trailing white space". > >Hear hear!
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-07-09 23:08 +0000 |
| Subject | Re: Python blanks |
| Message-ID | <112p9ln$p5ou$5@dont-email.me> |
| In reply to | #61206 |
On Thu, 9 Jul 2026 14:01:49 -0000 (UTC), Waldek Hebisch wrote: > I am not a big fan of indented syntax, but for me it is in not a big > trouble. And when using indented syntax I feel less pressure to put > end markers on syntactic constructs (compared to Lisp or C). Part of > the reason is that in indented syntax indentation can not be > misleading ... It is the lack of redundancy that can be misleading, and that can occur either way. In traditional free-format languages, you have statement bracketing symbols to denote program structure. Human programmers usually arrange the code with indented layout as well, which the compiler is supposed to pay no attention to. But the two ways of saying the same thing help to make things clearer to a human reader. In an indentation-controlled language, there are no statement bracketing symbols. But again, it can be helpful to add comments to provide the bracketing hints, even if the compiler pays no attention them; the two ways of saying the same thing help to make things clearer to a human reader.
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2026-07-02 13:41 -0400 |
| Message-ID | <jwvv7axs33c.fsf-monnier+comp.lang.lisp@gnu.org> |
| In reply to | #61104 |
>>> Does it make a difference to the correctness of the code? >> Definitely, because it can change the algorithmic complexity in >> terms of space usage, so it can affect whether a programs runs in >> constant space or not, for example. > That’s not about correctness, that’s an efficiency issue. So that’s a > “no”, then. When your program runs out of memory that becomes a correctness issue. E.g. when `list-length` runs out of stack space when called on very long lists it's a correctness issue. === Stefan
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-07-03 05:45 +0000 |
| Message-ID | <1127i8t$3676o$1@dont-email.me> |
| In reply to | #61120 |
On Thu, 02 Jul 2026 13:41:43 -0400, Stefan Monnier wrote: > When your program runs out of memory that becomes a correctness > issue. So why doesn’t the language spec resolve the ambiguity, then? Because if you’re relying on the implementation working in a particular way, then that’s called “undefined behaviour” and the program must be considered buggy. I thought garbage collection was supposed to remove the headache of worrying about managing memory allocations. But it doesn’t, does it?
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2026-07-03 10:12 -0400 |
| Message-ID | <jwvechkupwq.fsf-monnier+comp.lang.lisp@gnu.org> |
| In reply to | #61129 |
Lawrence D’Oliveiro [2026-07-03 05:45:01] wrote: > On Thu, 02 Jul 2026 13:41:43 -0400, Stefan Monnier wrote: >> When your program runs out of memory that becomes a correctness >> issue. > So why doesn’t the language spec resolve the ambiguity, then? Probably for the same reason most language "specifications" don't deserve this name, they're just vague descriptions with lots of grey areas. Some languages are more precise and do provide usable guarantees w.r.t when a value is unreachable, but they're still a small minority. === Stefan
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2026-07-03 18:43 -0700 |
| Message-ID | <871pdjy1eu.fsf@nightsong.com> |
| In reply to | #61140 |
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> So why doesn’t the language spec resolve the ambiguity, then?
> Probably for the same reason most language "specifications" don't
> deserve this name
There's a viewpoint (denotative?) that an incorrect program is one that
generates wrong answers (like 2+2=5) and a correct program is one that
is not incorrect. So if the program hangs or crashes, it hasn't
generated any type of answer much less a wrong one, and therefore it is
correct. That type of program is called partial or divergent. A
never-diverging program is called "total" and being correct and total at
the same time is called "total correctness".
Total correctness sounds like something everyone should want, but
really, for most users, a program that might crash or generate a blue
screen is probably tolerable, as long as the probability of this event
is less than that of, say, a power failure at the office that similarly
crashes the user's computer. So proofs of program correctness in (say)
Rocq often won't care about algorithm complexity. Your program might
compute 2+2 using an valid but impractical algorithm that consumes
galactic-scale resources, and Rocq could certify it as correct. At
least it won't give the wrong answer! It will run out of memory
instead.
Ada/SPARK, on the other hand, not only seek to certify correctness, but
also totality ("this program cannot throw any exceptions, such as
integer overflow or out-of-memory"). I think those proofs are quite a
bit more cumbersome than Rocq proofs. So in practice (certainly in most
Lisp programs) we users mostly care only about correctness, not
totality.
I haven't used Rocq or SPARK in any serious way though.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-07-04 23:28 +0000 |
| Message-ID | <112c4ug$k25o$4@dont-email.me> |
| In reply to | #61143 |
On Fri, 03 Jul 2026 18:43:53 -0700, Paul Rubin wrote: > So if the program hangs or crashes, it hasn't generated any type of > answer much less a wrong one, and therefore it is correct. That type > of program is called partial or divergent. A never-diverging program > is called "total" and being correct and total at the same time is > called "total correctness". There is one easy, if one might say brutal, way of guaranteeing termination, at any rate: make the language primitive-recursive. Remember Blender, the example app I mentioned before? It uses node-graph-style languages for defining shaders (how the materials that objects are made of interact with light), compositor processing, and “geometry nodes” (actual programmatic generation of objects). These are all primitive-recursive.
[toc] | [prev] | [next] | [standalone]
Page 5 of 32 — ← Prev page 1 … 3 4 [5] 6 7 … 32 Next page →
Back to top | Article view | comp.lang.lisp
csiph-web