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-06-03 03:16 +0000 |
| Articles | 20 on this page of 183 — 20 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? 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? 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? 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? 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? 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? tfb <no_email@invalid.invalid> - 2026-06-18 09:32 +0000
Re: Resources to learn common lisp? antispam@fricas.org (Waldek Hebisch) - 2026-06-18 14:15 +0000
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? 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? tfb <no_email@invalid.invalid> - 2026-06-16 13:34 +0000
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? 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? Paul Rubin <no.email@nospam.invalid> - 2026-06-16 15:29 -0700
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? 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? 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
Page 2 of 10 — ← Prev page 1 [2] 3 4 … 10 Next page →
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-10 00:14 +0000 |
| Message-ID | <110aa8j$ckmk$7@dont-email.me> |
| In reply to | #60837 |
On Tue, 09 Jun 2026 12:07:43 +0200, Axel Reichert wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > >> What’s a homoiconic language with postfix operation syntax? > > https://factorcode.org/ > https://concatenative.org/wiki/view/Factor/Features/The%20language I see it needs to have an explicit “macro" construct to implement homoiconicity. This was unnecessary in PostScript. Here <https://gitlab.com/ldo/gxscript> is my attempt at a PostScript revival.
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-17 00:01 -0400 |
| Message-ID | <87fr2lq0hv.fsf@gmail.com> |
| In reply to | #60840 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > On Tue, 09 Jun 2026 12:07:43 +0200, Axel Reichert wrote: > >> Lawrence D’Oliveiro <ldo@nz.invalid> writes: >> >>> What’s a homoiconic language with postfix operation syntax? >> >> https://factorcode.org/ >> https://concatenative.org/wiki/view/Factor/Features/The%20language > > I see it needs to have an explicit “macro" construct to implement > homoiconicity. This was unnecessary in PostScript. > > Here <https://gitlab.com/ldo/gxscript> is my attempt at a PostScript > revival. most (u)nix programers use ghostscript. this should save you significant amount of timr. Also GV is awesome.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-17 05:53 +0000 |
| Message-ID | <110tcov$1l264$2@dont-email.me> |
| In reply to | #60939 |
On Wed, 17 Jun 2026 00:01:00 -0400, steve g wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > >> I see it needs to have an explicit “macro" construct to implement >> homoiconicity. This was unnecessary in PostScript. >> >> Here <https://gitlab.com/ldo/gxscript> is my attempt at a >> PostScript revival. > > most (u)nix programers use ghostscript. PostScript is so little used nowadays, even Adobe has deleted all the documentation from its website. The graphics model is obsolete. The language had some interesting features, but it needed more -- like proper local variables and lexical binding, which I added to my PostScript-alike language. If I wanted to generate high-quality 2D graphics and text with a quick scripting language nowadays, I would use the Cairo graphics library with Python, like here <https://www.deviantart.com/default-cube/gallery/53606552/qahirah-examples>.
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2026-06-17 09:06 +0100 |
| Subject | [OT] Disappearing documentation (was: Re: Resources to learn common lisp?) |
| Message-ID | <110tkit$1m43t$3@dont-email.me> |
| In reply to | #60944 |
On 2026-06-17, Lawrence D’Oliveiro wrote: > On Wed, 17 Jun 2026 00:01:00 -0400, steve g wrote: > >> Lawrence D’Oliveiro <ldo@nz.invalid> writes: >> >>> I see it needs to have an explicit “macro" construct to implement >>> homoiconicity. This was unnecessary in PostScript. >>> >>> Here <https://gitlab.com/ldo/gxscript> is my attempt at a >>> PostScript revival. >> >> most (u)nix programers use ghostscript. > > PostScript is so little used nowadays, even Adobe has deleted all the > documentation from its website. That is not the argument you think it is. There have been a lot of website revampings, perhaps pushed by Google's skewed search rankings, which promoted badly designed sites and content scrappers, perhaps pushed by adoption of JS frameworks that were deemed as requiring designing a new site from scratch. That has meant a lot of companies which used to have documentation, drivers, etc available now don't have but for a few select models. Along with the push to discontinue FTP support in browsers for some reason, which then was used to justify getting rid of such repositories here and there. This, if anything, is proof of companies being a bit asshole-y. Or perhaps indication that one should grab and archive *all the things*. (Also, what's this? <https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf>) -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-19 19:05 -0400 |
| Subject | Re: [OT] Disappearing documentation |
| Message-ID | <8733yijflk.fsf@gmail.com> |
| In reply to | #60946 |
Nuno Silva <nunojsilva@invalid.invalid> writes: > Along with the push to discontinue FTP support in browsers for some > reason, which then was used to justify getting rid of such repositories > here and there. yes, I also find this a bit disturbing. FTP is not that bad. Using webbrowser scripts is annoying. > This, if anything, is proof of companies being a bit asshole-y. Or > perhaps indication that one should grab and archive *all the things*. > > > (Also, what's this? > <https://www.adobe.com/jp/print/postscript/pdfs/PLRM.pdf>) postscript has changed ?
[toc] | [prev] | [next] | [standalone]
| From | steve g <Sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-19 19:01 -0400 |
| Message-ID | <877bnujfsa.fsf@gmail.com> |
| In reply to | #60944 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > On Wed, 17 Jun 2026 00:01:00 -0400, steve g wrote: > >> Lawrence D’Oliveiro <ldo@nz.invalid> writes: >> >>> I see it needs to have an explicit “macro" construct to implement >>> homoiconicity. This was unnecessary in PostScript. >>> >>> Here <https://gitlab.com/ldo/gxscript> is my attempt at a >>> PostScript revival. >> >> most (u)nix programers use ghostscript. > > PostScript is so little used nowadays, even Adobe has deleted all the > documentation from its website. sigh, I know. I still call pdf postscript version 3.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-20 00:02 +0000 |
| Message-ID | <1114lbd$3m8ht$1@dont-email.me> |
| In reply to | #60990 |
On Fri, 19 Jun 2026 19:01:41 -0400, steve g wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > >> PostScript is so little used nowadays, even Adobe has deleted all >> the documentation from its website. > > sigh, I know. I still call pdf postscript version 3. There is/was an actual PostScript language version (aka “language level”) 3. Following on from “PostScript Level 2”, it should have been called “PostScript Level 3”, but they used the name “PostScript 3” instead. I think somebody else might have had a trademark on “Level 3”, or something. One interesting difference between the language reference manuals between version/level 2 and 3 was the Display PostScript part in the former was dropped from the latter.
[toc] | [prev] | [next] | [standalone]
| From | tfb <no_email@invalid.invalid> |
|---|---|
| Date | 2026-06-11 17:22 +0000 |
| Message-ID | <110eqtf$1k9f5$1@dont-email.me> |
| In reply to | #60836 |
Lawrence D´Oliveiro <ldo@nz.invalid> wrote: > How about this for a definition: “homoiconicity with minimal syntax”. I think this is close. This would define what my friend Zyni would call a 'lispoid'. She is mostly a mathematician, and this is by analogy with terms like 'groupoid', which is something on the way to being a group. For almost all purposes a lispoid is enough: it is not a term meant to denigrate lispoids! In particular lispoids are enough to support seamless macros. I think Clojure is probably a lispoid by this definition. A lisp is then a lispoid where the underlying representation of source code is singly-linked lists. -- www.tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2026-06-13 13:59 -0700 |
| Message-ID | <87cxxu88cf.fsf@nightsong.com> |
| In reply to | #60836 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > How about this for a definition: “homoiconicity with minimal syntax”. Nah, it's more of a state of mind. At the center of it is lambda calculus, but even that only sometimes. Picolisp uses FEXPRs instead of macros and I remember hearing that those break lambda calculus in some way that I don't understand.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-14 00:55 +0000 |
| Message-ID | <110ku5g$3a32m$3@dont-email.me> |
| In reply to | #60877 |
On Sat, 13 Jun 2026 13:59:44 -0700, Paul Rubin wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: >> >> How about this for a definition: “homoiconicity with minimal >> syntax”. > > Nah, it's more of a state of mind. At the center of it is lambda > calculus, but even that only sometimes. λ-calculus is at the centre of *everything* in CompSci, like it or not. (Did you know that λ-calculus offers a way to reason about logical paradoxes, by representing them as endless loops? Mathematicians seem to be scared of paradoxes for some reason, but as you know in CompSci we deal with them all the time, it doesn’t drive us mad or anything.) > Picolisp uses FEXPRs instead of macros and I remember hearing that > those break lambda calculus in some way that I don't understand. I had a quick look at picolisp.com. I have this suspicion the language has no lexical binding -- maybe that’s the issue you’re thinking of? If so, I would consider that a bug, not a feature.
[toc] | [prev] | [next] | [standalone]
| From | Paul Rubin <no.email@nospam.invalid> |
|---|---|
| Date | 2026-06-14 01:43 -0700 |
| Message-ID | <87o6hd7br8.fsf@nightsong.com> |
| In reply to | #60880 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > λ-calculus is at the centre of *everything* in CompSci, like it or not. I'd say the correspondence between traditional imperative programs and lambda calculus is at best way more obscure than it is in Lisp. I'm not versed enough in PL theory to know if it appears at all. > (Did you know that λ-calculus offers a way to reason about logical > paradoxes, by representing them as endless loops? Not sure what you mean by that? >> Picolisp uses FEXPRs > I had a quick look at picolisp.com. I have this suspicion the language > has no lexical binding -- maybe that’s the issue you’re thinking of? No it's a completely separate issue. https://en.wikipedia.org/wiki/Fexpr describes some issues with FEXPRs. I guess the problem wasn't as serious as an inconsistency in the resulting lambda calculus, but more a matter of making FEXPR-using code difficult to compile. I've never used Picolisp but I've studied its documentation a little. It has some cute ideas but overall it didn't excite me very much.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-14 05:45 +0000 |
| Message-ID | <110lf56$3dqkh$5@dont-email.me> |
| In reply to | #60877 |
On Sat, 13 Jun 2026 13:59:44 -0700, Paul Rubin wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: >> >> How about this for a definition: “homoiconicity with minimal >> syntax”. > > Nah, it's more of a state of mind. At the center of it is lambda > calculus, but even that only sometimes. λ-calculus is at the centre of *everything* in CompSci, like it or not. (Did you know that λ-calculus offers a way to reason about logical paradoxes, by representing them as endless loops? Mathematicians seem to be scared of paradoxes for some reason, but as you know in CompSci we deal with their endless-loop equivalents all the time, it doesn’t drive us mad or anything.) > Picolisp uses FEXPRs instead of macros and I remember hearing that > those break lambda calculus in some way that I don't understand. I had a quick look at picolisp.com. I have this suspicion the language has no lexical binding -- maybe that’s the issue you’re thinking of? If so, I would consider that a bug, not a feature.
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-09 00:35 +0000 |
| Message-ID | <1107n4i$3k6ea$6@dont-email.me> |
| In reply to | #60820 |
On Mon, 08 Jun 2026 12:41:56 -0400, steve g wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > >> Lisp is a pretty interesting language, but it was never >> standardized to the extent that we expect of languages today. Look >> at the Common Lisp spec, and it still retains a lot of baggage to >> maintain compatibility with obsolete OSes that simply don’t matter >> any more. > >> And also, which particular Lisp do you want to learn? There are a >> number in common use today: > > this is false. common lisp is a programming language. In today’s terms, Common Lisp is only a partial language spec. It has all that historical baggage, and yet it leaves out crucial things that other languages, like Python, implement more uniformly today.
[toc] | [prev] | [next] | [standalone]
| From | steve g <sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-08 12:37 -0400 |
| Message-ID | <87pl21m1i6.fsf@gmail.com> |
| In reply to | #60748 |
Mario Rosell <mario@mariorosell.es> writes: < > Finally, what do you want learn it for? It might just be for fun or < > it might be because you have a very specific goal in mind for which < > someone might have some specific recommendations. actually lisp is best for researchers trying to test new alogrithims. Fun as much as programming is fun... > Just for fun. It seems like a pretty interesting language. hook, line, and sinker!
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-09 00:33 +0000 |
| Message-ID | <1107n17$3k6ea$5@dont-email.me> |
| In reply to | #60819 |
On Mon, 08 Jun 2026 12:37:53 -0400, steve g wrote: > actually lisp is best for researchers trying to test new [algorithms]. Lisp is purely garbage-collected though, isn’t it? Languages like Perl and Python try for a hybrid reference-counted/garbage-collected approach, for speed and also more deterministic memory usage in many common scenarios. I think you can use all three in Jupyter notebooks, anyway. That’s an environment I recommend for just about any kind of “scratchpad” or quick “experimentation” programming.
[toc] | [prev] | [next] | [standalone]
| From | steve g <sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-09 00:22 -0400 |
| Message-ID | <87tsrcxrz8.fsf@gmail.com> |
| In reply to | #60825 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > On Mon, 08 Jun 2026 12:37:53 -0400, steve g wrote: > < > actually lisp is best for researchers trying to test new [algorithms]. > Lisp is purely garbage-collected though, isn’t it? Languages like Perl > and Python try for a hybrid reference-counted/garbage-collected > approach, for speed and also more deterministic memory usage in many > common scenarios. i will not deny my love of this languagw. yes liSP uses GC. A hybride approad? like unboxed numbers?
[toc] | [prev] | [next] | [standalone]
| From | Alan Bawden <alan@csail.mit.edu> |
|---|---|
| Date | 2026-06-09 01:22 -0400 |
| Message-ID | <865x3sthhu.fsf@williamsburg.bawden.org> |
| In reply to | #60825 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > Lisp is purely garbage-collected though, isn’t it? Languages like Perl > and Python try for a hybrid reference-counted/garbage-collected > approach, for speed and also more deterministic memory usage in many > common scenarios. I don't think any of Common Lisp, Java, Perl or Python promise to employ any particular algorithm for collecting garbage. It's not something you really need to put in your language specification document. All you need to say is that storage management is not something the programmer needs to worry about. Nothing prevents you from implementing a Common Lisp that does reference counting. It seems to be fashionable these days to consider reference counting to be somehow different from garbage collection, but historically reference counting was just another tool used for garbage collection. At least one of the InterLisp implementations used reference counting as part of its garbage collector, and nobody thought that it had less of a true garbage collector as a result. -- Alan Bawden
[toc] | [prev] | [next] | [standalone]
| From | tfb <no_email@invalid.invalid> |
|---|---|
| Date | 2026-06-09 06:17 +0000 |
| Message-ID | <1108b4u$3p13j$1@dont-email.me> |
| In reply to | #60830 |
Alan Bawden <alan@csail.mit.edu> wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > > At least > one of the InterLisp implementations used reference counting as part of > its garbage collector, and nobody thought that it had less of a true > garbage collector as a result. > Those of us who had to write code to laboriously decircularize about-to-be-dead structures on d machines definitely did! But your point is right: these are implementation, not language, questions. (I also hate the stupid 'reference counting is better' thing. It is 2000 already, machines live or die on their caches. I drop a large structure on the floor. A reference-counted implementation now dutifully walks over the entire structure reducing all the counts to zero *and ensuring the machine's caches are full of data that will never be used again*. An implementation with a copying GC ... never touches that memory again. One of these approaches is a lot less hostile to caches than the other.) -- www.tfeb.org/computer/
[toc] | [prev] | [next] | [standalone]
| From | Lawrence D’Oliveiro <ldo@nz.invalid> |
|---|---|
| Date | 2026-06-09 06:50 +0000 |
| Message-ID | <1108d3q$3p7sr$2@dont-email.me> |
| In reply to | #60830 |
On Tue, 09 Jun 2026 01:22:53 -0400, Alan Bawden wrote: > Lawrence D’Oliveiro <ldo@nz.invalid> writes: > >> Lisp is purely garbage-collected though, isn’t it? Languages like >> Perl and Python try for a hybrid >> reference-counted/garbage-collected approach, for speed and also >> more deterministic memory usage in many common scenarios. > > I don't think any of Common Lisp, Java, Perl or Python promise to > employ any particular algorithm for collecting garbage. It's not > something you really need to put in your language specification > document. It does have some subtle, but far-reaching, implications for language usage, though. For example, pure GC makes it easy to support multithreading. But the downside is that it is easy for a single long-running program to consume all available memory, even if its memory needs at any particular moment are not that great. So you need to put arbitrary constraints on its heap size. And if turns it that wasn’t enough for a particular run, then you need to stop and re-run with a larger heap allocation. Which defeats some of the point of dynamic memory allocation when you have to micromanage such things, doesn’t it? This is why both Perl and Python stuck with the hybrid approach. In Perl’s case, they kind of fudged their approach to multithreading as a consequence, with implications for sharing objects across threads. While the Python folks have put a lot of effort into coming up with a more comprehensive solution, making reference counts just a little bit nondeterministic in return for greater performance while still allowing object sharing to work the way you would expect.
[toc] | [prev] | [next] | [standalone]
| From | steve g <sgonedes1977@gmail.com> |
|---|---|
| Date | 2026-06-10 12:40 -0400 |
| Message-ID | <875x3q2vsf.fsf@gmail.com> |
| In reply to | #60835 |
Lawrence D’Oliveiro <ldo@nz.invalid> writes: > On Tue, 09 Jun 2026 01:22:53 -0400, Alan Bawden wrote: > < > Lawrence D’Oliveiro <ldo@nz.invalid> writes: < > < >> Lisp is purely garbage-collected though, isn’t it? Languages like < >> Perl and Python try for a hybrid < >> reference-counted/garbage-collected approach, for speed and also < >> more deterministic memory usage in many common scenarios. < > < > I don't think any of Common Lisp, Java, Perl or Python promise to < > employ any particular algorithm for collecting garbage. It's not < > something you really need to put in your language specification < > document. > > It does have some subtle, but far-reaching, implications for language > usage, though. > > For example, pure GC makes it easy to support multithreading. !!? Ummm ??! But the > downside is that it is easy for a single long-running program to > consume all available memory, even if its memory needs at any > particular moment are not that great. So you need to put arbitrary > constraints on its heap size. > And if turns it that wasn’t enough for a > particular run, then you need to stop and re-run with a larger heap > allocation. Which defeats some of the point of dynamic memory > allocation when you have to micromanage such things, doesn’t it? > This is why both Perl and Python stuck with the hybrid approach. In > Perl’s case, they kind of fudged their approach to multithreading as a > consequence, with implications for sharing objects across threads. with all due respect, garbage collection is very difficult. Most programmers will use the best algorithm available; like guile does. PERL is the fastest interpreter I have ever used, compiling the code to C results in slower running speed. There is an issue with heap... > While the Python folks have put a lot of effort [...] there is no perfect solution; python can be compiled with LTO, I don't have the numbers on me... from what I understand this is a new method.
[toc] | [prev] | [next] | [standalone]
Page 2 of 10 — ← Prev page 1 [2] 3 4 … 10 Next page →
Back to top | Article view | comp.lang.lisp
csiph-web