• Re: Resources to learn common lisp?

    From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Jul 29 23:48:46 2026
    From Newsgroup: comp.lang.lisp

    On 10 Jul 2026 10:17:33 GMT, Stefan Ram wrote:

    |Which one gets invoked ("dispatch") is decided at run-time,
    |in contrast to many other languages with "overloading".
    "An Introduction to the Common Lisp Object System"
    - Gregor Kiczales, Jim des Rivi|?res, and Daniel G. Bobrow?

    Maybe that doesnrCOt mean what you think it means. Remember, theyrCOre
    using rCLdispatchrCY specifically for a language without infix operators. Smalltalk was doing dynamic operator overloading before Common Lisp
    was even thought of.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Jul 29 23:50:47 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 29 Jul 2026 16:26:56 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    If garbage collection is so good, why donrCOt OS kernels use it?

    You are probably using a shitty OS.

    So where is there a rCLnon-shitty OSrCY that uses garbage collection in
    its kernel? Does the one *you* use have garbage collection in its
    kernel?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Jul 29 23:52:45 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 29 Jul 2026 16:31:22 -0400, steve g wrote:

    postscript is a complicated language in my mind, especially when
    compared to C.

    PostScript is a language that can make Lisp look complicated. It
    offers homoiconicity, like Lisp does, but with less syntax: so much
    less that it doesnrCOt even need macros or rCLspecial formsrCY, or much of a compile-time mechanism at all.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Jul 29 23:53:51 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 29 Jul 2026 16:08:10 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 29 Jun 2026 07:33:05 -0000 (UTC), tfb wrote:

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    If a GC is not finding long-dead objects to reclaim, then what
    exactly is it doing? IsnrCOt that exactly what the rCLgarbagerCY is,
    that it is supposed to rCLcollectrCY?

    Like I said: you do not understand, at all, how a copying GC works.

    ThatrCOs what we call a rCLpassive-aggressiverCY response: trying to
    imply IrCOm wrong, but not specifically enough so that I can call you
    up on it.

    Where did you study psychology; I mean social worker class.

    Specific substantive response still lacking.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Fri Jul 31 07:17:43 2026
    From Newsgroup: comp.lang.lisp

    On 30/07/2026 4:21 AM, steve g wrote:
    tfb <tfb@work.it.out> writes:

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    Have they come up with any excuses as to why OS kernels donrCOt use
    garbage collection?

    I think you are mistaken about OS kernels. They do garbage collection.
    Just not in the way you think about it. It's for instance how killing processes in Linux "cleans up" memory. I disagree with this design
    choice, and do not use Linux when I can avoid it.



    Here is why: they're written either in C or in languages which must be
    memory & call compatible with C. It is essentially impossible to implement >> a garbage collector in C. There is a famous counterexample: the Boehm GC. >> It would probably be possible to use that in an OS kernel written in C but >> I expect it would be very hard to retrofit it to an existing kernel. It's >> also (because C) not a copying collector.


    Introduction to GC:

    The GC package contains the Boehm-Demers-Weiser conservative garbage collector, which can be used as a garbage collecting replacement for the
    C malloc function or C++ new operator. It allows you to allocate memory basically as you normally would, without explicitly deallocating memory
    that is no longer useful. The collector automatically recycles memory
    when it determines that it can no longer be otherwise accessed. The
    collector is also used by a number of programming language
    implementations that either use C as intermediate code, want to
    facilitate easier interoperation with C libraries, or just prefer the
    simple collector interface. Alternatively, the garbage collector may be
    used as a leak detector for C or C++ programs, though that is not its
    primary goal.

    this is what guile uses and GCC can use.

    And I guess you're ignorant of the Ravenbrook /Memory Pool System/, or
    you'd have mentioned it already.

    https://github.com/Ravenbrook/mps

    I have it on stand by for a future project. I'll see if it's easier to
    use that, than to write my own. Cross posted to comp.lang.c to irritate
    the annoying regulars there.


    C was a deeply appropriate language to write an OS for the PDP-11. At
    every point since then there's been the choice of continuing to use C and
    either a port of that OS or an implementation of a compatible OS or of
    implementing a new, incompatible, OS. For at least 30 years there's really >> only been one answer to that question. And so, today, by a series of
    perfectly reasonable choices, we've ended up with a vast OS implemented in >> a language which is now deeply inappropriate.

    let me guess assembler is not your programming language of choice.
    henceforth C.

    I do a bit of assembly now and then. Which one is your favorite?


    Sadly we've also ended up with programmers who think the machines they
    program for are giant PDP-11s, and as a result machines which spend a huge >> amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Jul 30 21:05:43 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 29 Jul 2026 16:15:25 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:

    tfb <tfb@work.it.out> writes:

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    Have they come up with any excuses as to why OS kernels donrCOt use
    garbage collection?

    Here is why: they're written either in C or in languages which must be
    memory & call compatible with C. It is essentially impossible to implement >> a garbage collector in C.

    Of course you meant "for C." Many collectors are/were written "in C."

    ... There is a famous counterexample: the Boehm GC.
    It would probably be possible to use that in an OS kernel written in C but >> I expect it would be very hard to retrofit it to an existing kernel. It's >> also (because C) not a copying collector.

    Bartlett, Detlefs, and Yip all have created /copying/ (ie. moving)
    collectors for C++.
    [Sorry don't have URLs handy - my sources are dead trees.]


    C++ new() specifies the type of object to be allocated whereas C
    malloc() specifies only a size in bytes. A collector based upon new()
    can have perfect knowledge of objects in the heap [and their layouts].

    The details differ, but basically they can move heap objects pointed
    to only by globals or other heap objects, but can't move objects that
    appear to be pointed to by registers, correctly aligned stack resident
    datums, or by union members. Such objects are considered to be
    "pinned" in place for the current GC cycle - perhaps in the next cycle
    they will be movable again.

    So the collector's "new" space is logical and includes pinned objects
    as well ones that have been relocated.


    ----
    BTW: Detlefs and Ellis submitted a standard's proposal for GC to be
    officially supported by C++. The proposal is not for any particular
    collector, but rather calls for changes to code generators that would
    make a collector's job easier.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Jul 30 21:37:16 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 29 Jul 2026 23:48:46 -0000 (UTC), Lawrence D-|Oliveiro
    <ldo@nz.invalid> wrote:

    On 10 Jul 2026 10:17:33 GMT, Stefan Ram wrote:

    |Which one gets invoked ("dispatch") is decided at run-time,
    |in contrast to many other languages with "overloading".
    "An Introduction to the Common Lisp Object System"
    - Gregor Kiczales, Jim des Rivi|?res, and Daniel G. Bobrow?

    Maybe that doesnrCOt mean what you think it means. Remember, theyrCOre
    using rCLdispatchrCY specifically for a language without infix operators. >Smalltalk was doing dynamic operator overloading before Common Lisp
    was even thought of.

    Maybe you missed the word "many" in the quote.

    You are quite correct that Smalltalk preceded and even somewhat
    influenced Common Lisp ... but your comparison of them is not valid.

    Smalltalk methods dispatch on the runtime type of the object, but the
    types of the arguments are not considered. If an argument is used
    incorrectly you get an error. If a given method wants to handle an
    argument that may be any of multiple types, it has to manually test
    for them.

    Common Lisp multimethods (aka generic functions) are not attached to
    any object and dispatch considers the runtime types of all arguments.
    You handle different types of arguments by writing different overload
    functions - which do not have to test argument types because dispatch
    has already done it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Jul 31 08:01:26 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:

    Of course you meant "for C." Many collectors are/were written "in C."

    Yes, and specifically 'for large existing C programs which you are not
    willing to completely reengineer'. At any point since it started running
    on machines where a GC would be a practical proposition[*], the Unix kernel
    was such a program.

    There is more, I think: the Sapir-Whorf hypothesis is at least partly true
    for programming languages: the language determines what its programmers can (easily) think. You obviously could write GC-friendly C programs, but C programmers exposed to large existing C programs probably would find them
    so alien they probably wouldn't actually write them. You really need a new language (which, in turn, would influence how people think, but in
    different ways).

    And let's leave out compatibility questions: 'you mean to port my device
    driver I have to ...?'

    All of this means that, once you've got large C programs and a culture
    around them you can't just drop in GC.

    [*] Yes, I do not claim GC is suitable for all machines. I've written
    programs for the 1802.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.c on Fri Jul 31 12:21:51 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which
    spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent
    fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Sat Aug 1 01:48:56 2026
    From Newsgroup: comp.lang.lisp

    On 31/07/2026 11:21 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which
    spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent
    fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.

    The fun is in writing atypical applications, and then finding yourself
    looking at the disassembly in SBCL.

    Personally, I love writing in C, even though it's more verbose.

    That said, and to be mildly on-topic in comp.lang.lisp, have

    * /The Common Lisp Condition System/, and

    * /Programming Algorithms in Lisp/

    been mentioned before as resources for learning common lisp?

    These two books look lovely in my programming shelf, next to

    * /Common Lisp Recipes/, and

    * /Practical Common Lisp/,

    which must have been mentioned. They're interspersed with

    * /Low Level Programming/,

    * /String Algorithms in C/, and

    * /The Joys of Hashing/,

    which come in handy when you want to implement your own Common
    Lisp system.


    Enjoy!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp,comp.lang.c,comp.lang.python on Fri Jul 31 22:46:45 2026
    From Newsgroup: comp.lang.lisp

    On Fri, 31 Jul 2026 12:21:51 -0300, Anton Antimo wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct.

    What a dumb idea. Common Lisp is full of legacy baggage to cater to
    proprietary pre-POSIX OSes which are now extinct.

    Python can offer basic facilities like these in its standard library: <https://docs.python.org/3/library/subprocess.html> <https://docs.python.org/3/library/select.html>; where are the Common
    Lisp equivalents?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c,comp.lang.asm on Sat Aug 1 07:38:32 2026
    From Newsgroup: comp.lang.lisp

    On 01/08/2026 6:46 AM, Lawrence DrCOOliveiro wrote:
    On Fri, 31 Jul 2026 12:21:51 -0300, Anton Antimo wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct.

    What a dumb idea. Common Lisp is full of legacy baggage to cater to proprietary pre-POSIX OSes which are now extinct.

    As always, you start off by mouthing your own ignorance.

    * OpenVMS is both sold and ported to the x86. https://vmssoftware.com/

    * OS/2 is being sold and supported, under a new brand name.
    https://www.arcanoae.com/

    * MenuetOS is written in assembly language, so I replaced
    comp.lang.python with comp.lang.asm. https://www.menuetos.net/


    Python can offer basic facilities like these in its standard library: <https://docs.python.org/3/library/subprocess.html> <https://docs.python.org/3/library/select.html>; where are the Common
    Lisp equivalents?

    You mean this? https://www.sbcl.org/manual/#running-external-programs
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Fri Jul 31 23:52:27 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:26:56 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    If garbage collection is so good, why donrCOt OS kernels use it?

    You are probably using a shitty OS.

    So where is there a rCLnon-shitty OSrCY that uses garbage collection in
    its kernel? Does the one *you* use have garbage collection in its
    kernel?

    It depends on how the kernel is compiled. be it BSD or linux; I can no
    longer compile windows without a credit card. So the options are shit...
    OS/2? I liked PC-DOS.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c on Fri Jul 31 23:59:43 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which
    spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent
    fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.


    Wait until you read LISP:Lisp In Small Pieces. it's published in france.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 1 05:24:05 2026
    From Newsgroup: comp.lang.lisp

    On Fri, 31 Jul 2026 23:52:27 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:26:56 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    If garbage collection is so good, why donrCOt OS kernels use it?

    You are probably using a shitty OS.

    So where is there a rCLnon-shitty OSrCY that uses garbage collection in
    its kernel? Does the one *you* use have garbage collection in its
    kernel?

    It depends on how the kernel is compiled.

    What a load of nonsense. There is no OS kernel you have access to,
    that uses garbage collection for internal memory management. Just
    admit it instead of trying to bullshit.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Sat Aug 1 16:12:36 2026
    From Newsgroup: comp.lang.lisp

    On 01/08/2026 11:59 AM, steve g wrote:
    Anton Antimo <anton@safunu.org> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which
    spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent
    fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.


    Wait until you read LISP:Lisp In Small Pieces. it's published in france.




    I read the French edition. /Principes d'Implantation de Scheme et
    Lisp/, and it's now available as ebook on Amazon. I recommend it,
    it's a really fun book. I believe it's the /second edition/, and
    may have a little bit different content than the English one, which
    I haven't read.

    Do you read French?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.c,comp.lang.python on Sat Aug 1 09:08:16 2026
    From Newsgroup: comp.lang.lisp

    It is 2042. A dry wind blows over a desolate landscape, raising flurries
    of dust from the burnt ground. Feral dogs, tumours proliferating on their skin, pick through the debris, raking through yellow bones in the hope of
    rats. In the distance the remains of a city, a city whose name will soon
    be remembered by nobody. Some of the buildings appear curiously melted.

    A structure made of corrugated iron, rusting, deformed panels torn from
    some vehicle, and papier m|och|-. A turbine atop a tower made partly of
    garden furniture, creaking in the wind. A collection of car batteries.

    In the shed a thin figure crouches: ragged clothes and open sores. He
    types at a keyboard, poking a stick into the switches of the missing keys.
    The screen is cracked and dim.

    The camera's eye moves, we can see, barely, the text on the screen.

    PYTHON IS THE ONLY TRUE SOLUTION PYTHON HAS BEEN THE BEST THE ONLY
    LANGUAGE FOR CENTURIES REFERENCE COUNTING WILL NOT CORRUPT YOUR PRECIOUS BODILY FLUIDS GARBAGE COLLECTION IS THE WORK OF SATAN PYTHON IS THE
    STANDARD REFERENCE COUNTING MAKES THE BIRDS SING AND THE GRASS GREEN
    GARBAGE COLLECTORS ARE CONTINUALLY TRAWLING THROUGH DEAD DATA LISP IS OBSOLETE EVIL NOBODY USES LISP USE PYTHON LIKE ME USE PYTHON REFERENCE
    PYTHON LISP SLOW FAST PYTHON BEST YES PYTHON GARBAGE BAD PYTHON OBSOLETE

    Flecks of foam and blood land on the keyboard. No birds sing; what once
    was grass is now dust and ash.

    Still he types, faster and faster now, singing and chanting.

    From the computer in the shack a cable runs. The camera follows it, to its end: copper cores poking through charred insulation.

    Fade.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to comp.lang.lisp,comp.lang.c,comp.lang.python on Sat Aug 1 07:49:41 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 8/1/2026 5:08 AM, tfb wrote:
    It is 2042.

    Fade.

    The land may be parched, but the surface is populated
    by shiny machines filled with the pretense of AI inside.

    When I asked an LLM-AI to draw me a picture of something,
    it said "here is your Python Card, execute this and your
    picture will appear". As usual, some cosmetic changes were
    required to the Card, but the code did run and meet the objective.
    I do not recollect asking for a Python Card, I asked
    for a picture. As an ordinary end-user, I was expected to know
    what Python was ("the one true language") :-) The LLM-AI
    didn't even say "Do you know what Python is ?" . It just
    said "here is your Python Card", like everyone knows what
    that is.

    You see, the LLM-AI had decided what the chosen language is,
    and it happens to be Python :-) Insert cackling laughter.

    *******

    I just asked it explicitly now, and it really IS hilarious.

    "If you are given a programming task to do, and the
    programming language is not specified, what language
    do you choose for the task and why do you choose
    that particular language ?
    "

    CoPilot Answer:

    If the task doesnrCOt specify a programming language, the smartest choice
    is the language that gives you the fastest, clearest, least-painful path
    to a correct solution. For most general, unspecified tasks, that tends
    to be Python - and hererCOs why.

    Efoa Short answer

    I choose Python, because it minimizes friction: fast to write, easy to read, huge standard library, and excellent for everything from quick scripts to complex algorithms.
    ...

    So there you have it, it wasn't an "accident" after all.
    It really does mean it, when it hands out Python Cards
    like they were candy. Yikes! Looks like the language
    wars are over.

    My resume in the year 2042:

    Languages: Python
    (And when I have to, English)

    *******

    Well, that was only a leg-pull. Here is another paragraph of that slop,
    to provide some balance.

    Efoa When I wouldnrCOt choose Python
    If the task hints at certain domains, I pivot:

    HighrCaperformance numeric computing raA C++ or Rust

    Systems programming / OSrCalevel tasks raA C or Rust

    Web frontrCaend raA JavaScript/TypeScript

    Enterprise backend raA Java or C#

    Embedded / microcontrollers raA C

    Functional programming or concurrency-heavy tasks raA Haskell, Elixir, or Rust

    But if the prompt gives no domain clues, Python is the most rational starting point.

    *******

    You Rust programmers, your job is safe for now.

    And Rust never sleeps.

    Paul
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp,comp.lang.c,comp.lang.python on Sat Aug 1 23:37:28 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 1 Aug 2026 07:49:41 -0400, Paul wrote:

    Well, that was only a leg-pull. Here is another paragraph of that
    slop, to provide some balance.

    Enterprise backend raA Java or C#

    This <https://www.infoworld.com/article/4091447/spring-ai-tutorial-get-started-with-spring-ai.html>
    is supposed to be an example of how you do AI programming in Java.

    Is anybody still mystified why normal people would rather use Python
    instead?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp,comp.lang.c,comp.lang.python on Sat Aug 1 16:54:12 2026
    From Newsgroup: comp.lang.lisp

    On 8/1/2026 4:37 PM, Lawrence DrCOOliveiro wrote:
    On Sat, 1 Aug 2026 07:49:41 -0400, Paul wrote:

    Well, that was only a leg-pull. Here is another paragraph of that
    slop, to provide some balance.

    Enterprise backend raA Java or C#

    This <https://www.infoworld.com/article/4091447/spring-ai-tutorial-get-started-with-spring-ai.html>
    is supposed to be an example of how you do AI programming in Java.

    Is anybody still mystified why normal people would rather use Python
    instead?

    Yeah. I see normal people that use python all the time in the store...
    Give me a break!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.c,comp.lang.python on Sun Aug 2 07:39:42 2026
    From Newsgroup: comp.lang.lisp

    Paul <nospam@needed.invalid> wrote:
    [... Python, Rust ...]

    Woosh.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kotorifan@mindyourownbiz@noemail.fuck to comp.lang.lisp on Sun Aug 2 16:42:37 2026
    From Newsgroup: comp.lang.lisp

    Am Fri, 20 Feb 2026 22:53:00 +0100 schrieb Mario Rosell:

    Hello everyone!

    I want to learn Common Lisp, but I don't really know what resources to
    use.

    What did you all use to learn? Is that even relevant? Is this newsgroup active?

    Thanks for everyone in advice

    For learning the basics about the language I highly recommend the book "Practical Common Lisp" by Peter Seibel. It is available for free over
    here: https://gigamonkeys.com/book/ and explains the basic concepts like macros, loops, CLOS, and so on in detail. From all resources I know, this
    has been the most helpful in learning CL. Other than that you should check
    out the Hyperspec when stuck, it's essentially something akin to man
    pages, but for CL, and documents the language well. It is not really a
    good beginner resource, however, for that rather read the book.

    Also it does help to have a background in Emacs Lisp, which you will need anyway when dealing with SLIME/Sly, Emacs, and CL, so it's a good idea to
    get acquainted with Elisp in parallel, even if your knowledge is only very rudimentary, it still helps.

    -- kotorifan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sun Aug 2 22:53:23 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 02 Aug 2026 16:42:37 +0000, kotorifan wrote:

    For learning the basics about the language I highly recommend the
    book "Practical Common Lisp" by Peter Seibel.

    Common Lisp is a museum-worthy spec by this point. There needs to be
    something more modern, not so full of legacy baggage tied to old,
    proprietary, pre-POSIX OS platforms which are all extinct by now.

    Also it does help to have a background in Emacs Lisp ...

    Emacs Lisp contains some useful functionality beyond that specified by
    Common Lisp, but it still isnrCOt really enough for a general-purpose programming language. Not in this day and age.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Sun Aug 2 16:56:20 2026
    From Newsgroup: comp.lang.lisp

    kotorifan <mindyourownbiz@noemail.fuck> writes:
    For learning the basics about the language I highly recommend the book "Practical Common Lisp" by Peter Seibel.... Also it does help to have
    a background in Emacs Lisp

    It might be enough to start with an understanding of Scheme from SICP (Structure and Interpretation of Computer Programs). My own "road to
    Lisp" basically was studying the Emacs source code and grokking Emacs
    Lisp that way, followed by using CLTL1 to see that CL was a
    generalization of the same ideas.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Tue Aug 4 00:49:45 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 5 Jul 2026 01:49:41 -0000 (UTC), I wrote:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    Python's inventors insist that it's not a Lisp, but we Lispers can
    see that it's just a weird Lisp implementation with some surface
    syntax added.

    Lisp doesnrCOt have operator overloading.

    Also: Python doesnrCOt need the whole multiple-value-return
    Heath-Robinsonesque mechanism. It has something simpler: destructuring assignment.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Tue Aug 4 09:56:23 2026
    From Newsgroup: comp.lang.lisp

    On 04/08/2026 8:49 AM, Lawrence DrCOOliveiro wrote:
    On Sun, 5 Jul 2026 01:49:41 -0000 (UTC), I wrote:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    Python's inventors insist that it's not a Lisp, but we Lispers can
    see that it's just a weird Lisp implementation with some surface
    syntax added.

    Lisp doesnrCOt have operator overloading.

    Also: Python doesnrCOt need the whole multiple-value-return Heath-Robinsonesque mechanism. It has something simpler: destructuring assignment.

    Again, you're wallowing in error and dizziness. What do you call this?

    (destructuring-bind (a b c) (list 1 2 3)
    (print a) (print b) (print c))

    You just return a list, and destructure it on the receiving end.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?Niocl=C3=A1is=C3=ADn_C=C3=B3il=C3=ADn_Glost=C3=A9ir?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 4 18:35:36 2026
    From Newsgroup: comp.lang.lisp

    |------------------------------------------------------------------------------|
    |" Ar an c||igi|| l|i de m|! I||il, scr|!obh Lawrence DrCOOliveiro: |
    | |
    | > On Sun, 05 Jul 2026 22:14:32 +0100, Aidan Kehoe wrote: |
    | > |
    | > > Ar an nao|| l|i is fiche de m|! Meitheamh, scr|!obh tfb: |
    | > > |
    | > >> steve g <Sgonedes1977@gmail.com> wrote: |
    | > >>> |
    | > >>> Does any program actually free or return memory to the kernel |
    | > >>> before it exits? |
    | > >>> |
    | > >> Absolutely. LispWorks even has a function to do just this. |
    | > > |
    | > > Why, with a modern OS? For the sake of leak-tracking? |
    | > |
    | > rCLModernrCY OSes support multitasking. That means there are going to be |
    | > other processes running and doing useful things in their way, not just |
    | > yours. |
    | > |
    | > Giving up memory yourCOre not using is just part of acting like a |
    | > well-behaved resident of the userland ecosystem. Because, at least on |
    | > Linux, being too much of a memory hog is liable to awaken the Dreaded |
    | > OOM Killer. |
    | > |
    | > And you do not want that. |
    | |
    |I broadly agree with that; my question above was from a misinterpretation of: |
    | |
    | > >>> Does any program actually free or return memory to the kernel |
    | > >>> before it exits? |
    | > >>> |
    | > >> Absolutely. LispWorks even has a function to do just this. |
    | |
    |I took the question to mean rCLright before it exits,rCY which would be a waste of|
    |time." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in mac Eochadha.

    N|! c||is n|iire sin!

    Is mise le meas,
    Niocl|is|in Caile|in Glost|-ir
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Wed Aug 5 05:46:17 2026
    From Newsgroup: comp.lang.lisp

    On 05/08/2026 2:35 AM, Niocl|iis|!n C||il|!n Glost|-ir wrote:
    |------------------------------------------------------------------------------|
    |" Ar an c||igi|| l|i de m|! I||il, scr|!obh Lawrence DrCOOliveiro: |
    | |
    | > On Sun, 05 Jul 2026 22:14:32 +0100, Aidan Kehoe wrote: |
    | > |
    | > > Ar an nao|| l|i is fiche de m|! Meitheamh, scr|!obh tfb: |
    | > > |
    | > >> steve g <Sgonedes1977@gmail.com> wrote: |
    | > >>> |
    | > >>> Does any program actually free or return memory to the kernel |
    | > >>> before it exits? |
    | > >>> |
    | > >> Absolutely. LispWorks even has a function to do just this. |
    | > > |
    | > > Why, with a modern OS? For the sake of leak-tracking? |
    | > |
    | > rCLModernrCY OSes support multitasking. That means there are going to be |
    | > other processes running and doing useful things in their way, not just |
    | > yours. |
    | > |
    | > Giving up memory yourCOre not using is just part of acting like a |
    | > well-behaved resident of the userland ecosystem. Because, at least on |
    | > Linux, being too much of a memory hog is liable to awaken the Dreaded |
    | > OOM Killer. |
    | > |
    | > And you do not want that. |
    | |
    |I broadly agree with that; my question above was from a misinterpretation of: |
    | |
    | > >>> Does any program actually free or return memory to the kernel |
    | > >>> before it exits? |
    | > >>> |
    | > >> Absolutely. LispWorks even has a function to do just this. |
    | |
    |I took the question to mean rCLright before it exits,rCY which would be a waste of|
    |time." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in mac Eochadha.

    N|! c||is n|iire sin!

    Is mise le meas,
    Niocl|is|in Caile|in Glost|-ir
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    To do that, you use mmap() and its ilk to allocate the memory. Then you
    can munmap() that to return this bunch of memory to the operating
    system.

    This is for instance not a bad idea to allocate memory for text editor
    buffers, because if you decide to "edit" a 16GB log file, you don't need
    to keep those 16GB unused address space allocated to the application
    once you close the buffer.

    You can make use of the regular heap for the rest of the editor runtime,
    with or without a Common Lisp system.

    That said, while this is technically possible, rather few applications
    do this, and I have not bothered to look up ready made interfaces in
    SBCL for this as I write this post. If missing, it's /trivial/ for
    some value of trivial, to just add it to SBCL.


    Best wishes, and happy munmap()ping!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Tue Aug 4 22:08:42 2026
    From Newsgroup: comp.lang.lisp

    On Fri, 31 Jul 2026 08:01:26 -0000 (UTC), tfb <tfb@work.it.out> wrote:

    George Neuner <gneuner2@comcast.net> wrote:

    Of course you meant "for C." Many collectors are/were written "in C."

    Yes, and specifically 'for large existing C programs which you are not >willing to completely reengineer'. At any point since it started running
    on machines where a GC would be a practical proposition[*], the Unix kernel >was such a program.

    There is more, I think: the Sapir-Whorf hypothesis is at least partly true >for programming languages: the language determines what its programmers can >(easily) think. You obviously could write GC-friendly C programs, but C >programmers exposed to large existing C programs probably would find them
    so alien they probably wouldn't actually write them. You really need a new >language (which, in turn, would influence how people think, but in
    different ways).

    Yes and no. It actually is difficult to write GC-friendly programs in
    C - there are all kinds of constraints you have to obey. See below.


    And let's leave out compatibility questions: 'you mean to port my device >driver I have to ...?'

    All of this means that, once you've got large C programs and a culture
    around them you can't just drop in GC.

    [*] Yes, I do not claim GC is suitable for all machines. I've written >programs for the 1802.


    I'm sure *you* (tfb) know this, but for those who don't:



    C pointers are not positively identifiable at runtime, so GC has to be "conservative" - only /potential/ pointers can be identified, and the
    objects they point to, in general, can't be moved without corrupting
    program data. You don't need to worry about objects on the stack -
    only objects on the heap.

    In C the situation is complicated even beyond simply not being able to
    find pointers because the standard explicitly permits idioms and code optimizations that can obscure what pointers are there.


    The standard permits a pointer into the interior of an object to be
    the /only/ pointer to that object. So, e.g., the only pointer
    referencing a structure might be not point to the structure itself but
    instead to one of its data members. Similarly for an array, the only
    pointer might point at some random element rather than the start of
    the array.

    For arrays it even is worse because the only pointer might in fact
    point to the non-existent element one index past the array's end.


    At the source level in C, you might think that you could just ensure
    there always is a pointer to the base of each object, or the start of
    each data structure. However, the compiler is permitted to elide
    pointers [and indexing] it determines are superfluous.

    E.g., in the following fragment

    :
    int *a = (int*) malloc( 32 * sizeof(int) );

    int *p = a;
    for ( int i = 0; i < 32; ++i )
    p[i] = ...
    :

    you might think 'a' always points to the base of the array ... but in
    fact the compiler is permitted to completely ignore 'p', or if 'a' is
    not used again, the compiler can forget about 'a' after the assignment
    to 'p'. Similarly it can turn the indexing into simple counting, and
    simply walk one of the pointers over the array.

    Consider where the pointer might be if GC occurs when 'i' is not zero.
    If the compiler used 'a' to walk over the array, did it reset 'a' to
    point to the base of the array following the loop? Lacking another use
    of a[] or call to free(a), it isn't required to.


    And, of course, C allows casting values of one type into another, and
    creating unions that overlay at the same location values of different
    types at different times.

    And then there are tricky idioms like declaring a structure to have a
    zero length array as its last member, then allocating a chunk of
    memory large enough to contain both the structure and an array of some
    non-zero length.


    Basically, for uncooperative languages such as C, the GC has to
    consider as a /potential/ pointer every set of [pointer-length] bytes
    having the correct alignment to be a pointer. It must compare the
    value of each potential to the set of known heap objects, allowing for
    the pointer's value to be anywhere within [or even past] the bounds of
    the referenced object.

    Since GC can't be sure that any value that appears to be a pointer
    actually /is/ a pointer, in general, it can't move the referenced
    objects. Moving an object requires also changing all the pointers to
    it, but changing datums that really are not pointers but only appear
    to be ... well, that would corrupt the data.



    A bit more can be done with C++ because, in C++, structures are a kind
    of object (a POD object) and [at least modern] programmers are more
    likely to use stdlib array objects rather than C-style arrays.

    Detlefs created a GC for C++ he called "mostly moving" which was able
    to pin only those heap objects directly referenced by register or
    stack resident [potential] pointers. Heap objects pointed to only by
    other heap objects could be moved.



    Many of the issues with moving GC could be solved by changing the
    compiler to guarantee that object and array base pointers always are
    maintained regardless, and by making object layouts available at
    runtime. The latter could be done with various types of maps or by
    compiler generating an enumeration function for each type of object
    [including stack frames].

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 4 22:22:10 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:08:10 -0400, steve g wrote:


    Specific substantive response still lacking.


    I am actually nor familiar with this. thank you for mentioning it! I
    will certainly discuss this with a friend whois Dr Psychology. This will
    be a great discussion. seriously I think I can use this to impress him
    :)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c,comp.lang.asm on Tue Aug 4 22:26:33 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 01/08/2026 6:46 AM, Lawrence DrCOOliveiro wrote:
    On Fri, 31 Jul 2026 12:21:51 -0300, Anton Antimo wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct.
    What a dumb idea. Common Lisp is full of legacy baggage to cater to
    proprietary pre-POSIX OSes which are now extinct.

    As always, you start off by mouthing your own ignorance.

    * OpenVMS is both sold and ported to the x86. https://vmssoftware.com/

    I am actually glad to heear this! the women of the 70's loved these
    things :)


    * OS/2 is being sold and supported, under a new brand name.
    https://www.arcanoae.com/

    not the best solution in the world but it did/does work.
    I still think that PC-DOS was worth it's weight. Automatic IRQ, DMA,
    HIGHMEM managment all automated. Wow!


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c,comp.lang.python on Tue Aug 4 22:39:06 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:


    Flecks of foam and blood land on the keyboard. No birds sing; what once
    was grass is now dust and ash.

    Still he types, faster and faster now, singing and chanting.

    From the computer in the shack a cable runs. The camera follows it, to its end: copper cores poking through charred insulation.

    Fade.


    you are quite the poet.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 4 22:47:33 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Fri, 31 Jul 2026 23:52:27 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:26:56 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 29 Jun 2026 17:37:24 -0700, Paul Rubin wrote:

    If garbage collection is so good, why donrCOt OS kernels use it?

    You are probably using a shitty OS.

    So where is there a rCLnon-shitty OSrCY that uses garbage collection in
    its kernel? Does the one *you* use have garbage collection in its
    kernel?

    It depends on how the kernel is compiled.

    What a load of nonsense. There is no OS kernel you have access to,
    that uses garbage collection for internal memory management. Just
    admit it instead of trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c on Tue Aug 4 22:50:09 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 01/08/2026 11:59 AM, steve g wrote:
    Anton Antimo <anton@safunu.org> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which >>>>>> spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent >>> fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.
    Wait until you read LISP:Lisp In Small Pieces. it's published in france.


    I read the French edition. /Principes d'Implantation de Scheme et
    Lisp/, and it's now available as ebook on Amazon. I recommend it,
    it's a really fun book. I believe it's the /second edition/, and
    may have a little bit different content than the English one, which
    I haven't read.

    Do you read French?

    No I do not read french; just the algorithms. It is a fantastic book. I
    can also apparently read german algorithms but the comments and the
    docstrings can be difficult.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 5 02:54:18 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead of
    trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 4 23:05:53 2026
    From Newsgroup: comp.lang.lisp

    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!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 4 23:11:08 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead of
    trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?

    No, I do not wonder about microsoft or why their stuff fails.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 5 07:31:41 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 04 Aug 2026 23:11:08 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead
    of trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?

    No, I do not wonder about microsoft or why their stuff fails.

    Funny, you were just talking about it. Suddenly backpedalling when you
    realize itrCOs actually destroying rather than strengthening your
    argument?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 5 18:26:34 2026
    From Newsgroup: comp.lang.lisp

    On 05/08/2026 10:54 AM, Lawrence DrCOOliveiro wrote:
    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead of
    trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?

    Now, now, Lawrence, you're totally misunderstanding the situation. As
    always. Garbage collection is /not bad/. And we have a practical de- monstration of this in OpenSSL, hence adding comp.lang.c to the dis-
    cussion, where their lack of GC was causing a problem in the real world.


    https://securityaffairs.com/195588/hacking/openssl-fixes-hollowbyte-memory-exhaustion-bug.html

    I don't know why you're always trying to "sound smart" when everyone can
    see that you're just making a fool of yourself. /Every/. /Time/.

    You can stop being a troll any time you want. All you have to do, is to
    start to use the Illumos operating system for your desktop, with CDE as
    is proper on a Unix workstation. You can even use Xlibre because they
    love their X server on all kinds of operating system, unlike x.org.

    Now, once you've been illuminated enough by the Illumos operating system
    your outer troll shell will turn into stone. There won't be a speck of
    Rust on you.

    And then, only then, can you stop being a troll on comp.lang.lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 5 19:02:34 2026
    From Newsgroup: comp.lang.lisp

    On 05/08/2026 10:50 AM, steve g wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 01/08/2026 11:59 AM, steve g wrote:
    Anton Antimo <anton@safunu.org> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    [...]

    Sadly we've also ended up with programmers who think the machines >>>>>>> they program for are giant PDP-11s, and as a result machines which >>>>>>> spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent >>>> fast code that I'd write in C, where speed matters. In other words, I >>>> seem to gain nothing (other than more work) by writing typical
    applications in C.
    Wait until you read LISP:Lisp In Small Pieces. it's published in france. >>>

    I read the French edition. /Principes d'Implantation de Scheme et
    Lisp/, and it's now available as ebook on Amazon. I recommend it,
    it's a really fun book. I believe it's the /second edition/, and
    may have a little bit different content than the English one, which
    I haven't read.

    Do you read French?

    No I do not read french; just the algorithms. It is a fantastic book. I
    can also apparently read german algorithms but the comments and the docstrings can be difficult.

    That's good. If you want to brush up on your German, this course looks
    solid,


    https://shop.thegreatcourses.com/learning-german-a-journey-through-language-and-culture

    and I've been meaning to take it. Note that if you buy it now online,
    you only get it streaming, so if you want to download it, you can look
    for a DVD copy on Ebay.

    I haven't checked if it's available on the binary discussion groups of
    Usenet.

    Now is there some particular book you feel is worth my time in German?
    For either studying some C or Lisp arcana? Preferably not some basics,
    as those are already covered in English.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 5 11:29:17 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:
    In C the situation is complicated even beyond simply not being able to
    find pointers because the standard explicitly permits idioms and code optimizations that can obscure what pointers are there.


    I wonder how the Symbolics C compiler dealt with all this horror? That's
    not a rhetorical question: if anyone knows, I'd be interested, because it
    must have been painful.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.c on Wed Aug 5 13:13:42 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 31/07/2026 11:21 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which
    spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent
    fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.

    The fun is in writing atypical applications, and then finding yourself looking at the disassembly in SBCL.

    I actually do that every now and then just to learn a bit more about
    assembly, something I find so cool about SBCL (and lacking in other close-to-the-language tools).

    Speaking of which, I decided to try Common Lisp about 2 years ago,
    having struggled to deal with Racket for over ten years, nevertheless considering Racket the most elegant Lisp around ever since its birth.
    And, boy, did I never look back.

    (*) A critique of Racket

    To be fair, a big part of my struggle is the thick layer of Racket on
    top of POSIX. For instance, try to locate the equivalent select-call on
    it. It's so hard to recognize exactly how your Racket maps to the lower
    level. I understand that may a strong point of Racket's design, but it certainly hits my weakness.

    How about the macro system? So perfect, yet so annoying. One thing I
    love about Common Lisp is precisely macro's (lack of) hygiene. I'm
    totally fine with complete guarantee. Anaphoric macros are so useful.
    (No idea how to implement them in Racket---impossible?)

    Personally, I love writing in C, even though it's more verbose.

    That said, and to be mildly on-topic in comp.lang.lisp, have

    * /The Common Lisp Condition System/, and

    * /Programming Algorithms in Lisp/

    been mentioned before as resources for learning common lisp?

    These two books look lovely in my programming shelf, next to

    * /Common Lisp Recipes/, and

    * /Practical Common Lisp/,

    which must have been mentioned. They're interspersed with

    * /Low Level Programming/,

    * /String Algorithms in C/, and

    * /The Joys of Hashing/,

    which come in handy when you want to implement your own Common
    Lisp system.


    Enjoy!

    Enjoyed a lot! Thanks so much for sharing very useful references.

    Let me try to contribute with

    Let Over Lambda
    Doug Hoyte, 2008
    ISBN 978-1-4357-1275-1

    --8<-------------------------------------------------------->8---
    Let Over Lambda (ISBN 978-1-4357-1275-1, 376+iv pp.) is one of the
    most hardcore computer programming books out there. Starting with the
    fundamentals, it describes the most advanced features of the most
    advanced language: COMMON LISP. The point of this book is to expose
    you to ideas that you might otherwise never be exposed to.

    This book is about macros, that is programs that write
    programs. Macros are what make lisp the greatest programming language
    in the world. When used properly, macros enable amazing feats of
    abstraction, programmer productivity, and code efficiency and security
    that are unheard of elsewhere. Macros let you do things you simply
    cannot do in other languages.
    --8<-------------------------------------------------------->8---

    Source:
    Doug Hoyte, https://letoverlambda.com/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Madhu@enometh@meer.net to comp.lang.lisp on Wed Aug 5 23:46:00 2026
    From Newsgroup: comp.lang.lisp


    * tfb <114v6qd$2u5ab$1@dont-email.me> :
    Wrote on Wed, 5 Aug 2026 11:29:17 -0000 (UTC):

    George Neuner <gneuner2@comcast.net> wrote:
    In C the situation is complicated even beyond simply not being able to
    find pointers because the standard explicitly permits idioms and code
    optimizations that can obscure what pointers are there.


    I wonder how the Symbolics C compiler dealt with all this horror? That's
    not a rhetorical question: if anyone knows, I'd be interested, because it must have been painful.

    For the C standard of those decades,,

    Here's a llm remake of a 80s project that implements k&r c and the unix
    v7 c library. (I stopped reading after looking at the commits page)

    https://github.com/ChristineTham/lisp-cc https://raw.githubusercontent.com/ChristineTham/lisp-cc/main/README.md
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp,comp.lang.c on Wed Aug 5 13:05:19 2026
    From Newsgroup: comp.lang.lisp

    On 8/5/2026 3:26 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 05/08/2026 10:54 AM, Lawrence DrCOOliveiro wrote:
    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead of
    trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?

    Now, now, Lawrence, you're totally misunderstanding the situation.-a As always.-a Garbage collection is /not bad/.

    Yeah. Until its really bad. If you find yourself "needing" a GC, try to reevaluate your system.


    [...]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 5 21:48:57 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket
    on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket
    maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.

    Sounds very Java-like. Though perhaps not as irritating as Java.

    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.

    Let Over Lambda
    Doug Hoyte, 2008
    ISBN 978-1-4357-1275-1

    This book is about macros, that is programs that write programs.
    Macros are what make lisp the greatest programming language in the
    world. When used properly, macros enable amazing feats of
    abstraction, programmer productivity, and code efficiency and
    security that are unheard of elsewhere. Macros let you do things
    you simply cannot do in other languages.

    Given this is posted to comp.lang.c, itrCOs always worth mentioning
    these are not macros in the style of #define, but they work at the AST
    level. Which is really the only sensible way to implement a workable
    macro system.

    And no longer unique to Lisp.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 5 22:00:45 2026
    From Newsgroup: comp.lang.lisp

    If garbage collection is so good, why donrCOt high-performance operating
    system kernels use it? Why do they prefer reference-counting instead?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 5 22:34:52 2026
    From Newsgroup: comp.lang.lisp

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:
    If garbage collection is so good, why donrCOt high-performance operating system kernels use it? Why do they prefer reference-counting instead?


    All that is old is new again.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to comp.lang.lisp,comp.lang.c on Thu Aug 6 09:05:38 2026
    From Newsgroup: comp.lang.lisp

    On 05/08/2026 23:48, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    Given this is posted to comp.lang.c, itrCOs always worth mentioning
    these are not macros in the style of #define, but they work at the AST
    level. Which is really the only sensible way to implement a workable
    macro system.

    And no longer unique to Lisp.

    Given that this is entirely about Lisp (or at least it has absoltuely
    nothing to do with C), it should be posted only in comp.lang.list - not comp.lang.c. It would be very nice if the absurd level of pointless cross-postings we have seen recently were to stop. It is fine to have occasional cross-postings and "outside influence" in a newsgroup, but a
    few trolls have taken to cross-posting meaningless ramblings to all
    sorts of groups. I would ask all reasonable participants in Usenet
    threads to check the newsgroup lists on their posts, and trim them where
    it makes sense (or simply not to respond to the worst trolls).

    As for macros in programming languages, AST macros are /not/ the only "sensible" way to have macros. They are a very different thing from text-based macros as supported by the C pre-processor. The two types of
    macro have their advantages and disadvantages, and can be used for
    different purposes. The mistake is not in having one or the other, but
    in calling them both "macros". It is reasonable to note, however, that
    AST macros must be part of the language while text-based macros can be provided by a generic external tool (like m4).



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Aug 6 09:57:32 2026
    From Newsgroup: comp.lang.lisp

    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!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp on Thu Aug 6 11:33:54 2026
    From Newsgroup: comp.lang.lisp

    On 8/6/2026 12:05 AM, David Brown wrote:
    On 05/08/2026 23:48, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    Given this is posted to comp.lang.c, itrCOs always worth mentioning
    these are not macros in the style of #define, but they work at the AST
    level. Which is really the only sensible way to implement a workable
    macro system.

    And no longer unique to Lisp.

    Given that this is entirely about Lisp (or at least it has absoltuely nothing to do with C), it should be posted only in comp.lang.list - not comp.lang.c.-a It would be very nice if the absurd level of pointless cross-postings we have seen recently were to stop.-a It is fine to have occasional cross-postings and "outside influence" in a newsgroup, but a
    few trolls have taken to cross-posting meaningless ramblings to all
    sorts of groups.-a I would ask all reasonable participants in Usenet
    threads to check the newsgroup lists on their posts, and trim them where
    it makes sense (or simply not to respond to the worst trolls).

    As for macros in programming languages, AST macros are /not/ the only "sensible" way to have macros.-a They are a very different thing from text-based macros as supported by the C pre-processor.-a The two types of macro have their advantages and disadvantages, and can be used for
    different purposes.-a The mistake is not in having one or the other, but
    in calling them both "macros".-a It is reasonable to note, however, that
    AST macros must be part of the language while text-based macros can be provided by a generic external tool (like m4).

    Speaking of macros... Well, hold on to your horses:

    https://github.com/rofl0r/chaos-pp

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 6 15:49:21 2026
    From Newsgroup: comp.lang.lisp

    David Brown <david.brown@hesbynett.no> writes:

    On 05/08/2026 23:48, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:
    Given this is posted to comp.lang.c, itrCOs always worth mentioning
    these are not macros in the style of #define, but they work at the AST
    level. Which is really the only sensible way to implement a workable
    macro system.
    And no longer unique to Lisp.

    Given that this is entirely about Lisp (or at least it has absoltuely
    nothing to do with C), it should be posted only in comp.lang.list -
    not comp.lang.c. It would be very nice if the absurd level of
    pointless cross-postings we have seen recently were to stop. It is
    fine to have occasional cross-postings and "outside influence" in a newsgroup, but a few trolls have taken to cross-posting meaningless
    ramblings to all sorts of groups. I would ask all reasonable
    participants in Usenet threads to check the newsgroup lists on their
    posts, and trim them where it makes sense (or simply not to respond to
    the worst trolls).

    As for macros in programming languages, AST macros are /not/ the only "sensible" way to have macros. They are a very different thing from text-based macros as supported by the C pre-processor. The two types
    of macro have their advantages and disadvantages, and can be used for different purposes. The mistake is not in having one or the other,
    but in calling them both "macros". It is reasonable to note, however,
    that AST macros must be part of the language while text-based macros
    can be provided by a generic external tool (like m4).

    With all due respect, what's amusingly absurd is that while you protest
    the off-topic nature of the topic for comp.lang.c, you follow up on
    things like the C pre-processor, evidently showing the subject has at
    least a margin of connection to C programming.

    It's not the case anymore that comp.lang.c hosts that high volume of the
    late nineties. I vote for comp.lang.c to relax a bit until the USENET
    faces that exponentially growing volume once again---even if the article
    is from Lawrence D'Oliveiro or another author of manuals such as how to
    make friends on the USENET.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Thu Aug 6 19:25:26 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Tue, 04 Aug 2026 23:11:08 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Tue, 04 Aug 2026 22:47:33 -0400, steve g wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    There is no OS kernel you have access to, that uses garbage
    collection for internal memory management. Just admit it instead
    of trying to bullshit.

    well thanks. as Microsoft's Singularity apparently uses a GC.

    Try using past tense. ItrCOs a dead project. Wonder why?

    No, I do not wonder about microsoft or why their stuff fails.

    Funny, you were just talking about it. Suddenly backpedalling when you realize itrCOs actually destroying rather than strengthening your
    argument?

    The question I have is "what argument"?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c on Thu Aug 6 19:36:33 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:


    Now is there some particular book you feel is worth my time in German?
    For either studying some C or Lisp arcana? Preferably not some basics,
    as those are already covered in English.

    my answer would be using ITU (international morse code) and looking at
    American (or military) CW (continious wave). Many people claim they have learned both from just listening to it on the radio.

    Unfortunately radio is all but dead. This is a good thing; less "traffic police".

    As to english books I do have an excellent book one of my teachers gave
    me. it contains all the funky rules of american enhlish. I am not at
    "home" right now so I look it up and I can't remeber the name. She said
    just read and re-scim this book before writing papers in college. This
    is bothering me now...

    I personally think that you need to practice the language to understand
    it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Thu Aug 6 19:41:05 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    George Neuner <gneuner2@comcast.net> wrote:
    In C the situation is complicated even beyond simply not being able to
    find pointers because the standard explicitly permits idioms and code
    optimizations that can obscure what pointers are there.


    I wonder how the Symbolics C compiler dealt with all this horror? That's
    not a rhetorical question: if anyone knows, I'd be interested, because it must have been painful.

    It has been some time since I fired up the machine; but it is getting
    rather old (made in 1986 or so) and of course I do not have access to
    it. I do believe there was talk about a C interpreter. The hardest part
    would be writing the backend to support computers that are 30 years
    older than the machine.

    I think any C compiler is a nightmare in the parsing area.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Aug 6 20:23:08 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 6 Aug 2026 09:05:38 +0200, David Brown
    <david.brown@hesbynett.no> wrote:

    As for macros in programming languages, AST macros are /not/ the only >"sensible" way to have macros.

    Depends on your definition of "sensible". <grin>


    ... They are a very different thing from
    text-based macros as supported by the C pre-processor. The two types of >macro have their advantages and disadvantages, and can be used for
    different purposes. The mistake is not in having one or the other, but
    in calling them both "macros".

    I believe that particular confusion is all on C.

    Lisp's AST macros were invented in the summer of 1963. By the time C
    came along in 1972, the major Lisps[*] all included them. https://dspace.mit.edu/handle/1721.1/6111


    [*] not Common Lisp, but its predecessors


    ... It is reasonable to note, however, that
    AST macros must be part of the language while text-based macros can be >provided by a generic external tool (like m4).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Thu Aug 6 18:05:34 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:
    Let me try to contribute with
    Let Over Lambda
    Doug Hoyte, 2008
    ISBN 978-1-4357-1275-1

    For something easier (beginner friendly) I liked Land of Lisp,
    landoflisp.com. It even has a Lispy music video on its home page,
    plugging the book:

    https://www.youtube.com/watch?v=HM1Zb3xmvMc
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Fri Aug 7 09:36:27 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:
    On Thu, 6 Aug 2026 09:05:38 +0200, David Brown
    <david.brown@hesbynett.no> wrote:

    As for macros in programming languages, AST macros are /not/ the only >>"sensible" way to have macros.

    Depends on your definition of "sensible". <grin>

    Do you think that reader macros are sensible?
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 7 11:58:37 2026
    From Newsgroup: comp.lang.lisp

    Waldek Hebisch <antispam@fricas.org> wrote:

    Do you think that reader macros are sensible?


    I think nonstandard reader macros are used much less than ordinary macros
    in CL. I may be wrong.

    But reader macros are also not at all the same as C preprocessor macros:
    The C preprocessor accepts text and turns it into other text, while a CL
    reader macro accepts text and turns it into anything at all, which almost
    never is text. Consider the macro associated with '(' in the standard readtable, for instance.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 8 22:00:22 2026
    From Newsgroup: comp.lang.lisp

    On 05/08/2026 10:22 AM, steve g wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:08:10 -0400, steve g wrote:


    Specific substantive response still lacking.


    I am actually nor familiar with this. thank you for mentioning it! I
    will certainly discuss this with a friend whois Dr Psychology. This will
    be a great discussion. seriously I think I can use this to impress him
    :)


    I'm starting to think Lawrence has a list of words on a piece of paper,
    and uses dice to select them for his replies on Usenet. Nothing he says
    ever makes sense.

    I mean, at least he could do would be to run an L.L.M. and generate the
    words for him. It's less work, and doesn't require throwing all these
    dice.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 8 22:05:17 2026
    From Newsgroup: comp.lang.lisp

    On 06/08/2026 6:00 AM, Lawrence DrCOOliveiro wrote:
    If garbage collection is so good, why donrCOt high-performance operating system kernels use it? Why do they prefer reference-counting instead?

    Dear Lawrence,

    I don't know which operating system kernels you mean, you don't specify,
    and I don't want to read your mind. Apart from being impolite on my
    end, I think it'll be fruitless on your end.

    Please go to your nearest public library, and pick out the book

    /Garbage Collection/
    /Algorithms for Automatic/
    /Dynamic Memory Management/

    by Richard Jones, and Rafael Lins. Published in 1996.

    It explicitly states that reference counting is a discipline of garbage collectors. If you have reference counting, you have a garbage collect-
    or.


    Happy garbage deliveries!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.lang.lisp on Sat Aug 8 14:14:08 2026
    From Newsgroup: comp.lang.lisp

    Le 08-08-2026, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> a |-crit-a:
    On 05/08/2026 10:22 AM, steve g wrote:
    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Wed, 29 Jul 2026 16:08:10 -0400, steve g wrote:


    Specific substantive response still lacking.


    I am actually nor familiar with this. thank you for mentioning it! I
    will certainly discuss this with a friend whois Dr Psychology. This will
    be a great discussion. seriously I think I can use this to impress him
    :)


    I'm starting to think Lawrence has a list of words on a piece of paper,
    and uses dice to select them for his replies on Usenet. Nothing he says
    ever makes sense.

    I mean, at least he could do would be to run an L.L.M. and generate the
    words for him. It's less work, and doesn't require throwing all these
    dice.

    I guess I understand what you mean and that's why I disagree. Sometimes,
    he's very serious and what he says does make sense and is very
    interesting. And some other times his replies are senseless or
    uncorrelated with the message he's answering or plain dead stupid.

    So, I believe the game is to guess if one should laugh or answer seriously.
    --
    Si vous avez du temps |a perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Sat Aug 8 14:45:24 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I'm starting to think Lawrence has a list of words on a piece of paper,
    and uses dice to select them for his replies on Usenet. Nothing he says
    ever makes sense.

    I mean, at least he could do would be to run an L.L.M. and generate the
    words for him. It's less work, and doesn't require throwing all these
    dice.

    I think he (it?) may well *be* an LLM. In particular he (it?) has, at
    least twice, done this weird looping thing, asking the same question which
    has already been answered. That looks like something losing context.

    If it wasn't for the fact that usenet is moribund, an obvious way of
    acquiring training data for LLMs would be to set up troll bots and then use
    all the human responses to them as training data. Perhaps it's bit as
    moribund as I thought and someone is in fact doing this.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Sun Aug 9 02:11:52 2026
    From Newsgroup: comp.lang.lisp

    On 07/08/2026 7:36 AM, steve g wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:


    Now is there some particular book you feel is worth my time in German?
    For either studying some C or Lisp arcana? Preferably not some basics,
    as those are already covered in English.

    my answer would be using ITU (international morse code) and looking at American (or military) CW (continious wave). Many people claim they have learned both from just listening to it on the radio.

    Unfortunately radio is all but dead. This is a good thing; less "traffic police".

    As to english books I do have an excellent book one of my teachers gave
    me. it contains all the funky rules of american enhlish. I am not at
    "home" right now so I look it up and I can't remeber the name. She said
    just read and re-scim this book before writing papers in college. This
    is bothering me now...

    I personally think that you need to practice the language to understand
    it.

    I try to keep in shape by reading books in languages I'm not using. Or converse with people about programming languages I don't use anymore,
    such as Pascal.

    I've managed to keep my French more or less intact, but could use a
    brush up on Danish, and of course German as I said. I'm sure I'll
    find something to inspire me to keep practicing German. After all,
    I'm struggling to read Asterisk and Obelisk in Latin.


    Best wishes, and happy language studies in comp.lang.lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sun Aug 9 02:18:33 2026
    From Newsgroup: comp.lang.lisp

    On 08/08/2026 10:45 PM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I'm starting to think Lawrence has a list of words on a piece of paper,
    and uses dice to select them for his replies on Usenet. Nothing he says
    ever makes sense.

    I mean, at least he could do would be to run an L.L.M. and generate the
    words for him. It's less work, and doesn't require throwing all these
    dice.

    I think he (it?) may well *be* an LLM. In particular he (it?) has, at
    least twice, done this weird looping thing, asking the same question which has already been answered. That looks like something losing context.

    If it wasn't for the fact that usenet is moribund, an obvious way of acquiring training data for LLMs would be to set up troll bots and then use all the human responses to them as training data. Perhaps it's bit as moribund as I thought and someone is in fact doing this.


    Well, I have a friend who's playing L.L.M. training, and I just sent him
    a .zip file of all my posts since ca. 2019.

    Can you imagine, an L.L.M. that knows how to talk like me?

    Personally, I don't want to have anything to do with these things. But
    I don't begrudge people who train their own. All the more power to
    them, and their power bill.

    I much prefer to make my own mistakes, when coding Common Lisp, than to
    have a machine make them for me.


    Happy Lisping!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.lang.lisp on Sat Aug 8 19:02:48 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-07, Waldek Hebisch <antispam@fricas.org> wrote:
    George Neuner <gneuner2@comcast.net> wrote:
    On Thu, 6 Aug 2026 09:05:38 +0200, David Brown
    <david.brown@hesbynett.no> wrote:

    As for macros in programming languages, AST macros are /not/ the only >>>"sensible" way to have macros.

    Depends on your definition of "sensible". <grin>

    Do you think that reader macros are sensible?

    I've not implemented them in TXR Lisp. It's not that they are
    "insensible" or any other epithet.

    They have a disruptive effect in the ecosystem.

    In a project that is rife with someone's custom reader macros, your
    editor settings for the language probably don't work, for starters.

    Files of the langauge cannot be machine read without executing the
    directives which alter the read syntax. (Packages also have
    this problem, by the way).

    Reader macros usually have the deficiency that the syntax they
    accept cannot be printed and in the CL design that is not easily
    fixable: only CLOS objects can have custom printing.

    The output of a read macro that produces cons structure will print
    as cons structure.

    (Hardly ever would you want a read macro to produce a CLOS object;
    that would be useful if there were a standard method protocol to
    handle a CLOS object in syntax: like some method that transforms
    it to something else during the macro walk. I.e. during the read
    phase, the read macro goes to a CLOS object. Then during the processing
    of the form as code, the CLOS object is recognized and some
    predetermind protocol method is invoked on it; whatever it returns
    is substituted for the object.)

    This means that user-defined read macros are second-class citizens
    compared to built in ones like ' for quote: expressions like (quote X)
    do actually print as 'X.

    Read macros are basically a hack for situations when someone wants
    a certain notational input convenience so badly that they dismiss
    the disadvantages.

    In my project, I decided that the benevolent dictator for life should
    decide all the read syntax, and that read syntax will be a combination
    of the right amount of tasteful choices that nobody will need anything
    else.

    If the language controls read syntax, you can do some things that
    are slightlly hard to parse for just dispatch tables.

    An example of this is the consing dot. You can't just wire a
    self-contained, context-free function dispatched on the character #\. to implement the consing dot. The parsing context for scanning a list has
    to recognize and handle it.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sun Aug 9 05:26:34 2026
    From Newsgroup: comp.lang.lisp

    On 06/08/2026 12:13 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 31/07/2026 11:21 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    [...]

    Sadly we've also ended up with programmers who think the machines
    they program for are giant PDP-11s, and as a result machines which >>>>>> spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent >>> fast code that I'd write in C, where speed matters. In other words, I
    seem to gain nothing (other than more work) by writing typical
    applications in C.

    The fun is in writing atypical applications, and then finding yourself
    looking at the disassembly in SBCL.

    I actually do that every now and then just to learn a bit more about assembly, something I find so cool about SBCL (and lacking in other close-to-the-language tools).

    Speaking of which, I decided to try Common Lisp about 2 years ago,
    having struggled to deal with Racket for over ten years, nevertheless considering Racket the most elegant Lisp around ever since its birth.
    And, boy, did I never look back.

    (*) A critique of Racket

    To be fair, a big part of my struggle is the thick layer of Racket on
    top of POSIX. For instance, try to locate the equivalent select-call on
    it. It's so hard to recognize exactly how your Racket maps to the lower level. I understand that may a strong point of Racket's design, but it certainly hits my weakness.

    How about the macro system? So perfect, yet so annoying. One thing I
    love about Common Lisp is precisely macro's (lack of) hygiene. I'm
    totally fine with complete guarantee. Anaphoric macros are so useful.
    (No idea how to implement them in Racket---impossible?)


    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.


    Personally, I love writing in C, even though it's more verbose.

    That said, and to be mildly on-topic in comp.lang.lisp, have

    * /The Common Lisp Condition System/, and

    * /Programming Algorithms in Lisp/

    been mentioned before as resources for learning common lisp?

    These two books look lovely in my programming shelf, next to

    * /Common Lisp Recipes/, and

    * /Practical Common Lisp/,

    which must have been mentioned. They're interspersed with

    * /Low Level Programming/,

    * /String Algorithms in C/, and

    * /The Joys of Hashing/,

    which come in handy when you want to implement your own Common
    Lisp system.


    Enjoy!

    Enjoyed a lot! Thanks so much for sharing very useful references.

    Let me try to contribute with

    Let Over Lambda
    Doug Hoyte, 2008
    ISBN 978-1-4357-1275-1


    [snip]

    Thank you. I went to a bookstore, and put a copy in my shopping cart.

    I'm not in a hurry, and I'm not sure when I'll exit the bookstore, for
    I have other books to buy. It might take a month, or more.

    By the time I have further need for macros in Common Lisp, I'm all for
    reading this book.

    Have a nice book shopping day!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Sun Aug 9 05:33:22 2026
    From Newsgroup: comp.lang.lisp

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket
    on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket
    maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.

    Sounds very Java-like. Though perhaps not as irritating as Java.

    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.


    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, so I'm impelled to ask, what is
    is that you use select for, in Python?

    https://www.sbcl.org/manual/#networking


    Let Over Lambda
    Doug Hoyte, 2008
    ISBN 978-1-4357-1275-1

    This book is about macros, that is programs that write programs.
    Macros are what make lisp the greatest programming language in the
    world. When used properly, macros enable amazing feats of
    abstraction, programmer productivity, and code efficiency and
    security that are unheard of elsewhere. Macros let you do things
    you simply cannot do in other languages.

    Given this is posted to comp.lang.c, itrCOs always worth mentioning
    these are not macros in the style of #define, but they work at the AST
    level. Which is really the only sensible way to implement a workable
    macro system.

    And no longer unique to Lisp.

    Indeed. If you want to manipulate C code at the AST level, in C, all
    you need to do is to hook your code with libclang. It's annoying to
    use, because it's a private API for the fruit vendor, and mostly un- documented. That's why I basically gave up on using it in my own pro-
    jects.


    Good luck with libclang!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sat Aug 8 18:37:40 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 9 Aug 2026 05:26:34 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.

    I don't find writing macros annoying, but I also don't do it very
    often. I bother only when I find myself frequently repeating a bunch
    of boilerplate.

    As it happens, nowadays I'm doing DBMS middleware and backend systems,
    and there tends to be quite a bit of surrounding code that is the same
    [or nearly so] for every database query.

    MMV.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sat Aug 8 19:08:50 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo <anton@safunu.org>
    wrote:


    (*) A critique of Racket

    To be fair, a big part of my struggle is the thick layer of Racket on
    top of POSIX. For instance, try to locate the equivalent select-call on
    it. It's so hard to recognize exactly how your Racket maps to the lower >level. I understand that may a strong point of Racket's design, but it >certainly hits my weakness.

    To be fair, you need to understand that Racket is multi-platform,
    needs to run on Windows, and Windows [for the most part] does not
    implement POSIX functions.

    Racket's network [and filesystem, and ... ] implementation tries to
    abstract over equivalent behaviors on all the target platforms.


    How about the macro system? So perfect, yet so annoying. One thing I
    love about Common Lisp is precisely macro's (lack of) hygiene. I'm
    totally fine with complete guarantee. Anaphoric macros are so useful.
    (No idea how to implement them in Racket---impossible?)

    Racket has its roots in Scheme. Scheme is defined in terms of source
    /text/ rather than the compiler's AST. So there is no real equivalent
    of Lisp's AST macros.

    That said, Racket does support Lisp-like unhygienic macros with
    'define-macro'. Apologies for the ridiculous length of the URL.

    https://docs.racket-lang.org/compatibility/defmacro.html#%28form._%28%28lib._compatibility%2Fdefmacro..rkt%29._define-macro%29%29
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Sun Aug 9 08:52:28 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.


    It is so weird that people use a language whose defining feature is the incremental construction of languages and then say they don't use that
    feature. I mean, I'm aware people do that, but it's just so fucking weird.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Sun Aug 9 11:50:07 2026
    From Newsgroup: comp.lang.lisp


    Ar an naoi|| l|i de m|! L||nasa, scr|!obh tfb:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.

    It is so weird that people use a language whose defining feature is the incremental construction of languages and then say they don't use that feature. I mean, I'm aware people do that, but it's just so fucking weird.

    I donrCOt find macros annoying, but I will use macrolet much more than defmacro.
    Usually no point making a utility macro available in the run-time namespace. (This is XEmacs Lisp, so reader macros not available.)

    Common Lisp is big and thererCOs plenty worth using in the rest of the language.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sun Aug 9 23:01:46 2026
    From Newsgroup: comp.lang.lisp

    On 09/08/2026 6:50 PM, Aidan Kehoe wrote:

    Ar an naoi|| l|i de m|! L||nasa, scr|!obh tfb:

    > Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    > >
    > > I've found the Common Lisp macro system annoying enough that I rarely
    > > use it. I'm OK with functions most of the time, and CLOS the rest of
    > > the time. And only resort to macros when I can't do anything else in
    > > the situation.
    >
    > It is so weird that people use a language whose defining feature is the
    > incremental construction of languages and then say they don't use that
    > feature. I mean, I'm aware people do that, but it's just so fucking weird.

    I donrCOt find macros annoying, but I will use macrolet much more than defmacro.
    Usually no point making a utility macro available in the run-time namespace. (This is XEmacs Lisp, so reader macros not available.)

    I've never really gotten the hang of when I need to use (gensym) and
    and when I don't. If I ever reach those heights of Common Lisp arcana,
    I may change my mind and use macros all the time.

    Chances are, I won't. I have this feeling that macros should be used as
    a last resort, and not as the first /weapon of choice/ when coding Comm-
    on Lisp.


    Common Lisp is big and thererCOs plenty worth using in the rest of the language.


    Indeed, and QuickLisp makes it bigger. It's perhaps the major reason I
    find myself faster at coding certain tasks in Common Lisp than most
    other programming languages. Though packages of various types are now commonplace in other common programming languages.

    Perhaps the major beauty of the Common Lisp social culture, is the disc-
    ipline of keeping interfaces stable. As far as I've heard, the /Python-
    ic/ interfaces are always in flux, perhaps because their Python is ever writhing? It didn't help when they ditched the syntax of Python 2.7.
    Many people whose code got obsolete decided never to use that language
    again. And with good reason.

    Of course, cultures change, but Common Lisp is eternal. I'm sure we can
    still code all of our websites with Hunchentoot without ever having the
    need to learn something new, several hundred years from now.


    Happy coding in Common Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sun Aug 9 20:34:23 2026
    From Newsgroup: comp.lang.lisp

    If garbage collection is so good, why donrCOt high-performance operating
    system kernels use it? Why do they prefer reference-counting instead?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sun Aug 9 20:36:33 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 09 Aug 2026 11:50:07 +0100, Aidan Kehoe wrote:

    Common Lisp is big and thererCOs plenty worth using in the rest of the language.

    It leaves out too many things we take for granted in this era of
    pretty much universal POSIX availability.

    Where are the Common Lisp equivalents of these?

    <https://docs.python.org/3/library/subprocess.html> <https://docs.python.org/3/library/threading.html> <https://docs.python.org/3/library/select.html>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 10 05:32:45 2026
    From Newsgroup: comp.lang.lisp

    On 10/08/2026 4:36 AM, Lawrence DrCOOliveiro wrote:
    On Sun, 09 Aug 2026 11:50:07 +0100, Aidan Kehoe wrote:

    Common Lisp is big and thererCOs plenty worth using in the rest of the
    language.

    It leaves out too many things we take for granted in this era of
    pretty much universal POSIX availability.

    Where are the Common Lisp equivalents of these?

    <https://docs.python.org/3/library/subprocess.html> <https://docs.python.org/3/library/threading.html> <https://docs.python.org/3/library/select.html>

    Now now Lawrence, you don't get to cause trouble for the other students
    of Common Lisp. Just because you're lazy doesn't mean you can expect
    everyone else to look things up for you.

    Please tell us in exquisite details what you're missing from

    https://www.sbcl.org/manual/

    and maybe we can just add it to Steel Bank's Common Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 18:42:29 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 6:00 AM, Lawrence DrCOOliveiro wrote:
    If garbage collection is so good, why donrCOt high-performance operating
    system kernels use it? Why do they prefer reference-counting instead?

    to be a high performance kernel you should not need to do garbage
    collection. GC is for user space, not kernel space. Kernel developers
    are usually very good programmers.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 18:47:01 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    I think he (it?) may well *be* an LLM.


    I was asked a psychiatrist what an LLM is. Large Language Model makes no
    sense. What is behind this LLM, neural nets? I was thkng that semantic
    nets. How do I go about writing an LLM, no I do not want to use one; I
    want to write one (list is comp.lang.lisp afterall).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.lang.c on Sun Aug 9 18:49:36 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    I try to keep in shape by reading books in languages I'm not using. Or converse with people about programming languages I don't use anymore,
    such as Pascal.

    I've managed to keep my French more or less intact, but could use a
    brush up on Danish, and of course German as I said. I'm sure I'll
    find something to inspire me to keep practicing German. After all,
    I'm struggling to read Asterisk and Obelisk in Latin.


    Best wishes, and happy language studies in comp.lang.lisp!


    Have you tried shortwave radio? You'll get all kinds of people talking different languages; not to mention it is rather entertaining.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 18:59:19 2026
    From Newsgroup: comp.lang.lisp

    Kaz Kylheku <046-301-5902@kylheku.com> writes:


    Do you think that reader macros are sensible?

    I've not implemented them in TXR Lisp. It's not that they are
    "insensible" or any other epithet.

    They have a disruptive effect in the ecosystem.


    I remeber the orinial discussion that reader macros do nothing more than
    slow down compilation. Not to mention the confusions.

    I liked the idea of

    (with-current-readtable (xyz)
    ...)

    i think franz was doing this, and they added the case of symbols.

    At readtime they can be usefull. When I'm done using the reader macro I reinstall the old one.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 19:02:00 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    It is so weird that people use a language whose defining feature is the incremental construction of languages and then say they don't use that feature. I mean, I'm aware people do that, but it's just so fucking weird.

    I do not use CLOS. I already know I am weird.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 19:09:04 2026
    From Newsgroup: comp.lang.lisp

    Jyyohann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    I've never really gotten the hang of when I need to use (gensym) and
    and when I don't. If I ever reach those heights of Common Lisp arcana,
    I may change my mind and use macros all the time.

    using macros to enhance performance is usually a bad idea. The macros
    save time.

    (macrolet ((def-optimize (name args &body forms)
    ;; Optimize a function for inlining.
    (assert (symbolp name))
    `(progn
    (declaim (inline ,name))
    (defun ,name ,args
    ;; these
    (declare (optimize speed (compilation-speed 0) (debug 1) (safety 2) (space 0)))
    ,@forms))))

    (def-optimize list-length=1 (lst)
    (declare (list lst))
    "Return T or nil if length of the list <lst> is one."
    (and (consp lst) (null (cdr lst)))
    ))

    I find this better than rewriting a bunch of code or implementing
    defsubst. Macros should not be an initial response. wait until you think
    you need them... IMHO




    Chances are, I won't. I have this feeling that macros should be used as
    a last resort, and not as the first /weapon of choice/ when coding Comm-
    on Lisp.

    Common Lisp is big and thererCOs plenty worth using in the rest of the
    language.


    Indeed, and QuickLisp makes it bigger. It's perhaps the major reason I
    find myself faster at coding certain tasks in Common Lisp than most
    other programming languages. Though packages of various types are now commonplace in other common programming languages.

    Perhaps the major beauty of the Common Lisp social culture, is the disc- ipline of keeping interfaces stable. As far as I've heard, the /Python-
    ic/ interfaces are always in flux, perhaps because their Python is ever writhing? It didn't help when they ditched the syntax of Python 2.7.
    Many people whose code got obsolete decided never to use that language
    again. And with good reason.

    Of course, cultures change, but Common Lisp is eternal. I'm sure we can still code all of our websites with Hunchentoot without ever having the
    need to learn something new, several hundred years from now.


    Happy coding in Common Lisp!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 9 19:12:49 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    To be fair, you need to understand that Racket is multi-platform,
    needs to run on Windows, and Windows [for the most part] does not
    implement POSIX functions.

    Can you use CYGwin? it is a bit ugly but it is POSIX. Microsoft should
    be able to introduce a POSIX level (xyz) rather easily; they just don't
    do that. It's like the Xterminal.

    dunno, I cannot use windows 11; it needs a credit card. God bless the
    Free Software Project!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Stefan Monnier@monnier@iro.umontreal.ca to comp.lang.lisp on Sun Aug 9 11:51:34 2026
    From Newsgroup: comp.lang.lisp

    Do you think that reader macros are sensible?
    I've not implemented them in TXR Lisp. It's not that they are
    "insensible" or any other epithet.
    They have a disruptive effect in the ecosystem.

    +1

    Reader macros have been proposed/requested for ELisp several times, but
    we've managed to resist the temptation so far.


    === Stefan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp on Mon Aug 10 00:56:32 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-09, tfb wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.


    It is so weird that people use a language whose defining feature is the incremental construction of languages and then say they don't use that feature. I mean, I'm aware people do that, but it's just so fucking weird.

    Why should it be termed "weird" at all? Is this one of these things
    where somebody comes up with a definition of the "normal" way to do
    things and points fingers at anyone who deviates from that? Or is macro
    system usage somehow mandatory for Lisp programming?
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Mon Aug 10 01:46:13 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 06 Aug 2026 19:25:26 -0400, steve g wrote:

    The question I have is "what argument"?

    Since you mentioned MicrosoftrCOs Singularity, letrCOs look in a bit
    more detail at it, shall we?

    It was some kind of OS rCLresearch projectrCY. rCLLetrCOs build yet another microkernelrCY, they thought. As if that wasnrCOt a bad enough idea, they
    also thought rCLletrCOs include garbage collection in the kernelrCY. Perhaps two sufficiently bad ideas, mashed together sufficiently thoroughly,
    will add up to something good?

    So what came out of that research project? Nothing, that I can see. It
    was abandoned, and then disappeared without leaving any trace on the
    world of computer science. Can you find some published papers on it?
    Do they say anything more than rCLthis is not something that should be
    tried againrCY?

    Because if you go to the website, the link to the downloadable
    software disappears off into the ether. It would have gone to
    MicrosoftrCOs old Codeplex site, but that got subsumed into GitHub.
    Except I donrCOt think the Singularity stuff survived the transition.
    Somebody probably thought rCLthis is best forgottenrCY.

    Feel free to prove me wrong. But somehow I donrCOt think you would know
    where to start.

    Of course, you could always regurgitate some AI slop, if you think it
    will help ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Mon Aug 10 01:48:49 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    On Wed, 5 Aug 2026 22:00:45 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If garbage collection is so good, why donrCOt high-performance
    operating system kernels use it? Why do they prefer
    reference-counting instead?

    to be a high performance kernel you should not need to do garbage
    collection.

    But isnrCOt that supposed to be better than reference-counting? Offering
    higher performance or something?

    GC is for user space, not kernel space. Kernel developers are
    usually very good programmers.

    Do different laws of physics apply in kernel space or something?
    And/or is that an admission that garbage collection is not for rCLvery
    good programmersrCY?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Mon Aug 10 00:48:59 2026
    From Newsgroup: comp.lang.lisp

    Stefan Monnier <monnier@iro.umontreal.ca> writes:
    Reader macros have been proposed/requested for ELisp several times, but
    we've managed to resist the temptation so far.

    I remember using them in CL for some kind of embedded DSL, but that kind
    of thing is normally not done with Emacs.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Mon Aug 10 00:54:06 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    It is so weird that people use a language whose defining feature is
    the incremental construction of languages and then say they don't use
    that feature. I mean, I'm aware people do that, but it's just so
    fucking weird.

    For a long time, Scheme didn't have macros, but it was still considered
    cool.

    Lisp macros are generally a way for user code to get hold of unevaluated
    args in a sexp. If your language has lazy evaluation (Haskell) and/or syntactic support for your likely macro use cases (lots of languages),
    macros become less important. As Lispers like to say, syntax is no big
    deal. So why obsess about being able to redefine it?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.c on Mon Aug 10 01:11:03 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, so I'm impelled to ask, what is
    is that you use select for, in Python?

    Select is used to listening to a bunch of file descriptors
    simultaneously and unblocking as soon as data becomes available on one
    or more of the fd's. These days it's somewhat superseded by epoll or
    io_uring or a few other alternatives.

    I actually don't see any of these in the sbcl manual, though maybe I
    didn't look hard enough. I'd expect to see it in the streams or
    concurrency modules. You could use threads and mailboxes instead, but
    that's often overkill, especially with posix threads.

    I see a mention of:

    *Recursive Event Loop*: SBCL provides a recursive event loop
    (serve-event) for doing non-blocking IO on multiple streams without
    using threads.

    But I don't see anything more about that in the manual. There's a
    reddit thread saying it's poorly supported:

    https://old.reddit.com/r/Common_Lisp/comments/kdk6mq/how_to_use_serveevent_from_sbcl/

    Anyway that is basically what select is for.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andreas Eder@a_eder_muc@web.de to comp.lang.lisp on Mon Aug 10 14:21:38 2026
    From Newsgroup: comp.lang.lisp

    On So 09 Aug 2026 at 05:26, Johann 'Myrkraverk' Oskarsson wrote:

    On 06/08/2026 12:13 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 31/07/2026 11:21 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    [...]

    Sadly we've also ended up with programmers who think the machines >>>>>>> they program for are giant PDP-11s, and as a result machines which >>>>>>> spend a huge amount of effort pretending to be giant PDP-11s.

    It's all a tragedy.

    The tragedy is not using Common Lisp for everything.

    I loved this bit and I have a feeling you're correct. My little
    experience with Common Lisp is that it allows me to write the equivalent >>>> fast code that I'd write in C, where speed matters. In other words, I >>>> seem to gain nothing (other than more work) by writing typical
    applications in C.

    The fun is in writing atypical applications, and then finding yourself
    looking at the disassembly in SBCL.
    I actually do that every now and then just to learn a bit more about
    assembly, something I find so cool about SBCL (and lacking in other
    close-to-the-language tools).
    Speaking of which, I decided to try Common Lisp about 2 years ago,
    having struggled to deal with Racket for over ten years, nevertheless
    considering Racket the most elegant Lisp around ever since its birth.
    And, boy, did I never look back.
    (*) A critique of Racket
    To be fair, a big part of my struggle is the thick layer of Racket on
    top of POSIX. For instance, try to locate the equivalent select-call on
    it. It's so hard to recognize exactly how your Racket maps to the lower
    level. I understand that may a strong point of Racket's design, but it
    certainly hits my weakness.
    How about the macro system? So perfect, yet so annoying. One thing I
    love about Common Lisp is precisely macro's (lack of) hygiene. I'm
    totally fine with complete guarantee. Anaphoric macros are so useful.
    (No idea how to implement them in Racket---impossible?)

    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.

    That us exactly where it should be used - when there is no other way.

    'Andreas
    --
    ceterum censeo redmondinem esse delendam
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andreas Eder@a_eder_muc@web.de to comp.lang.lisp on Mon Aug 10 14:44:46 2026
    From Newsgroup: comp.lang.lisp

    On Mi 05 Aug 2026 at 11:29, tfb wrote:

    George Neuner <gneuner2@comcast.net> wrote:
    In C the situation is complicated even beyond simply not being able to
    find pointers because the standard explicitly permits idioms and code
    optimizations that can obscure what pointers are there.


    I wonder how the Symbolics C compiler dealt with all this horror? That's
    not a rhetorical question: if anyone knows, I'd be interested, because it must have been painful.

    The ZetaLisp C compiler is now in public domain.
    You can have a look at http://www.bitsavers.org/bits/TI/Explorer/zeta-c/

    Apparently there is also a C compiler for Common Lisp at https://github.com/vsedach/Vacietis

    But I never use any, so take that with enough grains of salt.

    'Andreas
    --
    ceterum censeo redmondinem esse delendam
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Mon Aug 10 10:48:48 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo <anton@safunu.org>
    wrote:


    (*) A critique of Racket

    To be fair, a big part of my struggle is the thick layer of Racket on
    top of POSIX. For instance, try to locate the equivalent select-call
    on it. It's so hard to recognize exactly how your Racket maps to the
    lower level. I understand that may a strong point of Racket's design,
    but it certainly hits my weakness.

    To be fair, you need to understand that Racket is multi-platform,
    needs to run on Windows, and Windows [for the most part] does not
    implement POSIX functions.

    Racket's network [and filesystem, and ... ] implementation tries to
    abstract over equivalent behaviors on all the target platforms.

    I understand that. I shouldn't have written "a critique of Racket" as
    my post is really personal. It's my weakness. I think in terms of POSIX---likely because I started there. I got to know Racket after
    giving myself a year of C and UNIX. Now, in my defense, I think my
    situation would be worse if I had started out in Racket and then later discovered C and UNIX, say. Call me stupid or whatever, but I'm happy
    where I am.

    And by the way some of my complains can also be exactly applied to
    Common Lisp. For instance, I think Common Lisp doesn't have the
    semantics of POSIX's read(2). I suppose there are libraries out there
    that might go lower level (than Common Lisp's) and then give you an
    abstraction that mimics read(2), but that's beside the point.

    In the end I think we need to deal with the likely-fact that we can't
    really write every program as something 100% portable (and not to be
    totally slow at the same time, say).

    But anyway I totally understand your point here. Thanks for sharing.

    How about the macro system? So perfect, yet so annoying. One thing I
    love about Common Lisp is precisely macro's (lack of) hygiene. I'm
    totally fine with complete guarantee. Anaphoric macros are so useful.
    (No idea how to implement them in Racket---impossible?)

    Racket has its roots in Scheme. Scheme is defined in terms of source
    /text/ rather than the compiler's AST. So there is no real equivalent
    of Lisp's AST macros.

    Interesting. I bet this has been one my major difficulties because I had
    never quite understood that and I probably still don't. I had realized
    I always needed to manipulate the syntax objects as opposed to sexps and
    it was always confusing to insert a new identifier into the generating
    code and so on. The blame is of course always on me, but yeah---difficult-to-understand stuff. Common Lisp is a lot simpler, I
    feel. (Let me also say that I was never able to understand Scheme
    compilers' error messages, Racket included.)

    Is there an article out there that elaborate your paragraph here? I'd
    like to learn more about these differences. I suppose the Scheme people
    would have very strong arguments to go their way.

    That said, Racket does support Lisp-like unhygienic macros with 'define-macro'. Apologies for the ridiculous length of the URL.

    https://docs.racket-lang.org/compatibility/defmacro.html#%28form._%28%28lib._compatibility%2Fdefmacro..rkt%29._define-macro%29%29

    We need a project that can promise to shorten and maintain URLs for 50
    years, say. (I say fifty so a single hacker can keep it running during
    his lifetime. After 50 years, a young hacker takes it on for another
    50.) It'a pity that Google Inc. let us down with goo.gl.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.lang.lisp on Mon Aug 10 14:57:40 2026
    From Newsgroup: comp.lang.lisp

    [-comp.lang.c]

    In article <87jypyqtt4.fsf@nightsong.com>,
    Paul Rubin <no.email@nospam.invalid> wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, so I'm impelled to ask, what is
    is that you use select for, in Python?

    Select is used to listening to a bunch of file descriptors
    simultaneously and unblocking as soon as data becomes available on one
    or more of the fd's. These days it's somewhat superseded by epoll or >io_uring or a few other alternatives.

    I actually don't see any of these in the sbcl manual, though maybe I
    didn't look hard enough. I'd expect to see it in the streams or
    concurrency modules. You could use threads and mailboxes instead, but
    that's often overkill, especially with posix threads.

    You can use `select` (or `poll`, `epoll`, `kqueue`, etc) from
    SBCL using the FFI, but most programs use `usocket` or `iolib`
    instead.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.lang.lisp on Mon Aug 10 15:05:07 2026
    From Newsgroup: comp.lang.lisp

    In article <87zeyuvru2.fsf@gmail.com>, steve g <Sgonedes1977@gmail.com> wrote: >Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 6:00 AM, Lawrence DrCOOliveiro wrote:
    If garbage collection is so good, why donrCOt high-performance operating >>> system kernels use it? Why do they prefer reference-counting instead?

    to be a high performance kernel you should not need to do garbage
    collection. GC is for user space, not kernel space. Kernel developers
    are usually very good programmers.

    The problem with wrestling with a pig is that you get covered in
    shit and the pig likes it. Kinda like arguing with Lawrence.

    Of course modern operating systems do things equivalent to
    garbage collection; what does he think RCU is? It is used
    pervasively in his one-true-OS, Linux. Or, really, any of the
    deferred memory reclamation techniques used for high performance
    lock-free data structures in non-GC languages.

    For that matter, there are kernels implemented in garbage
    collected languages; biscuit comes to mind as an example: https://github.com/mit-pdos/biscuit

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp,comp.lang.c on Mon Aug 10 13:08:53 2026
    From Newsgroup: comp.lang.lisp

    On 8/8/2026 11:11 AM, Johann 'Myrkraverk' Oskarsson wrote:
    On 07/08/2026 7:36 AM, steve g wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:


    Now is there some particular book you feel is worth my time in German?
    For either studying some C or Lisp arcana?-a Preferably not some basics, >>> as those are already covered in English.

    my answer would be using ITU (international morse code) and looking at
    American (or military) CW (continious wave). Many people claim they have
    learned both from just listening to it on the radio.

    Unfortunately radio is all but dead. This is a good thing; less "traffic
    police".

    As to english books I do have an excellent book one of my teachers gave
    me. it contains all the funky rules of american enhlish. I am not at
    "home" right now so I look it up and I can't remeber the name. She said
    just read and re-scim this book before writing papers in college. This
    is bothering me now...

    I personally think that you need to practice the language to understand
    it.

    I try to keep in shape by reading books in languages I'm not using.-a Or converse with people about programming languages I don't use anymore,
    such as Pascal.

    I've managed to keep my French more or less intact, but could use a
    brush up on Danish, and of course German as I said.-a I'm sure I'll
    find something to inspire me to keep practicing German.-a After all,
    I'm struggling to read Asterisk and Obelisk in Latin.






    Best wishes, and happy language studies in comp.lang.lisp!

    Kind of makes my ears go all pointy wrt, is that from an ai?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp,comp.lang.c on Mon Aug 10 13:10:14 2026
    From Newsgroup: comp.lang.lisp

    On 8/10/2026 1:11 AM, Paul Rubin wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, so I'm impelled to ask, what is
    is that you use select for, in Python?

    Select is used to listening to a bunch of file descriptors
    simultaneously and unblocking as soon as data becomes available on one
    or more of the fd's. These days it's somewhat superseded by epoll or io_uring or a few other alternatives.

    I actually don't see any of these in the sbcl manual, though maybe I
    didn't look hard enough. I'd expect to see it in the streams or
    concurrency modules. You could use threads and mailboxes instead, but
    that's often overkill, especially with posix threads.

    I see a mention of:

    *Recursive Event Loop*: SBCL provides a recursive event loop
    (serve-event) for doing non-blocking IO on multiple streams without
    using threads.

    But I don't see anything more about that in the manual. There's a
    reddit thread saying it's poorly supported:

    https://old.reddit.com/r/Common_Lisp/comments/kdk6mq/how_to_use_serveevent_from_sbcl/

    Anyway that is basically what select is for.

    select works fine, but put it under pressure... Well, no so much... ;^o
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.c on Mon Aug 10 17:41:30 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket
    on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket
    maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.
    Sounds very Java-like. Though perhaps not as irritating as Java.
    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.


    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, [...]

    It would be like writing C in Lisp notation. For select (called unix-fast-select in SBCL), see sb-unix.

    (defun wait-for-stdin-select ()
    (sb-alien:with-alien ((read-fds (sb-alien:struct sb-unix:fd-set)))
    (sb-unix:fd-zero read-fds)
    (sb-unix:fd-set 0 read-fds)
    (format t "Waiting up to 5 seconds for input on stdin... Type something!~%")
    (force-output)
    (multiple-value-bind (count err)
    (sb-unix:unix-fast-select 1 (sb-alien:addr read-fds) nil nil 5 0)
    (cond
    ((null count)
    (format t "Select failed with errno: ~A~%" err))
    ((zerop count)
    (format t "Timeout! No input received.~%"))
    ((sb-unix:fd-isset 0 read-fds)
    (format t "Data is ready to be read from stdin!~%"))
    (t
    (format t "Something else woke up select!~%"))))))

    ;; run it
    (wait-for-stdin-select)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp,comp.lang.c on Mon Aug 10 23:53:00 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 10 Aug 2026 17:41:30 -0300, Anton Antimo wrote:

    For select (called unix-fast-select in SBCL), see sb-unix.

    select(2) is considered an archaic way of doing things these days,
    because of its ABI limitations. The modern way is poll() <https://manpages.debian.org/poll(2)> (POSIX) or even epoll() <https://manpages.debian.org/epoll(7)> (Linux-specific).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Mon Aug 10 23:55:36 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 10 Aug 2026 10:48:48 -0300, Anton Antimo wrote:

    I think in terms of POSIX---likely because I started there.

    Nothing wrong with that. I agree, and I didnrCOt even start there.

    The general rule nowadays is: beware of language-specific APIs that
    try to abstract away too much of POSIX.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Mon Aug 10 21:10:47 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Thu, 06 Aug 2026 19:25:26 -0400, steve g wrote:

    The question I have is "what argument"?

    Since you mentioned MicrosoftrCOs Singularity, letrCOs look in a bit
    more detail at it, shall we?

    It was some kind of OS rCLresearch projectrCY. rCLLetrCOs build yet another microkernelrCY, they thought. As if that wasnrCOt a bad enough idea, they also thought rCLletrCOs include garbage collection in the kernelrCY. Perhaps two sufficiently bad ideas, mashed together sufficiently thoroughly,
    will add up to something good?

    Any programmer that puts anivirus software on a dedicated database server is weird.


    So what came out of that research project? Nothing, that I can see. It
    was abandoned, and then disappeared without leaving any trace on the
    world of computer science.

    how much money did they burn through for their "talking paper clip AI"
    that was introduced to in the 90s that destroyed the then excellent
    microsoft help system?

    Can you find some published papers on it?
    Do they say anything more than rCLthis is not something that should be
    tried againrCY?

    I wish... From what I understand they are hiring not so great
    programmers, and I would love to hear the boards direction... Luckily I
    only have stock in Microsoft on the India exchange (NO! I am just
    kidding. I do not own stock).

    They do have a new news channel on the TV, it is called MSNOW. I am sure
    this channel will scare us into more of their safety concepts :)

    I can go on and on about this. Microsoft pioneered the concept that
    software should be bought only if it is broken. What ever happened to
    SEARS?

    visio, visual basic v6, msstudio 2005, mp3, dvd, microsoft publisher;
    just to name a few. I got really pissed off when fontographer was not
    permitted to run. They kept a black list of programs that they could
    sink. dunno how they make money...

    Because if you go to the website, the link to the downloadable
    software disappears off into the ether.

    just like microsofts help system.

    Feel free to prove me wrong. But somehow I donrCOt think you would know
    where to start.

    Yes, microsoft makes lots of money by scaring people into thinking that microsoft can fix the problem (the problem that they create of course).

    Of course, you could always regurgitate some AI slop, if you think it
    will help ...

    I already brought up the damn talking paper clip help system from the
    90s :)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Mon Aug 10 21:18:36 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    On Wed, 5 Aug 2026 22:00:45 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    If garbage collection is so good, why donrCOt high-performance
    operating system kernels use it? Why do they prefer
    reference-counting instead?

    to be a high performance kernel you should not need to do garbage
    collection.

    But isnrCOt that supposed to be better than reference-counting? Offering higher performance or something?

    you must be kidding me. GC is always been considered slow.


    GC is for user space, not kernel space. Kernel developers are
    usually very good programmers.

    Do different laws of physics apply in kernel space or something?

    Yes they do. It is like radio circuits; Take ohms law and throw it out.

    And/or is that an admission that garbage collection is not for rCLvery
    good programmersrCY?

    Most programmers that are talented enough to write a kernel can probably
    handle malloc and free. That is why they don't use them.

    People who are not interested in maximum speed would probably have no
    problem with using a GC. Reference counting is not unholy - it is like
    using a goto statement.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Mon Aug 10 21:25:16 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:


    And by the way some of my complains can also be exactly applied to
    Common Lisp. For instance, I think Common Lisp doesn't have the
    semantics of POSIX's read(2). I suppose there are libraries out there
    that might go lower level (than Common Lisp's) and then give you an abstraction that mimics read(2), but that's beside the point.

    In common lisp your can link to C; like visual basic 6. SBCL has
    sb-posix:write already built in. it is the POSIX one, not the cl:write.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Tue Aug 11 11:19:08 2026
    From Newsgroup: comp.lang.lisp


    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are usually very good programmers.

    Do different laws of physics apply in kernel space or something?
    And/or is that an admission that garbage collection is not for rCLvery
    good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, decision making should be and mostly is (absent resource constraints) guided by what is right for the patient. (This sounds obvious but it does need to be re-emphasised and re-emphasised as part of training, because it is not always intuitive in the details of every decision made. Every six year old who bumps his or her head should not have a CT brain, for example.) Now, you can obviously ask patients (or parents in that last example) what they feel would be right for the patient, and that is often helpful, but it is not the case that every patient has thought through every specific clinical situation before, and it is not the case that every patient has an informed command of the relevant research.

    In practice, you have to develop a mental picture of what is right for almost everyone. Practically no-one wants to die young (and if they do, practically none of their family members want them to die young, and practically no-one continues to want to die young once the twelve Buckfasts have worn off or their depression is treated). Practically everyone wants to continue to be able to walk. Practically everyone wants to continue to have control of their bowels and bladders. Practically no-one wants to have dementia. No-one wants to die of metastatic cancer. Frail people in their high eighties may not want colonoscopy if they have a change to their bowel habit with some blood in their stool, and, if they are unlikely to be fit for treatment of any bowel cancer that is found, that is very reasonable and it is not a good use of time to attempt to talk them round to the investigation.

    This becomes more important when the patient is not paying directly for their care (they are paying through their taxes, or they have health insurance), since the body that pays for the care is incentivised to minimise investigations and management. If you are employed directly by the body that pays for care part of the job is, often and effectively, to market the investigations and management as necessary to other people in the organisation.

    Digression ended.

    When I returned to software I found it helpful, by analogy to rCLwhat is right for the patientrCY above, to consider what is right for the end user.

    If there were no resource constraints, a fully informed user aware of what is possible would like bug-free software that does exactly what is desired as quickly as the hardware can do it.

    This would require essentially assembler written with the quality of the Apollo code, without an operating system. (IrCOm sure everyone reading this accepts that
    good assembler, if it has no bugs, is going to make better use of the hardware than their language of choice.) This is not going to happen, because we have resource constraints; no-one is going to pay for that. But itrCOs helpful to keep it in mind as a possibility.

    Operating systems, virtual memory, and non-assembler languages are all examples of tools that make programming less demanding and less likely to have bugs. This means that the cost (in time and often in money) of developing software to do a given thing goes down. Portable non-assembler languages have the additional advantage that the development time can be amortised over multiple generations of hardware, reducing the cost further.

    The trade-off is that the resulting software is slower than the above ideal, and, e.g. that my Windows install decides that it is going to update whether I like it or not and the Cygwin terminal that I had open, in the middle of debugging something, with a command history that I would ideally like to have kept, evaporates.

    The question just becomes what point in the trade-off of increasing development time versus decreasing does-exactly-what-I-want-making-best-use-of-the-hardware a given piece of software should make.

    For me, garbage collection as it is actually implemented (I would phrase this -+real existierende Garbage-Collection-2 in German, by analogy with -+real existierender Sozialismus) has a non-negligible runtime cost. This is usually acceptable but sometimes not.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Tue Aug 11 10:00:43 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are usually very good programmers.

    Do different laws of physics apply in kernel space or something?
    And/or is that an admission that garbage collection is not for rCLvery good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, [...]

    Very cool that we have people from areas such as medicine here. (In
    reality, there's no academic discipline called programming---people in
    Computer Science are more often than not not programmers at all.)
    Medicine, in particular, is an unexpected one. Can you share a bit more
    about your history as in how did you get interested in medicine and
    computers (and Lisp specially)? That'd be cool to hear. (Assuming a
    little social chat is acceptable here given the current low volume.)

    This would require essentially assembler written with the quality of
    the Apollo code, without an operating system. (IrCOm sure everyone
    reading this accepts that good assembler, if it has no bugs, is going
    to make better use of the hardware than their language of choice.)

    Perfectly reasonable.

    The trade-off is that the resulting software is slower than the above
    ideal, and, e.g. that my Windows install decides that it is going to
    update whether I like it or not and the Cygwin terminal that I had
    open, in the middle of debugging something, with a command history
    that I would ideally like to have kept, evaporates.

    Isn't that irritating? Windows is a system that's really not very
    respectful at all with what the user is doing---lots of interruptions
    such as alerts by Windows Defender and whatnot. Many other programmers
    on Windows follow suit, so it's not Microsoft's fault completely. And
    that might be the same thing in the usual GNU system these days. For
    window management, I run CWM, which is one that really only lets
    anything happen that the user has actively made it happen.

    And speaking of Medicine, how is it disrespectful these days as well,
    but I won't digress on this (and it's perhaps just something that
    plagues the entirety of society).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.lang.lisp,comp.lang.c on Tue Aug 11 14:29:47 2026
    From Newsgroup: comp.lang.lisp

    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> writes:
    On Mon, 10 Aug 2026 17:41:30 -0300, Anton Antimo wrote:

    For select (called unix-fast-select in SBCL), see sb-unix.

    select(2) is considered an archaic way of doing things these days,
    because of its ABI limitations. The modern way is poll() ><https://manpages.debian.org/poll(2)> (POSIX) or even epoll() ><https://manpages.debian.org/epoll(7)> (Linux-specific).

    Both poll(2) and select(2) are fully supported POSIX interfaces.

    select derives from BSD, poll derives from System V.

    There are issues with select (due to the defintion of fd_set)
    that make it unsuitable for certain applications (such as those
    that use file descriptors greater than FD_SETSIZE).

    https://pubs.opengroup.org/onlinepubs/9699919799/functions/select.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/poll.html
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Tue Aug 11 11:38:21 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 09 Aug 2026 18:47:01 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:

    tfb <tfb@work.it.out> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    I think he (it?) may well *be* an LLM.


    I was asked a psychiatrist what an LLM is. Large Language Model makes no >sense. What is behind this LLM, neural nets? I was thkng that semantic
    nets. How do I go about writing an LLM, no I do not want to use one; I
    want to write one (list is comp.lang.lisp afterall).

    An LLM is an emulation of a neural net. There's plenty of study
    material regarding neural nets.


    Modern implementations forgo the traditional graph representation and
    instead are based on matrix math. Ie. you take a bunch of inputs,
    multiply each input by a weight, offset the result by adding some
    value, then summ and pass the summ put through a (possibly per node)
    equation to get an output. That ptoentially feeds into the inputs of
    the next layer of nodes.

    The difficulty is in getting the topology correct. Too many nodes,
    the nodes start to specialize, too few nodes the results are fuzzy.
    Bad connection scheme - either it doesn't work or training becomes
    very difficult. NNs have been studied since the 1970s, and there are
    known topologies to create various kinds of recognizers and types of
    (app specific) memories. You can (sort of) plug and play using these
    as modules. But still a lot of it is just trial and error. That's why
    so much effort is needed to build them.


    LLMs [I agree it's a stupid name] are hidden node models having tens
    of thousands (or more) of nodes, and many millions of inputs [and
    weights and offsets]. You can't build one without a supercomputer.

    There's a PHd and potential billions of $$$ waiting if you can figure
    out how to make a NN reliably forget something it has learned, without retraining from scratch and without affecting anything else it knows.


    Have fun!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Tue Aug 11 11:45:17 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 09 Aug 2026 19:12:49 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:

    George Neuner <gneuner2@comcast.net> writes:

    To be fair, you need to understand that Racket is multi-platform,
    needs to run on Windows, and Windows [for the most part] does not
    implement POSIX functions.

    Can you use CYGwin? it is a bit ugly but it is POSIX. Microsoft should
    be able to introduce a POSIX level (xyz) rather easily; they just don't
    do that. It's like the Xterminal.

    I'm not aware that Racket can run over Cygwin. If it can, I would bet
    that GUI/graphical programs won't work.

    Certainly you can create an interface to Cygwin and use it directly.
    [You can do this with pretty much any library.]


    dunno, I cannot use windows 11; it needs a credit card. God bless the
    Free Software Project!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Tue Aug 11 12:20:00 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 10 Aug 2026 10:48:48 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    George Neuner <gneuner2@comcast.net> writes:

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    How about the [Racket] macro system? So perfect, yet so annoying.
    One thing I love about Common Lisp is precisely macro's (lack of) >>>hygiene. I'm totally fine with complete guarantee. Anaphoric
    macros are so useful. (No idea how to implement them in Racket >>>---impossible?)

    Racket has its roots in Scheme. Scheme is defined in terms of source
    /text/ rather than the compiler's AST. So there is no real equivalent
    of Lisp's AST macros.

    Interesting. I bet this has been one my major difficulties because I had >never quite understood that and I probably still don't. I had realized
    I always needed to manipulate the syntax objects as opposed to sexps and
    it was always confusing to insert a new identifier into the generating
    code and so on. The blame is of course always on me, but >yeah---difficult-to-understand stuff. Common Lisp is a lot simpler, I
    feel. (Let me also say that I was never able to understand Scheme
    compilers' error messages, Racket included.)

    Is there an article out there that elaborate your paragraph here? I'd
    like to learn more about these differences. I suppose the Scheme people >would have very strong arguments to go their way.


    It is implicit in the semantics sections of the R_RS documents. Might
    be explicit in some of them, I don't recall - the earlier documents
    tended to contain more detail about intent, but I haven't (re)read any
    of them in ages. I'm sure I've seen it explicitly stated somewhere,
    but it may have been in some book.
    [One of my college professors was Mitchell Wand who co-wrote
    "Essentials of Programming Languages" and served on the Scheme
    defining committee for many years.]

    TLDR; Scheme's formal semantics are based on the syntax of forms in
    the /external/ representation - ie. the source text - not on any
    compiler's internal representation.


    Also Racket itself technically is not a Scheme, although it evolved
    from (PLT) Scheme, has many similarities to Scheme, and easily can
    emulate Scheme. The current distribution includes an interworking
    emulation of R6RS.


    That said, Racket does support Lisp-like unhygienic macros with
    'define-macro'. Apologies for the ridiculous length of the URL.

    https://docs.racket-lang.org/compatibility/defmacro.html#%28form._%28%28lib._compatibility%2Fdefmacro..rkt%29._define-macro%29%29

    We need a project that can promise to shorten and maintain URLs for 50
    years, say. (I say fifty so a single hacker can keep it running during
    his lifetime. After 50 years, a young hacker takes it on for another
    50.) It'a pity that Google Inc. let us down with goo.gl.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Tue Aug 11 18:31:24 2026
    From Newsgroup: comp.lang.lisp


    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh Anton Antimo:

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are usually very good programmers.

    Do different laws of physics apply in kernel space or something? And/or is that an admission that garbage collection is not for rCLvery good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, [...]

    Very cool that we have people from areas such as medicine here. (In reality, there's no academic discipline called programming---people in Computer Science are more often than not not programmers at all.) Medicine, in particular, is an unexpected one. Can you share a bit more about your history as in how did you get interested in medicine and computers (and Lisp specially)? That'd be cool to hear. (Assuming a little social chat is acceptable here given the current low volume.)

    My first degree was 1998-2002 and the professor (clearly taking shelter from the first AI winter) assigned the GNU Emacs manual as required reading for the first class. (This is, I understand, not typical.) At that point XEmacs was a better editor so after using GNU Emacs for a few weeks I switched to XEmacs. It still meets my needs and I have no plan to switch away from it.

    2002 was the Dot Com bust, and after six months unemployment following a 2.1 degree from the best university in my country, I ended up in technical support.
    To my surprise, I really enjoyed solving peoplerCOs problems then and there. Continued working in IT here in Europe (got out of technical support given it was clear that was moving to India, was in software development roles) realised I was not going to be able to comfortably raise a family in the roles I was doing.

    2007 my parents pointed me towards a new rCLGraduate Entry MedicinerCY course in
    Dublin, on the US model of requiring another degree but being only four years in length; I realised from the technical support experience that I would likely enjoy the day-to-day of this, and you can comfortably raise a family in medicine in Ireland.

    Studied medicine 2008-2012, worked like a demon 2013-2021, and am no longer at the point where I have to work and study relentlessly to make forward progress.
    Very happy with the job and with my day-to-day, and I finally have a bit of breathing space to be back on Usenet.

    If you use any emacs itrCOs hard to avoid Lisp. Emacs Lisp is not a paragon of good design nor of good implementation-- (aset (symbol-name nil) 0 ?\u0192) , (fillarray obarray 0) , anyone?--so the natural thing is to look around for something better. The consensus within XEmacs was that Common Lisp was better. On investigating, yes, it is. But, XEmacs needs work, no-one else is doing it, so my software work these days is C with a very Common-Lisp-oriented Emacs Lisp.

    This would require essentially assembler written with the quality of
    the Apollo code, without an operating system. (IrCOm sure everyone
    reading this accepts that good assembler, if it has no bugs, is going
    to make better use of the hardware than their language of choice.)

    Perfectly reasonable.

    The trade-off is that the resulting software is slower than the above ideal, and, e.g. that my Windows install decides that it is going to update whether I like it or not and the Cygwin terminal that I had
    open, in the middle of debugging something, with a command history
    that I would ideally like to have kept, evaporates.

    Isn't that irritating? Windows is a system that's really not very respectful at all with what the user is doing---lots of interruptions
    such as alerts by Windows Defender and whatnot. Many other programmers
    on Windows follow suit, so it's not Microsoft's fault completely. And
    that might be the same thing in the usual GNU system these days. For
    window management, I run CWM, which is one that really only lets
    anything happen that the user has actively made it happen.

    The comment wasnrCOt intended to be specifically about Windows, that just happened to be the most recent example that sprung to mind. All the common operating systems take time to boot, time which would ideally be spent doing what you, as the user, actually wish to do. Even resume-from-hibernation is not instant. All of the common operating systems update, often requiring a reboot, taking time which would ideally be spent doing what you, as the user, actually wish to do.

    Even if the update process is manual, e.g. when IrCOm using Debian and migrating
    a server to a new VM, I do not actually want to spend my time working out with trial and error what invocation of certbot will allow me to put Letsencrypt certificates on a new server that already has Apache installed. (Spoiler; spin down Apache, use certbot --certonly, which spins up its own HTTP server.)

    (I certainly donrCOt want to have to migrate well-written PHP of twenty years ago
    that carefully wrapped access to a database using then-best-practice APIs because those APIs are unmaintained and removed, but that is entirely on me, we all know PHP is terrible, and I knew it then. But Debian shouldnrCOt be terrible,
    and in the grand scheme of things it isnrCOt terrible.)

    There are reasons and many of them are good for these things. I donrCOt plan to switch my day-to-day to TempleOS. But that we have them is a trade off.

    And speaking of Medicine, how is it disrespectful these days as well,
    but I won't digress on this (and it's perhaps just something that
    plagues the entirety of society).

    What do you mean? Respect towards and from medicine varies by country. Doctors are regularly assaulted in India by family members of patients unhappy with the patientsrCO care. I get Christmas presents.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 11 18:35:58 2026
    From Newsgroup: comp.lang.lisp

    |------------------------------------------------------------------------------|
    |"If there were no resource constraints, a fully informed user aware of what is|
    |possible would like bug-free software that does exactly what is desired as |
    |quickly as the hardware can do it. |
    | |
    |[. . .] |
    |Operating systems, [. . .] are all examples |
    |of tools that make programming [. . .] less likely to have bugs." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in || Ceoth|inaigh ar an 11|| l|i de mh|! L||nasa 2026.

    Windows is buggy.

    |------------------------------------------------------------------------------|
    |"This means that the cost ([. . .] often in money) of developing software to |
    |do a given thing goes down. [. . .] |
    |[. . .] |
    | |
    |[. . .] |
    |[. . .] my Windows install decides that it is going to update whether I |
    |like it or not" |
    |------------------------------------------------------------------------------|
    arsa Aodh|in || Ciothaigh ar an 11|| l|i de mh|! L||nasa 2026.

    A license for Windows costs money.

    |------------------------------------------------------------------------------|
    |"and the Cygwin terminal that I had open, in the middle of |
    |debugging something, with a command history that I would ideally like to have |
    |kept, evaporates." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in mac Eochadha ar an 11|| l|i de mh|! L||nasa 2026.

    Is BASh on Windoze without its features on gratis operating systems?


    cat .bash_profile
    [. . .]

    unset HISTSIZE
    unset HISTFILESIZE
    mkdir -p ~/backed_up_shell_histories
    cp $HISTFILE ~/"backed_up_shell_histories/bash_history_""`date --reference=$HISTFILE '+timestamped_%Y-%m-%d_%H:%M'`""_backed_up_by_Process"$$"_on_""`date '+%Y-%m-%d_%H:%M'`"
    HISTTIMEFORMAT="%s"

    [. . .]

    shopt -s histappend
    PROMPT_COMMAND='history -a'

    [. . .]



    info bash
    [. . .]

    [. . .]

    'PROMPT_COMMAND'
    If this variable is set, and is an array, the value of each set
    element is interpreted as a command to execute before printing the
    primary prompt ('$PS1'). If this is set but not an array variable,
    its value is used as a command to execute instead.

    [. . .]

    'history'
    history [N]
    history -c
    history -d OFFSET
    history -d START-END
    history [-anrw] [FILENAME]
    history -ps ARG

    With no options, display the history list with line numbers. Lines
    prefixed with a '*' have been modified. An argument of N lists
    only the last N lines. If the shell variable 'HISTTIMEFORMAT' is
    set and not null, it is used as a format string for STRFTIME to
    display the time stamp associated with each displayed history
    entry. No intervening blank is printed between the formatted time
    stamp and the history line.

    Options, if supplied, have the following meanings:

    [. . .]

    '-a'
    Append the new history lines to the history file. These are
    history lines entered since the beginning of the current Bash
    session, but not already appended to the history file.


    ls backed_up_shell_histories/bash_history_timestamped_2023* | wc --lines
    1897

    ls backed_up_shell_histories/bash_history_timestamped_2024* | wc --lines
    2658

    ls backed_up_shell_histories/bash_history_timestamped_2025* | wc --lines
    2963

    wc --bytes backed_up_shell_histories/bash_history_timestamped_2023*
    [. . .]
    48862565 total

    wc --bytes backed_up_shell_histories/bash_history_timestamped_2024*
    [. . .]
    74706247 total

    wc --bytes backed_up_shell_histories/bash_history_timestamped_2025*
    [. . .]
    87638922 total


    Is mise le meas,
    Niocl|iis|!n C||il|!n Glost|-ir
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 11 19:35:58 2026
    From Newsgroup: comp.lang.lisp

    |--------------------------------------------------------|
    |"degree from the best university in my country, [. . .]"| |--------------------------------------------------------|
    arsa Aodh|in ua Ciothaigh ar an 11|| l|i de mh|! L||nasa 2026.

    Chan in |eirinn d'ollscoil ar bith!

    Is mise le meas,
    Niocl|is P||l Caile|in de Ghloucester
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Tue Aug 11 20:56:01 2026
    From Newsgroup: comp.lang.lisp


    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh C||il|!n Niocl|is|!n Glost|-ir:

    |--------------------------------------------------------|
    |"degree from the best university in my country, [. . .]"| |--------------------------------------------------------|
    arsa Aodh|in ua Ciothaigh ar an 11|| l|i de mh|! L||nasa 2026.

    Chan in |eirinn d'ollscoil ar bith!

    Hmm? The University of Dublin, founded 1592 by Queen Elizabeth as Trinity College Dublin, four Nobel laureates, alumni including Samuel Beckett,
    Oscar Wilde, Denis Burkitt of BurkittrCOs lymphoma is not a university? Where did
    you study, G||ttingen? Heidelberg? Padua?
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Tue Aug 11 21:14:46 2026
    From Newsgroup: comp.lang.lisp


    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh C||il|!n Niocl|is|!n Glost|-ir:

    |------------------------------------------------------------------------------|
    |"If there were no resource constraints, a fully informed user aware of what is|
    |possible would like bug-free software that does exactly what is desired as |
    |quickly as the hardware can do it. |
    | |
    |[. . .] |
    |Operating systems, [. . .] are all examples |
    |of tools that make programming [. . .] less likely to have bugs." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in || Ceoth|inaigh ar an 11|| l|i de mh|! L||nasa 2026.

    Windows is buggy.

    T|i a fhios agam.

    |------------------------------------------------------------------------------|
    |"This means that the cost ([. . .] often in money) of developing software to |
    |do a given thing goes down. [. . .] |
    |[. . .] |
    | |
    |[. . .] |
    |[. . .] my Windows install decides that it is going to update whether I |
    |like it or not" |
    |------------------------------------------------------------------------------|
    arsa Aodh|in || Ciothaigh ar an 11|| l|i de mh|! L||nasa 2026.

    A license for Windows costs money.

    T|i a fhios agam. Bh|!os ag scr|!obh go ginear|ilta. T|i fadhbanna ag Linux, ag OpenBSD; n|!l aon gh|i le airgead chun OpenBSD a us|iid.

    |------------------------------------------------------------------------------|
    |"and the Cygwin terminal that I had open, in the middle of |
    |debugging something, with a command history that I would ideally like to have |
    |kept, evaporates." |
    |------------------------------------------------------------------------------|
    arsa Aodh|in mac Eochadha ar an 11|| l|i de mh|! L||nasa 2026.

    Is BASh on Windoze without its features on gratis operating systems?

    If I am going to configure my Cygwin environment I will install zsh and turn on its history. ThatrCOs more work, beyond what I actually currently want to do with the computer; thank you for supporting my point.

    I notice you got the leagan Gaeilge of my surname completely wrong on first and second attempts and then the thirdq attempt was much closer to the actuality. Are you by any chance writing your posts using a large language model?

    Is mise le meas,
    Niocl|iis|!n C||il|!n Glost|-ir
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.lang.lisp on Tue Aug 11 20:20:47 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-10, Paul Rubin <no.email@nospam.invalid> wrote:
    tfb <tfb@work.it.out> writes:
    It is so weird that people use a language whose defining feature is
    the incremental construction of languages and then say they don't use
    that feature. I mean, I'm aware people do that, but it's just so
    fucking weird.

    For a long time, Scheme didn't have macros, but it was still considered
    cool.

    Lisp macros are generally a way for user code to get hold of unevaluated
    args in a sexp. If your language has lazy evaluation (Haskell) and/or syntactic support for your likely macro use cases (lots of languages),
    macros become less important.

    Suppressing evaluation is not the same thing as delaying evaluation.
    Macfros suppress evaluation so that the expression can be given an
    arbitrary meaning. One such meaning could be that evaluation is delayed,
    e.g. classic (delay <form>) macro, returning a promise. That's only a
    small point in a large universe.

    As Lispers like to say, syntax is no big
    deal. So why obsess about being able to redefine it?

    "Syntax is no big deal" means that in Lisp we drop most of the /bike
    shedding/ about how to design syntax, not that we don't want syntax.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 11 20:21:27 2026
    From Newsgroup: comp.lang.lisp

    |-------------------------------------------------------------------------|
    |" Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh C||il|!n Niocl|is|!n Glost|-ir: |
    | |
    | > |--------------------------------------------------------| |
    | > |"degree from the best university in my country, [. . .]"| |
    | > |--------------------------------------------------------| |
    | > arsa Aodh|in ua Ciothaigh ar an 11|| l|i de mh|! L||nasa 2026. |
    | > |
    | > Chan in |eirinn d'ollscoil ar bith! |
    | | |Hmm? The University of Dublin, founded 1592 by Queen Elizabeth as Trinity| |College Dublin, four Nobel laureates, alumni including Samuel Beckett, | |Oscar Wilde, Denis Burkitt of BurkittrCOs lymphoma is not a university?" | |-------------------------------------------------------------------------| arsa Aodh P||l ua Ceoth|inaigh.

    Dar liom!

    |-------------------------------------------------------------------------| |"Where did | |you study[. . .]?" | |-------------------------------------------------------------------------| arsa Aodh|in ua Ciothaigh.

    Le deirfi||r daoibh.

    Is mise le meas,
    Niocl|is|in Caile|in Glost|-ir
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 11 21:01:23 2026
    From Newsgroup: comp.lang.lisp

    |-------------------------------------------------------------------------------|
    |" Ar an t-aon|| l|i d|-ag" |
    |-------------------------------------------------------------------------------|
    arsa tusa ar an aon|| l|| dh|-ag den mh|! so. (So is not a misspelling of seo.)

    |-------------------------------------------------------------------------------|
    |" de m|! L||nasa, scr|!obh C||il|!n Niocl|is|!n Glost|-ir:" |
    |-------------------------------------------------------------------------------|
    arsa tusa i rith lae de mh|!.

    Aidan Kehoe <kehoea@Parhasard.net> wrote: |-------------------------------------------------------------------------------|
    |"[. . .] T|i fadhbanna ag Linux, ag |
    |OpenBSD; [. . .]" |
    |-------------------------------------------------------------------------------|

    B|!onn ceart agat.

    |--------------------------------------------------------------------------------|
    |"I notice you got the leagan Gaeilge of my surname completely wrong on first and|
    |second attempts [. . .]" |
    |--------------------------------------------------------------------------------|

    Wieso?

    |-------------------------------------------------------------------------------|
    |"Are you by any chance writing your posts using a large language model?" |
    |-------------------------------------------------------------------------------|

    Nein. However, the most recent (almost finished but still unfinished) refereeing by me is for a typescript whose name includes "LLMs".

    Is mise le meas,
    Niocl|is P||l Caile|in de Gloucester
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Tue Aug 11 22:44:49 2026
    From Newsgroup: comp.lang.lisp


    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh C||il|!n Niocl|is|!n Glost|-ir:

    |Hmm? The University of Dublin, founded 1592 by Queen Elizabeth as Trinity| |College Dublin, four Nobel laureates, alumni including Samuel Beckett, | |Oscar Wilde, Denis Burkitt of BurkittrCOs lymphoma is not a university?" |
    |-------------------------------------------------------------------------| arsa Aodh P||l ua Ceoth|inaigh.

    Dar liom!

    |-------------------------------------------------------------------------| |"Where did | |you study[. . .]?" | |-------------------------------------------------------------------------| arsa Aodh|in ua Ciothaigh.

    Le deirfi||r daoibh.

    Is mise le meas,

    N|!l mor|in meas le l|-amh sa teachtaireacht sin.

    To be clear, for anyone else reading this; if yourCOre going to write to me in Irish and choose to use the Irish version of my name, the Irish version of my name is Aodh|in Mac Eochaidh. Use that. Or use the English version, I donrCOt care, but get one of them right, and stick with that. Nick has been varying the spelling of my surname with each paragraph of each posting, after I made it clear to him that he was doing this.

    In his not particularly humble opinion, one of the universities I attended, details already given, is not a university. He is unwilling to give a useful answer to what university he went to in order to clarify if, in fact, he went to Heidelberg, or G||ttingen, or Padua, or theoretically Stanford, UChicago, Oxford, McMaster, UToronto, where I could seem some argument for a superiority complex. (Three months ago I would have accepted Cambridge in that, but I have recently been very entertained by the saga of Dr Jason Arday.)

    rCLIs mise le meas,rCY is a standard closing to letters in Irish, rCLI am, with respect [to you, the adressee],rCY the undersigned. I donrCOt see much respect in
    that message. I donrCOt plan to respond to Nick beyond this.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kaz Kylheku@046-301-5902@kylheku.com to comp.lang.lisp on Tue Aug 11 22:14:09 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-10, Andreas Eder <a_eder_muc@web.de> wrote:
    On So 09 Aug 2026 at 05:26, Johann 'Myrkraverk' Oskarsson wrote:
    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.

    That us exactly where it should be used - when there is no other way.

    I don't agree, because that amounts to macros never being used.

    It's never the case that there is no other way, because in place of
    any macro, you can write the expansion by hand.

    Macros should be used when it's better to use them than not.
    It makes the code easier to write, read, maintain.
    That's it.

    When you use CLOS and functions, you are using macros; your program
    is free of macro definitions because you are using ones that
    were provided like defclass and defmethod.

    Macros allowed that CLOS stuff to be developd more like a software project---people experimenting with and iterating on implementations
    of an object system---rather than a committee; though of course
    there was that too.
    --
    TXR Programming Language: http://nongnu.org/txr
    Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
    Mastodon: @Kazinator@mstdn.ca
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Tue Aug 11 22:50:15 2026
    From Newsgroup: comp.lang.lisp

    Sorry.

    I believe that no university exists in Ireland. I have the misfortune
    to be a graduate of an Irish fake university.

    No "university" which I used to go to is a real university. I used to
    be enrolled at or be employed at 5 fake universities in 4
    countries. Aidan Kehoe is a graduate of a more prestigous purported
    university (namely Dublin University) than I am a graduate
    of. Lecturer Micheal mac an Airchinnigh of an elite purported
    university of which Aidan Kehoe is a graduate lamented to me about
    lecturing with ProLog instead of a language which Micheal mac an
    Airchinnigh prefers.

    A different employee from that purported university used not
    understand English Word "sycophantic", so she asked me what does
    "sycophantic" mean. That different employee used to work under a
    different highly ranked scientist from the same purported university,
    who expressed ignorance of front-page news which she caused.

    That racist purported university made migrant Doctor Gerald Morgan
    homeless because he is a better English professor than a person of
    Aidan Kehoe's nationality.

    Cf.
    HTTPS://TrinityNews.Ie/2008/10/morgan-facing-potential-eviction
    and this email by Doctor Morgan reproduced by the
    Defending-Academic-Freedom LISTSERV ( HTTPS://WWW.JISCMail.ac.UK/cgi-bin/wa.exe?A0=defending-academic-freedom
    ):

    "Please confirm receipt of this email. As you know, in addition to
    banning me from giving lectures and seminars and launching books in
    College, cancelling at short notice my introduction to the showing of Casablanca on 14 April 2016, returning my post to sender even though
    the College itself has made me homeless, Dublin University (TCD) is
    also interfering in my work (and hence also in the work of the Centre
    of Medieval and Renaissance Studies) by blocking (with what legality,
    I am bound to wonder) emails to former colleagues with email addresses
    in College.

    Hence I ask you to confirm receipt of this email.

    I remind you that the College owes me an apology for the systematic
    violation of my rights as a Fellow since 7 October 2002 and another
    apology for the false allegation of the physical intimidation and
    harassment of a female colleague in the School of English on 6 October
    2002 accompanied by an immediate suspension and ban.

    If there was intimidation of any kind it was intimidation by sheer
    intellectual brilliance, as Carl Schmidt himself intimidated poor
    Denis Bethell (a brilliant medieval historian in hisown right) at UCD
    and CliftonTerrace, Monkstown, in 1969.

    In some ways Trinity College Dublin (78 or 160 in the World-|s
    rankings, way beneath the standard I have aways been accustomed to
    since I entered Jesus College, like Lawrence of Arabia and Harold
    Wilson, as a Meyricke Exhibitioner in 1961) reminds me of English
    referees in banning Danny Simpson [. . .]

    Or perhaps TCD will remind you of the South Yorkshire Police in a
    persistent and intransigent distaste for the truth. -|Truth-| is a philosophically profound matter,of course. What is truth when it comes
    to distinguishing between the incompetent police opening the
    floodgates and the Liverpool supporters climbing over a closed
    barrier?

    As it is I am only at halftime in the 27 year progress to -|truth and justice-|. That is, 13 and a half years,almost precisely, since I was
    suspended and banned without prior interview on 7 October 2002.

    Finally, may I thank you for your work as General Editor in making
    possible the publication of this book in honour of a great scholar at
    a great College (Balliol College, Oxford).

    Very best wishes, Gerald Morgan, FTCD (English Parliamentary Party, 2001)

    England-|s greatest Chaucer scholar from Central (not Upper or Lower) Lydbrook.

    Dr Gerald Morgan, FTCD (1993)
    Lydbrook School (1946-1953),
    Monmouth School (1953-1961),
    Meyricke Exhibitioner, Jesus College, Oxford (1961-1964),
    The Chaucer Hub."

    One can give more examples about that Irish fake university.

    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 07:51:39 2026
    From Newsgroup: comp.lang.lisp

    On 11/08/2026 7:53 AM, Lawrence DrCOOliveiro wrote:
    On Mon, 10 Aug 2026 17:41:30 -0300, Anton Antimo wrote:

    For select (called unix-fast-select in SBCL), see sb-unix.

    select(2) is considered an archaic way of doing things these days,
    because of its ABI limitations. The modern way is poll() <https://manpages.debian.org/poll(2)> (POSIX) or even epoll() <https://manpages.debian.org/epoll(7)> (Linux-specific).

    Dear Lawrence,

    You really don't keep up with the times. The /modern/ way to do this
    is to install FreeBSD over whatever other Unix you may have installed,
    and I suspect it's still S.C.O. UnixWare for you, and then use kqueues.

    https://man.freebsd.org/cgi/man.cgi?kqueue

    On the other hand, if you insist on using the illuminated operating sys-
    stem without cross porting the kqueue mechanism, there's always the port
    API.

    https://www.illumos.org/man/3C/port_create


    Happy queuing!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 07:59:49 2026
    From Newsgroup: comp.lang.lisp

    On 11/08/2026 4:41 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket
    on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket
    maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.
    Sounds very Java-like. Though perhaps not as irritating as Java.
    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.


    I admit I'm not sure why the select system call seems to be missing from
    this selection of networking functions, [...]

    It would be like writing C in Lisp notation. For select (called unix-fast-select in SBCL), see sb-unix.

    (defun wait-for-stdin-select ()
    (sb-alien:with-alien ((read-fds (sb-alien:struct sb-unix:fd-set)))
    (sb-unix:fd-zero read-fds)
    (sb-unix:fd-set 0 read-fds)
    (format t "Waiting up to 5 seconds for input on stdin... Type something!~%")
    (force-output)
    (multiple-value-bind (count err)
    (sb-unix:unix-fast-select 1 (sb-alien:addr read-fds) nil nil 5 0)
    (cond
    ((null count)
    (format t "Select failed with errno: ~A~%" err))
    ((zerop count)
    (format t "Timeout! No input received.~%"))
    ((sb-unix:fd-isset 0 read-fds)
    (format t "Data is ready to be read from stdin!~%"))
    (t
    (format t "Something else woke up select!~%"))))))

    ;; run it
    (wait-for-stdin-select)

    Thank you. This is indeed helpful. Unhelpfully, Lawrence is always
    talking about some sort of select in Python, and then talks about
    polling in Linux, when he knows we don't care about the Linux kernel
    here in comp.lang.lisp, because the Steel Banks Common Lisp encapsulates
    the kernel for us.

    I also admit to just using the two or three available socket libraries
    in QuickLisp, whenever I need to deal with raw sockets. I once imple-
    mented a D.N.S. server -- or service -- in Common Lisp, that replied un- helpfully with an error message to every query, as a practice in the
    D.N.S. protocol. I'm not sure if that source code is still public.

    You can trivially make your own, if you need the D.N.S. protocol in
    Common Lisp.

    That code was then adopted and the D.N.S. protocol removed, to do some-
    thing with raw U.D.P. datagrams. That is the beauty of sharing source
    code; one never knows what other people do with it.

    And no, I don't know why Lawrence is always pretending to be a Python influencer here in comp.lang.lisp. I hope he's getting paid for it.


    Happy network coding in Common Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 12 01:20:35 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 11 Aug 2026 18:35:58 -0000 (UTC), C||il|!n Niocl|is|!n Glost|-ir wrote:

    Is BASh on Windoze without its features on gratis operating systems?

    ItrCOs not about gratis, itrCOs about libre.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 12 01:19:28 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 11 Aug 2026 11:19:08 +0100, Aidan Kehoe wrote:

    This would require essentially assembler written with the quality of
    the Apollo code, without an operating system.

    The Apollo code *did* have an operating system. And remember, it
    crashed twice during the Apollo 11 landing. And got very confused by
    that lightning strike during the Apollo 12 launch.

    For me, garbage collection as it is actually implemented (I would
    phrase this -+real existierende Garbage-Collection-2 in German, by
    analogy with -+real existierender Sozialismus) has a non-negligible
    runtime cost. This is usually acceptable but sometimes not.

    My point exactly. And that cost is greater than that for
    reference-counting, for reasons I have already mentioned. Which is why
    Python and Perl prefer to use reference-counting as a first resort,
    only falling back to garbage collection when there is actual garbage
    to be collected.

    Some stubborn people keep refusing to accept this point.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 12 01:35:24 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 11 Aug 2026 18:31:24 +0100, Aidan Kehoe wrote:

    If you use any emacs itrCOs hard to avoid Lisp. Emacs Lisp is not a
    paragon of good design nor of good implementation-- (aset
    (symbol-name nil) 0 ?\u0192) , (fillarray obarray 0) , anyone?--so
    the natural thing is to look around for something better. The
    consensus within XEmacs was that Common Lisp was better. On
    investigating, yes, it is.

    ItrCOs a museum-worthy spec. Needs updating to, at least support POSIX-type features that we take for granted nowadays.

    Even if the update process is manual, e.g. when IrCOm using Debian and migrating a server to a new VM, I do not actually want to spend my
    time working out with trial and error what invocation of certbot
    will allow me to put Letsencrypt certificates on a new server that
    already has Apache installed. (Spoiler; spin down Apache, use
    certbot --certonly, which spins up its own HTTP server.)

    But you need to be able to keep the certs up to date without having to
    shut down Apache (or whatever web server yourCOre using) each time.

    Trust the standard Debian packages to take care of this automatically.

    (I certainly donrCOt want to have to migrate well-written PHP of
    twenty years ago that carefully wrapped access to a database using then-best-practice APIs because those APIs are unmaintained and
    removed, but that is entirely on me, we all know PHP is terrible,
    and I knew it then.

    I have never developed any web app from scratch in PHP. The only time
    IrCOve used it is to maintain existing code, or write plugins for
    existing code (WordPress, WooCommerce).

    As a language, its features read like a shopping list of sadness.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 11 23:30:53 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are usually very good programmers.

    Do different laws of physics apply in kernel space or something?
    And/or is that an admission that garbage collection is not for rCLvery good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, decision making should be and mostly is (absent resource constraints) guided by what is right for the patient.

    thank you for your service.

    (This sounds obvious but it does need to be re-emphasised and
    re-emphasised as part of training, because it is not always intuitive
    in the details of every decision made. Every six year old who bumps
    his or her head should not have a CT brain, for example.) Now, you can obviously ask patients (or parents in that last example) what they
    feel would be right for the patient, and that is often helpful, but it
    is not the case that every patient has thought through every specific clinical situation before, and it is not the case that every patient
    has an informed command of the relevant research.

    Oh another doctor that has to mention a CT scan. I slipped last winter
    and hit the back of my head. They took like 10 CT scans over time. They couldn't believe that I was still able to walk. I should mention I weigh
    200 pounds and am 5'7" .

    I believe the purpose of a doctor is to meet the patient at their
    current level of the disease process. At first I was squirting blood all
    over the place. So I cortorized the wound by placing my head in snow;
    while waiting for the ambulance.

    Once they stapled my head back together they started the CT scans. Point
    is CT scans before staples is not a good idea.

    In practice, you have to develop a mental picture of what is right for almost everyone. Practically no-one wants to die young (and if they do, practically none of their family members want them to die young, and practically no-one continues to want to die young once the twelve Buckfasts have worn off or their
    depression is treated). Practically everyone wants to continue to be able to walk. Practically everyone wants to continue to have control of their bowels and bladders. Practically no-one wants to have dementia. No-one wants to die of
    metastatic cancer. Frail people in their high eighties may not want colonoscopy
    if they have a change to their bowel habit with some blood in their stool, and,
    if they are unlikely to be fit for treatment of any bowel cancer that is found,
    that is very reasonable and it is not a good use of time to attempt to talk them round to the investigation.

    we may have a difference of things. It is much easier to lose a child
    then to lose a teenager. Not to mention they are easier to target.
    Memory is a bitch.

    This becomes more important when the patient is not paying directly for their care (they are paying through their taxes, or they have health insurance), since the body that pays for the care is incentivised to minimise investigations and management. If you are employed directly by the body that pays for care part of the job is, often and effectively, to market the investigations and management as necessary to other people in the organisation.

    sadly this is so true in the USA. I live in New Jersey, "The welfare state".

    Digression ended.

    When I returned to software I found it helpful, by analogy to rCLwhat is right
    for the patientrCY above, to consider what is right for the end user.

    yes transference is a bitch.

    If there were no resource constraints, a fully informed user aware of what is possible would like bug-free software that does exactly what is desired as quickly as the hardware can do it.

    In mycology (did I mention I am a bit goofy :) they call it senescence.

    This would require essentially assembler written with the quality of the Apollo
    code, without an operating system. (IrCOm sure everyone reading this accepts that
    good assembler, if it has no bugs, is going to make better use of the hardware
    than their language of choice.) This is not going to happen, because we have resource constraints; no-one is going to pay for that. But itrCOs helpful to keep it in mind as a possibility.

    they actually used a lot of wire wrapping. I've seen some pictures from
    the outside. It is fucking crazy.

    Operating systems, virtual memory, and non-assembler languages are all examples
    of tools that make programming less demanding and less likely to have bugs. This means that the cost (in time and often in money) of developing software to
    do a given thing goes down. Portable non-assembler languages have the additional advantage that the development time can be amortised over multiple generations of hardware, reducing the cost further.

    the business world has a mantra, The good programmers will eliminate
    their job, so you just hire 1000 monkeys to press the keyboard until one
    of them does it right.

    The trade-off is that the resulting software is slower than the above ideal, and, e.g. that my Windows install decides that it is going to update whether I
    like it or not and the Cygwin terminal that I had open, in the middle of debugging something, with a command history that I would ideally like to have kept, evaporates.

    That is assuming you give microsoft your credit card. God bless the free software movement. I am sure many people believe that stallman is crazy;
    he is sometimes very prophetic. I recommend reading his essay on the
    right to read. (it has been some time) He basically describes our (USA)
    current education crisis. The children are not taught to read/write cursive, nor read a clock! It is getting scary; when kids insist that a reality
    agent is zillow.

    The question just becomes what point in the trade-off of increasing development
    time versus decreasing does-exactly-what-I-want-making-best-use-of-the-hardware
    a given piece of software should make.

    For me, garbage collection as it is actually implemented (I would phrase this -+real existierende Garbage-Collection-2 in German, by analogy with -+real existierender Sozialismus) has a non-negligible runtime cost. This is usually acceptable but sometimes not.

    I leave you with this:

    ``Quantum Physics and Human Consciousness

    I don't think there's anything unique about human intelligence. We
    can someday replicate that on a machine.'' -

    Bill Gates in The Most Intriguing People of the Century, p. 101
    People Weekly, People Weekly Books, 1997''.

    I will stay away from my deviance Digression!

    what a plesant conversation. You just made my day a bit brighter and you
    did not even tell me to quit smoking cigarettes :)

    thanx doc.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 11 23:35:39 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are
    usually very good programmers.

    Do different laws of physics apply in kernel space or something?
    And/or is that an admission that garbage collection is not for rCLvery
    good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, [...]

    Very cool that we have people from areas such as medicine here. (In
    reality, there's no academic discipline called programming---people in Computer Science are more often than not not programmers at all.)
    Medicine, in particular, is an unexpected one. Can you share a bit more about your history as in how did you get interested in medicine and
    computers (and Lisp specially)? That'd be cool to hear. (Assuming a
    little social chat is acceptable here given the current low volume.)

    Yes, yes; I want to hear more from the doc!


    This would require essentially assembler written with the quality of
    the Apollo code, without an operating system. (IrCOm sure everyone
    reading this accepts that good assembler, if it has no bugs, is going
    to make better use of the hardware than their language of choice.)

    Perfectly reasonable.

    The trade-off is that the resulting software is slower than the above
    ideal, and, e.g. that my Windows install decides that it is going to
    update whether I like it or not and the Cygwin terminal that I had
    open, in the middle of debugging something, with a command history
    that I would ideally like to have kept, evaporates.

    Isn't that irritating? Windows is a system that's really not very
    respectful at all with what the user is doing---lots of interruptions
    such as alerts by Windows Defender and whatnot. Many other programmers
    on Windows follow suit, so it's not Microsoft's fault completely. And
    that might be the same thing in the usual GNU system these days. For
    window management, I run CWM, which is one that really only lets
    anything happen that the user has actively made it happen.

    And speaking of Medicine, how is it disrespectful these days as well,
    but I won't digress on this (and it's perhaps just something that
    plagues the entirety of society).

    The same way programming is, some people are more talented and more
    motivated to be the best person they can. Some people just don't give a
    shit - they have what we call an external locust of controll. They care
    about perception that science.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Tue Aug 11 20:39:34 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@parhasard.net> writes:
    once the twelve Buckfasts have worn off

    I had to look that up. Wow, that's the medicine we all need, lol.

    https://en.wikipedia.org/wiki/Buckfast_Tonic_Wine
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Tue Aug 11 20:51:21 2026
    From Newsgroup: comp.lang.lisp

    Kaz Kylheku <046-301-5902@kylheku.com> writes:
    Suppressing evaluation is not the same thing as delaying evaluation.

    Laziness can of course suppress evaluation. In Lisp you might have COND
    as a primitive and implement IF as a macro that turns into a COND.
    Haskell has pattern matching as a primitive. It has IF but doesn't
    really need it. You could implement IF like this:

    if' :: Bool -> a -> a
    if' condition val1 val2 = case condition of
    True -> val1
    False -> val2

    Evaluation of one of (val1, val2) is delayed, and the other is
    suppressed.

    The single quote (pronounced prime) being ok to use in identifiers is
    nothing special for Lispers, but it has always made me smile. It's
    intended for math-y names like x' or y', but it also means you can have function names like "isn't", "don't", and so on.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.c on Tue Aug 11 20:59:34 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    https://man.freebsd.org/cgi/man.cgi?kqueue

    Is this something like io_uring? Is it just for i/o on open fd's or can
    you also use it for stuff like opening files?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 13:07:53 2026
    From Newsgroup: comp.lang.lisp

    On 12/08/2026 11:59 AM, Paul Rubin wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    https://man.freebsd.org/cgi/man.cgi?kqueue

    Is this something like io_uring? Is it just for i/o on open fd's or can
    you also use it for stuff like opening files?

    I admit ignorance of how io_uring works. I haven't done low level code
    like this in Linux for a very long time, and I believe back then io_ur-
    ing didn't exist.

    The kqueue() is for open file descriptors, created as sockets or open
    files, or anything else the FreeBSD kernel decides is a file. I'm not
    aware of any interface to create one and open a file with the same func-
    tion call.


    Hope that helps!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 13:18:40 2026
    From Newsgroup: comp.lang.lisp

    On 09/08/2026 4:52 PM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.


    It is so weird that people use a language whose defining feature is the incremental construction of languages and then say they don't use that feature. I mean, I'm aware people do that, but it's just so fucking weird.


    No the subject of /weird/, I've also found it highly bizarre, if not
    outright disturbing, that people don't use do ... while(); in C. It's
    an eminently useful structured programming pattern.

    On the subject of Common Lisp, I find it more than disturbing when a
    codebase lacks the basic usage of hash tables.

    https://www.sbcl.org/manual/#hash-table-extensions


    Happy coding disturbing things!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan Bawden@alan@csail.mit.edu to comp.lang.lisp,comp.lang.c on Wed Aug 12 03:23:45 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 12/08/2026 11:59 AM, Paul Rubin wrote:
    Is this something like io_uring? Is it just for i/o on open fd's or can
    you also use it for stuff like opening files?
    The kqueue() is for open file descriptors, created as sockets or open
    files, or anything else the FreeBSD kernel decides is a file. I'm not
    aware of any interface to create one and open a file with the same func-
    tion call.

    I _think_ what Paul was asking was is it possible to get notified when a specific file in the file system is opened. If that's what he's asking,
    then the answer is: yes kqueue/kevent can do that. You open the file in question using O_PATH, and then create a kevent using that descriptor
    with filter EVFILT_VNODE and event NOTE_OPEN.
    --
    Alan Bawden
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 07:50:22 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 12 Aug 2026 03:23:45 -0400, Alan Bawden wrote:

    I _think_ what Paul was asking was is it possible to get notified
    when a specific file in the file system is opened. If that's what
    he's asking, then the answer is: yes kqueue/kevent can do that. You
    open the file in question using O_PATH, and then create a kevent
    using that descriptor with filter EVFILT_VNODE and event NOTE_OPEN.

    There is no POSIX API for this. Linux has inotify(7) for watching
    particular files, and certain kinds of directory operations, and
    fanotify(7) for more general watching of entire
    directories/filesystems.

    <https://manpages.debian.org/inotify(7)> <https://manpages.debian.org/fanotify(7)>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From bixbox@noreply@example.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 10:16:25 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 09/08/2026 4:52 PM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    No the subject of /weird/, I've also found it highly bizarre, if not
    outright disturbing, that people don't use do ... while(); in C. It's
    an eminently useful structured programming pattern.

    Finally, every time that I open a PR with that pattern I get questioned
    and frown. It's such disturbing.


    On the subject of Common Lisp, I find it more than disturbing when a
    codebase lacks the basic usage of hash tables.

    https://www.sbcl.org/manual/#hash-table-extensions

    unless you find some code base that use hash table all over the place.
    :)

    bix
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Wed Aug 12 09:12:55 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote: |-----------------------------------------------------------------------|
    |"> Is BASh on Windoze without its features on gratis operating systems?|
    | | |ItrCOs not about gratis, itrCOs about libre." | |-----------------------------------------------------------------------|

    I use a probably gratis copy of a libre operating system. One can buy
    a libre non-gratis copy.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.c on Wed Aug 12 02:22:57 2026
    From Newsgroup: comp.lang.lisp

    Alan Bawden <alan@csail.mit.edu> writes:
    I _think_ what Paul was asking was is it possible to get notified when a specific file in the file system is opened.

    No in linux that's called inotify. io_uring is basically an alternative
    system call interface that's relatively new, and maybe not complete.
    You send off a request to do the system call, and get back a queued
    response when the call is completed, unlike traditional syscalls that
    appear to be synchronous.

    One of the calls you can do that way is opening a file. Historically in
    Unix and Linux, there was no way to do that asynchronously. If you used
    open() and the operation was slow (for example NFS, or even anything on
    a hard disk), your program would be blocked until the call returned. If
    you don't want to block, you have to do the open() in a separate thread.
    GHC and Erlang BEAM have lightweight threads/processes, but they also
    had a pool of OS threads to handle operations like opening files.

    io_uring lets you open files asynchronously, so you can in principle
    simulate an OS in a single user-level process. More typically though,
    io_uring is used as an alternative to something like epoll, for
    listening on lots of sockets at the same time. There are a lot of
    benchmarks around that I think say io_uring is a little faster.
    io_uring also can replace AIO, which never worked very well. AIO was
    for asynchronous disk i/o operations after the file was already open.

    I haven't had occasion to use io_uring yet but I saw its importance when
    it first appeared.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.c on Wed Aug 12 09:01:41 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 11/08/2026 4:41 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket
    on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket >>>>> maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.
    Sounds very Java-like. Though perhaps not as irritating as Java.
    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.


    I admit I'm not sure why the select system call seems to be missing from >>> this selection of networking functions, [...]

    It would be like writing C in Lisp notation. For select (called
    unix-fast-select in SBCL), see sb-unix.
    (defun wait-for-stdin-select ()
    (sb-alien:with-alien ((read-fds (sb-alien:struct sb-unix:fd-set)))
    (sb-unix:fd-zero read-fds)
    (sb-unix:fd-set 0 read-fds)
    (format t "Waiting up to 5 seconds for input on stdin... Type something!~%")
    (force-output)
    (multiple-value-bind (count err)
    (sb-unix:unix-fast-select 1 (sb-alien:addr read-fds) nil nil 5 0) >> (cond
    ((null count)
    (format t "Select failed with errno: ~A~%" err))
    ((zerop count)
    (format t "Timeout! No input received.~%"))
    ((sb-unix:fd-isset 0 read-fds)
    (format t "Data is ready to be read from stdin!~%"))
    (t
    (format t "Something else woke up select!~%"))))))
    ;; run it
    (wait-for-stdin-select)

    Thank you. This is indeed helpful.

    But don't assume I'd ever write something like that in Lisp. Again,
    that's like C programming in Lisp notation. See IOLib, for example.

    Unhelpfully, Lawrence is always talking about some sort of select in
    Python, and then talks about polling in Linux, when he knows we don't
    care about the Linux kernel here in comp.lang.lisp, because the Steel
    Banks Common Lisp encapsulates the kernel for us.

    No sarcasm here. Lawrence has been doing a great service to the current
    USENET. We can say whatever we want about his knowledge or opinions or whatever, but he keeps a lot of people distracted here and I'm sure
    these people are all looking for a distraction. And his distractions
    are not all inadequate. He's usually bring up on-topic things that
    allows people here to exercise their own skills. If these contributions
    are too shallow---well---I'd say that's something we can say about most
    USENET traffic these days. Because we're very low volume these days, I
    think shallow contributions are better than nothing. I prefer the
    shallow chat than no chat at all.

    And no, I don't know why Lawrence is always pretending to be a Python influencer here in comp.lang.lisp. I hope he's getting paid for it.

    From what I can tell, Lawrence never really caught the Lisp culture---it
    can be seen in how he writes Lisp in the occasion he does it. This
    means his criticism aren't very serious. He loves Python, which is a
    way of saying---``thanks, Lisp, for the things you've done for me.''
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 15:23:48 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:

    I liked the idea of

    (with-current-readtable (xyz)
    ...)


    That is unuseful unless the body is a bunch of file compilations / loads.
    It should be apparent why.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 15:23:49 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:


    using macros to enhance performance is usually a bad idea.

    Macros are for building languages in which you can express ideas concisely.

    There are two laws of programming:

    (1) All sufficiently large programming systems become programming
    languages.
    (2) However soon you think (1) applies, it applies sooner than
    that.

    Blub languages (not my term) are largely those in which building languages
    is hard. Using Lisp as a blub language has always seemed weird to me.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 15:23:52 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:


    using macros to enhance performance is usually a bad idea.

    Macros are for building languages in which you can express ideas concisely.

    There are two laws of programming:

    (1) All sufficiently large programming systems become programming
    languages.
    (2) However soon you think (1) applies, it applies sooner than
    that.

    Blub languages (not my term) are largely those in which building languages
    is hard. Using Lisp as a blub language has always seemed weird to me.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 15:30:03 2026
    From Newsgroup: comp.lang.lisp

    Nuno Silva <nunojsilva@invalid.invalid> wrote:

    Why should it be termed "weird" at all? Is this one of these things
    where somebody comes up with a definition of the "normal" way to do
    things and points fingers at anyone who deviates from that? Or is macro system usage somehow mandatory for Lisp programming?


    A very long time ago, Lisp had many unique features. Today it has exactly
    one, but that feature is critical. It just seems weird to me to ignore its defining characteristic. Not wrong: weird.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 15:52:47 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:


    For a long time, Scheme didn't have macros, but it was still considered
    cool.


    Scheme-the standard did not: pretty much every implementation did.

    Lisp macros are generally a way for user code to get hold of unevaluated
    args in a sexp.

    Oh please, stop. You are describing fexprs. You can implement fexprs
    with macros (I have like six such fir CL, I can't even remember if I've published any (looks like I have, actually). You can't, in CL or any
    language with semantics anything like similar to it, go the other way.

    If your language has [...]
    syntactic support for your likely macro use cases (lots of languages),
    macros become less important.

    Right, if the language you already has supports every construct anyone
    might ever want to do anything, then nobody needs macros. That language
    is, of course, for all practical purposes, infinite. Its implementation
    will take an infinite amount of time. After, that is, people have agreed
    what the useful constructs *are*.

    As Lispers like to say, syntax is no big
    deal. So why obsess about being able to redefine it?


    Do they say that? Which ones? This one thinks that domain-specific and application-specific languages are useful and thinks that languages with facilities which allow the simple incremental construction of such
    languages are therefore also useful.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 16:25:03 2026
    From Newsgroup: comp.lang.lisp

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:


    The Apollo code *did* have an operating system. And remember, it
    crashed twice during the Apollo 11 landing. And got very confused by
    that lightning strike during the Apollo 12 launch.


    It had an OS in roughly the same sense that the 1802 code I used to write
    had an OS.

    It did not crash during the Apollo 11 powered descent. It detected that it couldn't handle all the data, said this, then threw away the data it
    couldn't handle and carried on. It did that by resetting itself, but
    that's not a crash: that was how it was designed to deal with this
    eventuality.

    I think that during the Apollo 12 event the AGC (which was not in use at
    the time: the DSKY was covered up by a checklist until it was removed
    during the event) did say true things: they did in fact lose the platform
    and it didn't know the attitude of the spacecraft as a result. Fortunately
    it didn't need to as the IU was running the ascent
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Wed Aug 12 16:28:06 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote: |---------------------------------------------------------------------|
    |"On Tue, 11 Aug 2026 18:31:24 +0100, Aidan Kehoe wrote: |
    |[. . .] |
    (I certainly donrCOt want to have to migrate well-written PHP of | twenty years ago that carefully wrapped access to a database using | then-best-practice APIs because those APIs are unmaintained and | removed, but that is entirely on me, we all know PHP is terrible, |
    and I knew it then. |
    | |
    |I have never developed any web app from scratch in PHP. The only time|
    |IrCOve used it is to maintain existing code, or write plugins for | |existing code (WordPress, WooCommerce). |
    | |
    |As a language, its features read like a shopping list of sadness." | |---------------------------------------------------------------------|

    WordPress. Ugh!
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ram@ram@zedat.fu-berlin.de (Stefan Ram) to comp.lang.lisp on Wed Aug 12 16:31:01 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> wrote or quoted:
    A very long time ago, Lisp had many unique features. Today it has exactly >one, but that feature is critical. It just seems weird to me to ignore its >defining characteristic. Not wrong: weird.

    Reddit concluded that with macros they were now supposed to learn
    to read several entirely unique, personalized programming languages,
    and preferred to rewrite their system in Python.

    Python's wrappers and resource contexts give developers a way to
    pass executable blocks to functions or objects achieving what devel-
    opers often use macros for without exposing the chaotic power of
    full AST manipulation.

    Python Example (without the implementation of the "macros")

    @html_element("div")
    def render_page():
    with html_block("p"):
    print(" Hello, world! This is nested content.")

    render_page()

    Output

    <div>
    <p>
    Hello, world! This is nested content.
    </p>
    </div>

    Python Example (with the implementation of the "macros")

    import functools
    from contextlib import contextmanager

    def html_element(tag):
    def decorator(func):
    @functools.wraps(func)
    def wrapper(*args, **kwargs):
    print(f"<{tag}>")
    result = func(*args, **kwargs)
    print(f"</{tag}>")
    return result
    return wrapper
    return decorator

    @contextmanager
    def html_block(tag):
    print(f" <{tag}>")
    try:
    yield
    finally:
    print(f" </{tag}>")

    @html_element("div")
    def render_page():
    with html_block("p"):
    print(" Hello, world! This is nested content.")

    render_page()


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Wed Aug 12 16:52:32 2026
    From Newsgroup: comp.lang.lisp

    Steve G <SGonedes1977@GMail.com> wrote: |----------------------------------------------------------------------------| |"Aidan Kehoe <kehoea@parhasard.net> writes: | |[. . .] | | | |[. . .] | |[. . .] stallman [. . .] | |he is sometimes very prophetic. I recommend reading his essay on the | |right to read." | |----------------------------------------------------------------------------|

    Dear Mister Stephen G:

    I had bought many books. They have been robbed. I never got to read
    them :(

    |----------------------------------------------------------------------------| |"[. . .] He basically describes our (USA) | |current education crisis. The children are not taught to read/write cursive,| |[. . .]" | |----------------------------------------------------------------------------|

    I do not write cursive writings. I am an Asperger autist.

    A neighbor in Ireland recently alleged to me that children here are
    not taught to write handwriting at all - not just not cursive
    handwritings! Handwriting is too important to be neglected!

    A journalist reported more than 3 years ago that a primary school
    which is located at the end of a route of circa 5.5 miles (according
    to
    HTTPS://WWW.ViaMichelin.com
    ) from me stopped using books! A primary school might be what you call
    an elementary school. The pupils in a primary school are younger than teenagers. A neighbor is related to a teacher here. This teacher
    laughed at a relative because this non-teacher relative uses a
    dictionary instead of Google.

    |----------------------------------------------------------------------------| |"[. . .] you | |did not even tell me to quit smoking cigarettes :)" | |----------------------------------------------------------------------------|

    Do not smoke :)
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Wed Aug 12 13:06:51 2026
    From Newsgroup: comp.lang.lisp


    ADDENDUM

    On Tue, 11 Aug 2026 12:20:00 -0400, George Neuner
    <gneuner2@comcast.net> wrote:

    On Mon, 10 Aug 2026 10:48:48 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    George Neuner <gneuner2@comcast.net> writes:

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    How about the [Racket] macro system? So perfect, yet so annoying.
    One thing I love about Common Lisp is precisely macro's (lack of) >>>>hygiene. I'm totally fine with complete guarantee. Anaphoric
    macros are so useful. (No idea how to implement them in Racket >>>>---impossible?)

    Racket has its roots in Scheme. Scheme is defined in terms of source
    /text/ rather than the compiler's AST. So there is no real equivalent
    of Lisp's AST macros.

    :
    Is there an article out there that elaborate your paragraph here? I'd
    like to learn more about these differences. I suppose the Scheme people >>would have very strong arguments to go their way.

    :

    It is implicit in the semantics sections of the R_RS documents. Might
    be explicit in some of them, I don't recall - the earlier documents
    tended to contain more detail about intent, but I haven't (re)read any
    of them in ages. I'm sure I've seen it explicitly stated somewhere,
    but it may have been in some book.
    [One of my college professors was Mitchell Wand who co-wrote
    "Essentials of Programming Languages" and served on the Scheme
    defining committee for many years.]

    TLDR; Scheme's formal semantics are based on the syntax of forms in
    the /external/ representation - ie. the source text - not on any
    compiler's internal representation.

    R6RS has in Appendix (A) a discussion of the formal semantics in which
    they do state that Scheme's denotation semantics are based on
    /strings/. Unfortunately the statement is offhand and the discussion
    itself is non-normative.

    So far I haven't been able to find it stated explicitly in any
    normative (authoritative) source, but I don't have access to the ISO
    or IEEE standard documents.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 17:07:09 2026
    From Newsgroup: comp.lang.lisp

    Stefan Ram <ram@zedat.fu-berlin.de> wrote:

    Reddit concluded that with macros they were now supposed to learn
    to read several entirely unique, personalized programming languages,
    and preferred to rewrite their system in Python.

    If that's a problem for you, I'd suggest doing the same. But, if this was
    the reason (fully willing to believe it was the reason) what it actually
    means is that their development practices were deeply, deeply shit. In particular they had so little coordination that they allowed individual developers to implement their own sets of, presumably undocumented,
    macrology, so people couldn't read each other's code. what they should have been doing is developing *a* language to deal with the problem domain, not
    six.

    Presumably the macros themselves were poorly designed, because half the
    purpose of well-designed constructs is to be easy to read. It shouldn't be hard for anyone who writes Lisp to guess what

    (for ((e (in-list l)
    (i (in-vector v)))
    ...)

    does, or

    (destructuring-match thing
    ((a) ...)
    ((a b) ...)
    (otherwise ...))

    does.

    More to the point by 2005 there were loads of Python web frameworks and
    loads of mostly-replacable Python programmers: what company wouldn't want
    that.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 12 17:16:00 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:

    R6RS has in Appendix (A) a discussion of the formal semantics in which
    they do state that Scheme's denotation semantics are based on
    /strings/. Unfortunately the statement is offhand and the discussion
    itself is non-normative.

    I think it's pretty clear. If you look at the formal syntax there is, for instance a definition of a list (it's one of the options for <datum>, but a procedure call is (<operator> <operand>*): it's not defined in terms of a
    list at all.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ram@ram@zedat.fu-berlin.de (Stefan Ram) to comp.lang.lisp on Wed Aug 12 17:20:24 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> wrote or quoted:
    Stefan Ram <ram@zedat.fu-berlin.de> wrote:
    Reddit concluded that with macros they were now supposed to learn
    to read several entirely unique, personalized programming languages,
    and preferred to rewrite their system in Python.
    If that's a problem for you, I'd suggest doing the same. But, if this was >the reason (fully willing to believe it was the reason)

    AFAIK it was not the only reason.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.lisp,comp.lang.c on Wed Aug 12 12:59:36 2026
    From Newsgroup: comp.lang.lisp

    On 8/11/2026 8:59 PM, Paul Rubin wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    https://man.freebsd.org/cgi/man.cgi?kqueue

    Is this something like io_uring? Is it just for i/o on open fd's or can
    you also use it for stuff like opening files?

    io_uring is meant for io completion. Its more low level than IOCP over
    on the windozer. Heck, on win, we can use it (IOCP) for files and
    sockets. io_uring takes special care with padding and alignment to get
    the mmapped memory to work with the kernel.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Wed Aug 12 23:23:32 2026
    From Newsgroup: comp.lang.lisp


    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh Paul Rubin:

    Aidan Kehoe <kehoea@parhasard.net> writes:
    once the twelve Buckfasts have worn off

    I had to look that up. Wow, that's the medicine we all need, lol.

    https://en.wikipedia.org/wiki/Buckfast_Tonic_Wine

    If you ever visit the UK (or Ireland), I strongly recommend that you do not try Buckfast. You likely will not end up in the Emergency Department, but it will add nothing constructive to your stay. (And you *might* end up in the Emergency Department, and you might start a fight with someone you would otherwise not have started a fight with, and, well, itrCOs great to have a working mandible.q)
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan Bawden@alan@csail.mit.edu to comp.lang.lisp,comp.lang.c on Wed Aug 12 20:55:55 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    Alan Bawden <alan@csail.mit.edu> writes:
    I _think_ what Paul was asking was is it possible to get notified when a
    specific file in the file system is opened.

    No in linux that's called inotify. io_uring is basically an alternative system call interface that's relatively new, and maybe not complete.
    You send off a request to do the system call, and get back a queued
    response when the call is completed, unlike traditional syscalls that
    appear to be synchronous.

    Ah! I didn't understand your original question because I didn't have
    the context of knowing what io_uring was. Thanks for introducing me to something new.
    --
    Alan Bawden
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Thu Aug 13 11:20:20 2026
    From Newsgroup: comp.lang.lisp

    On 12/08/2026 8:01 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 11/08/2026 4:41 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    To be fair, a big part of my struggle is the thick layer of Racket >>>>>> on top of POSIX. For instance, try to locate the equivalent
    select-call on it. It's so hard to recognize exactly how your Racket >>>>>> maps to the lower level. I understand that may a strong point of
    Racket's design, but it certainly hits my weakness.
    Sounds very Java-like. Though perhaps not as irritating as Java.
    Compare Python <https://docs.python.org/3/library/select.html> --
    thatrCOs less than 10 pages (i.e. number of times I have to hit
    Page-Down in the browser) of docs.


    I admit I'm not sure why the select system call seems to be missing from >>>> this selection of networking functions, [...]

    It would be like writing C in Lisp notation. For select (called
    unix-fast-select in SBCL), see sb-unix.
    (defun wait-for-stdin-select ()
    (sb-alien:with-alien ((read-fds (sb-alien:struct sb-unix:fd-set)))
    (sb-unix:fd-zero read-fds)
    (sb-unix:fd-set 0 read-fds)
    (format t "Waiting up to 5 seconds for input on stdin... Type something!~%")
    (force-output)
    (multiple-value-bind (count err)
    (sb-unix:unix-fast-select 1 (sb-alien:addr read-fds) nil nil 5 0) >>> (cond
    ((null count)
    (format t "Select failed with errno: ~A~%" err))
    ((zerop count)
    (format t "Timeout! No input received.~%"))
    ((sb-unix:fd-isset 0 read-fds)
    (format t "Data is ready to be read from stdin!~%"))
    (t
    (format t "Something else woke up select!~%"))))))
    ;; run it
    (wait-for-stdin-select)

    Thank you. This is indeed helpful.

    But don't assume I'd ever write something like that in Lisp. Again,
    that's like C programming in Lisp notation. See IOLib, for example.

    Unhelpfully, Lawrence is always talking about some sort of select in
    Python, and then talks about polling in Linux, when he knows we don't
    care about the Linux kernel here in comp.lang.lisp, because the Steel
    Banks Common Lisp encapsulates the kernel for us.

    No sarcasm here. Lawrence has been doing a great service to the current USENET. We can say whatever we want about his knowledge or opinions or whatever, but he keeps a lot of people distracted here and I'm sure
    these people are all looking for a distraction. And his distractions
    are not all inadequate. He's usually bring up on-topic things that
    allows people here to exercise their own skills. If these contributions
    are too shallow---well---I'd say that's something we can say about most USENET traffic these days. Because we're very low volume these days, I
    think shallow contributions are better than nothing. I prefer the
    shallow chat than no chat at all.

    And I prefer polite chat, such as the one we are now having. Thank you.

    I can only talk about my own skillset in Common Lisp, which I will prob-
    ably have to say is not that great, having used it much less in anger
    than C -- and prior to that, C++ but that's a different story -- and so
    I got myself all the Lisp books I have amassed, most or all of them al-
    ready mentioned in various topics here in comp.lang.lisp.

    That said, life happened, and continues to happen, so I don't know when
    I'll get to increase my skillset in Lisp. As everyone in comp.lang.c
    knows, I'm currently going through Appel's compiler book in C, and well,
    also took a detour by re-reading Loudon's /Mastering Algorithms in C/,
    which while somewhat basic in the C, is very good at giving practical
    examples of the data structures in question.

    I've previously mentioned a similar book in Lisp, by Domkin. I'll get
    to it one of these decades.


    And no, I don't know why Lawrence is always pretending to be a Python
    influencer here in comp.lang.lisp. I hope he's getting paid for it.

    From what I can tell, Lawrence never really caught the Lisp culture---it
    can be seen in how he writes Lisp in the occasion he does it. This
    means his criticism aren't very serious. He loves Python, which is a
    way of saying---``thanks, Lisp, for the things you've done for me.''

    I'm not sure I did either, to be honest. I just find it fascinating in
    many ways, and wish to increase my own skillset in Lisp, and of course,
    get a better immersion in the culture.

    Personally, I think Lisp people need -- well, need is a strong word, but
    I'll go with it -- to get a little bit more behind the notion of practi- cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de-
    tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    Games with Gabe wrote* about that extensively in his YouTube video, at

    https://www.youtube.com/watch?v=IbDAmvUwo5c

    and I heartily agree.

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.

    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three dimensional
    game objects.

    What do you think?


    * Here I'm making fun of the YouTubian culture of only ever talk** about videos, and never anything published in books. "This guy made a video
    about something, and I'm going to talk about too" is the typical intro
    duction, if I remember correctly. I don't watch much of YouTube any-
    more.

    ** I'm going to leave this grammatical error.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Thu Aug 13 11:33:20 2026
    From Newsgroup: comp.lang.lisp

    On 12/08/2026 3:50 PM, Lawrence DrCOOliveiro wrote:
    On Wed, 12 Aug 2026 03:23:45 -0400, Alan Bawden wrote:

    I _think_ what Paul was asking was is it possible to get notified
    when a specific file in the file system is opened. If that's what
    he's asking, then the answer is: yes kqueue/kevent can do that. You
    open the file in question using O_PATH, and then create a kevent
    using that descriptor with filter EVFILT_VNODE and event NOTE_OPEN.

    There is no POSIX API for this. Linux has inotify(7) for watching
    particular files, and certain kinds of directory operations, and
    fanotify(7) for more general watching of entire
    directories/filesystems.

    <https://manpages.debian.org/inotify(7)> <https://manpages.debian.org/fanotify(7)>

    Lawrence, we don't care about Posix here in comp.lang.lisp, nor do we
    care about what the Linux kernel people think is a good idea. They al-
    most never have good ideas anyway.

    So stop trying to force Posix discussion into kqueues and Illumos ports,
    unless you're also working for the Open Group, and trying to get some
    things standardized.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.c on Thu Aug 13 11:37:29 2026
    From Newsgroup: comp.lang.lisp

    On 12/08/2026 3:23 PM, Alan Bawden wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 12/08/2026 11:59 AM, Paul Rubin wrote:
    Is this something like io_uring? Is it just for i/o on open fd's or can >>> you also use it for stuff like opening files?
    The kqueue() is for open file descriptors, created as sockets or open
    files, or anything else the FreeBSD kernel decides is a file. I'm not
    aware of any interface to create one and open a file with the same func-
    tion call.

    I _think_ what Paul was asking was is it possible to get notified when a specific file in the file system is opened. If that's what he's asking,
    then the answer is: yes kqueue/kevent can do that. You open the file in question using O_PATH, and then create a kevent using that descriptor
    with filter EVFILT_VNODE and event NOTE_OPEN.


    Thank you. Are you aware of any book on this subject? One that teaches
    the ins and outs of how to use kqueues in FreeBSD? Something similar to /Advanced Programming in the UNIX Environment/ by Stevens?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Wed Aug 12 20:46:39 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp.

    I mentioned Land of Lisp a couple days ago. Its sample programs are
    games, if that helps. They're closer to Hunt the Wumpus than to a
    modern AAA game, but it's a start.

    You might also like Tim Sweeney's old slide deck about a hypothetical
    new language for game dev:

    https://groups.csail.mit.edu/cag/crg/papers/sweeney06games.pdf
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Thu Aug 13 05:03:50 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 12 Aug 2026 16:28:06 -0000 (UTC), C||il|!n Niocl|is|!n Glost|-ir wrote:

    WordPress. Ugh!

    WordPress is, I suspect one of the better collections of PHP code
    around, simply through sheer necessity, after its developers have had
    their heads banged together multiple times over security holes and the
    like.

    But it still has its bits of sadness. Like the way it does multisite
    support by duplicating table schemas with different prefixes assigned
    to the table names. That is rCLUgh!rCY indeed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Thu Aug 13 14:28:06 2026
    From Newsgroup: comp.lang.lisp

    On 13/08/2026 11:46 AM, Paul Rubin wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp.

    I mentioned Land of Lisp a couple days ago. Its sample programs are
    games, if that helps. They're closer to Hunt the Wumpus than to a
    modern AAA game, but it's a start.

    Yes, thank you. It's still in my shopping cart since a few days ago,
    and is likely to remain there until I start to get paychecks again.

    Sadly the new job I have lined up doesn't make use of Common Lisp yet,
    yet I have high hopes I can change that.


    You might also like Tim Sweeney's old slide deck about a hypothetical
    new language for game dev:

    https://groups.csail.mit.edu/cag/crg/papers/sweeney06games.pdf


    I'll keep it in mind.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From bixbox@noreply@example.invalid to comp.lang.lisp on Thu Aug 13 11:46:25 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp.

    I mentioned Land of Lisp a couple days ago. Its sample programs are
    games, if that helps. They're closer to Hunt the Wumpus than to a
    modern AAA game, but it's a start.

    I second Land of Lisp, not only because there is an example of game, but moreover because, as I have to work with C/C++ at work, the way that the
    design is approached is very Lispy and refreshing to me, and something
    that in my day to day job I have no opportunity to explore and learn
    and practice.

    bix
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From bixbox@noreply@example.invalid to comp.lang.lisp on Thu Aug 13 12:35:00 2026
    From Newsgroup: comp.lang.lisp

    Mario Rosell <mario@mariorosell.es> writes:

    Hello everyone!

    I want to learn Common Lisp, but I don't really know what resources to
    use.

    What did you all use to learn? Is that even relevant? Is this newsgroup active?

    Book already mentioned that was very useful to me, apologies to re-post
    1. Practical Common Lisp
    2. OnLisp
    3. Land Of Lisp

    one of my favorites but it's maybe controversial is Let Over Lambda

    A proper setup with Emacs with Sly, and lately I was able to enable
    open local HyperSpec from a symbol ( that was a game changer for my brain
    that can not hold to much info and unfortunately I have to use C++ at work).

    Quicklisp is very very handy, and I'm trying to setup quicklisp lookup
    textinfo from symbol as well similar to the HyperSpec, but the mileage
    vary here.


    bix


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anthk GM@anthk@disroot.org to comp.lang.lisp on Thu Aug 13 13:40:15 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-02, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Sun, 02 Aug 2026 16:42:37 +0000, kotorifan wrote:

    For learning the basics about the language I highly recommend the
    book "Practical Common Lisp" by Peter Seibel.

    Common Lisp is a museum-worthy spec by this point. There needs to be something more modern, not so full of legacy baggage tied to old, proprietary, pre-POSIX OS platforms which are all extinct by now.

    Also it does help to have a background in Emacs Lisp ...

    Emacs Lisp contains some useful functionality beyond that specified by
    Common Lisp, but it still isnrCOt really enough for a general-purpose programming language. Not in this day and age.

    SBCL tells me otherwise, ditto with the Kandria engine,
    or projects like Nyxt. Also, Coalton + Quilc in quantum
    mechanics basically makes any 'legacy' assumption on
    CL laughable.

    Good luck with the Scheme maze of SRFI's, ice-9's
    in guile vs eggs in Chicken and then the RSRx's.
    And, yes, I love SICP, and doing Chicken Scheme
    through it. But fragmentation made Scheme a broken
    dream.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 13 11:42:36 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an t-aon|| l|i d|-ag de m|! L||nasa, scr|!obh Anton Antimo:

    Aidan Kehoe <kehoea@parhasard.net> writes:

    Ar an deichi|| l|i de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Sun, 09 Aug 2026 18:42:29 -0400, steve g wrote:

    [...] GC is for user space, not kernel space. Kernel developers are usually very good programmers.

    Do different laws of physics apply in kernel space or something? And/or
    is that an admission that garbage collection is not for rCLvery good programmersrCY?

    Let me digress for a moment:

    Within medicine, my day job, [...]

    Very cool that we have people from areas such as medicine here. (In reality,
    there's no academic discipline called programming---people in Computer Science are more often than not not programmers at all.) Medicine, in particular, is an unexpected one. Can you share a bit more about your history as in how did you get interested in medicine and computers (and Lisp
    specially)? That'd be cool to hear. (Assuming a little social chat is acceptable here given the current low volume.)

    My first degree was 1998-2002 and the professor (clearly taking
    shelter from the first AI winter) assigned the GNU Emacs manual as
    required reading for the first class. (This is, I understand, not
    typical.)

    Very atypical these days. Your first degree must have been Computer
    Science? So you got two degrees. Having a degree or not in such areas,
    I think that understanding the fundamentals of computers and programming
    is a pretty good skill these days. There might be other areas I miss
    for sheer lack of wisdom here.

    I took a ``programming 102'' engineering class a few years ago in which
    the professor offered us a ZIP package containing the GNU EMACS set up
    with Python. Students on the first day of class protested against their ``programming 101'' (a Python primer) saying it was essentially useless
    with no real-world anything (which I fully agree: that course's real
    objective was to teach us the syntax of Python [with no OOP, which is
    the job of ``programming 102'']).

    The professor replied saying he would present us with some illustrations
    of real-world stuff. To my surprise, one of these things was the GNU
    EMACS. His EMACS came with all of its default configuration but some additional ones for people to run Python and ESHELL. (To run it, we'd
    double click on a icon on the desktop.) Students were welcome to ignore
    it all and use Python's IDLE or whatever, which I think 99% of them did.
    What students couldn't ignore, which was cool (lol), was that the way to
    turn in homework was through fossil. The professor introduced us to
    fossil in another lecture, saying he chose fossil over git due to
    slightly greater simplicity (compared to git, which I couldn't quite
    see). I was likely the one exception that didn't struggle with
    fossil----I had never heard of it until then, but I've been using git
    for years. Anyway, after these lectures, he went on with the course,
    which didn't work very well at all because I think after the GNU EMACS
    and fossil most students had already given up on him---there were many
    other professors teaching the same course in a way that it had a lot
    less new things to learn.

    At that point XEmacs was a better editor so after using GNU Emacs for
    a few weeks I switched to XEmacs. It still meets my needs and I have
    no plan to switch away from it.

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition
    says XEmacs started out with coloring? IIRC, Stallman or someone would
    have said that the idea was not properly designed. I can't recall, but
    I might research the question and report back here.

    2002 was the Dot Com bust, and after six months unemployment following
    a 2.1 degree from the best university in my country, I ended up in
    technical support. To my surprise, I really enjoyed solving peoplerCOs problems then and there. Continued working in IT here in Europe (got
    out of technical support given it was clear that was moving to India,
    was in software development roles) realised I was not going to be able
    to comfortably raise a family in the roles I was doing.

    Understandable. (I began in technical support as well, but ``I ended
    up'' a mathematician.)

    2007 my parents pointed me towards a new rCLGraduate Entry MedicinerCY
    course in Dublin, on the US model of requiring another degree but
    being only four years in length; I realised from the technical support experience that I would likely enjoy the day-to-day of this, and you
    can comfortably raise a family in medicine in Ireland.

    That makes sense.

    Studied medicine 2008-2012, worked like a demon 2013-2021, and am no
    longer at the point where I have to work and study relentlessly to
    make forward progress. Very happy with the job and with my
    day-to-day, and I finally have a bit of breathing space to be back on
    Usenet.

    Cool!

    If you use any emacs itrCOs hard to avoid Lisp. Emacs Lisp is not a paragon of
    good design nor of good implementation-- (aset (symbol-name nil) 0 ?\u0192) , (fillarray obarray 0) , anyone?--so the natural thing is to look around for something better. The consensus within XEmacs was that Common Lisp was better.
    On investigating, yes, it is. But, XEmacs needs work, no-one else is doing it,
    so my software work these days is C with a very Common-Lisp-oriented Emacs Lisp.

    I tried the code above on the GNU EMACS. The first crashes it
    immediately. The second doesn't seem to do its job anymore, throwing a
    type error. They must have created a new type called obarray. Saying
    (type-of obarray) produces obarray, while fillarray expects a vector.

    --8<-------------------------------------------------------->8---
    fillarray is a primitive-function in rCyC source coderCO.

    (fillarray ARRAY ITEM)

    Store each element of ARRAY with ITEM.
    ARRAY is a vector, string, char-table, or bool-vector.

    [back]
    --8<-------------------------------------------------------->8---

    This would require essentially assembler written with the quality of
    the Apollo code, without an operating system. (IrCOm sure everyone reading this accepts that good assembler, if it has no bugs, is going
    to make better use of the hardware than their language of choice.)

    Perfectly reasonable.

    The trade-off is that the resulting software is slower than the above ideal, and, e.g. that my Windows install decides that it is going to update whether I like it or not and the Cygwin terminal that I had
    open, in the middle of debugging something, with a command history
    that I would ideally like to have kept, evaporates.

    Isn't that irritating? Windows is a system that's really not very respectful at all with what the user is doing---lots of interruptions
    such as alerts by Windows Defender and whatnot. Many other programmers
    on Windows follow suit, so it's not Microsoft's fault completely. And that might be the same thing in the usual GNU system these days. For window management, I run CWM, which is one that really only lets
    anything happen that the user has actively made it happen.

    The comment wasnrCOt intended to be specifically about Windows, that
    just happened to be the most recent example that sprung to mind. All
    the common operating systems take time to boot, time which would
    ideally be spent doing what you, as the user, actually wish to
    do. Even resume-from-hibernation is not instant.

    It'll be very cool when that is so. (A quick tangent.)

    Incidentally, two things I don't like in computers---(1) I don't like to
    keep them on if they're not being used; (2) I don't like a slow start-up
    nor messy output on the screen. Don't get me wrong: my favorite
    start-up output is by OpenBSD because they've kept the old-style boot
    process and it seems the system is never blankly waiting for anything.
    What I really dislike about the Linux kernel is how it quickly puts the
    video in some high-resolution mode, which flashes the screen. I wish it
    had stuck with the old-style of only changing video mode when starting X up---or at least when it had a readable text output like OpenBSD does.
    (And no I wouldn't like to see a graphical something instead of kernel messages: I like kernel messages because they're very informative. I
    put the Linux kernel in loglevel=7, one less than the greatest.)

    I've tried various things with it---for example, here's a kernel
    argument I use: video=eDP-2:800x600. But it still switches resolution
    during boot.

    All of the common operating systems update, often requiring a reboot,
    taking time which would ideally be spent doing what you, as the user, actually wish to do.

    Even if the update process is manual, e.g. when IrCOm using Debian and migrating a server to a new VM, I do not actually want to spend my
    time working out with trial and error what invocation of certbot will
    allow me to put Letsencrypt certificates on a new server that already
    has Apache installed. (Spoiler; spin down Apache, use certbot
    --certonly, which spins up its own HTTP server.)

    Speaking of which, I think the renewal should be easier. Having to shut
    down your web server to renew certificates is pretty odd to me. I know
    one can renew it via zone authentication and it can be automated using
    APIs, but that's also frustrating---most DNS hosts have their own
    specific API, forcing one to have to program the solution out. Oh, and wildcarded certificates /must/ be renewed via DNS (IIRC), that is, you
    can't spin a web server to authenticate and renew.

    (I certainly donrCOt want to have to migrate well-written PHP of twenty
    years ago that carefully wrapped access to a database using then-best-practice APIs because those APIs are unmaintained and
    removed, but that is entirely on me, we all know PHP is terrible, and
    I knew it then. But Debian shouldnrCOt be terrible, and in the grand
    scheme of things it isnrCOt terrible.)

    What did you write 20 years ago? That's indeed PHP's prime time. I
    know the language. I used it seriously back then as well. I never went
    into PHP 4, remaining in PHP 3 for as long as I could until I gave up on
    PHP completely---I've always appreciated language stability.

    There are reasons and many of them are good for these things. I donrCOt
    plan to switch my day-to-day to TempleOS. But that we have them is a
    trade off.

    Lol. TempleOS. I watched some documentaries on it (on YouTube). I was
    happy to see such systems out there and I think they're likely pretty
    good learning opportunities, obviously for the genius who made it, but certainly as well for anyone who looks into it, specially now with the
    help of these smart-systems (may we enjoy them while they last?).

    And speaking of Medicine, how is it disrespectful these days as
    well, but I won't digress on this (and it's perhaps just something
    that plagues the entirety of society).

    What do you mean? Respect towards and from medicine varies by
    country. Doctors are regularly assaulted in India by family members of patients unhappy with the patientsrCO care. I get Christmas presents.

    It is indeed. If my sources are correct, in the United States (for
    example), we get deaths due to medical error top ranked---I don't mean
    top 1st, but highly ranked (top 3 a while ago?).

    But what I had meant was that I get the feeling from hearing from the population that the attention and time doctors spend with patients now
    has been greatly reduced; that doctors are often rude, get easily
    irritated and so on. That then makes me think they might be working too
    much. I in fact see a parallel with programmers: in the typical
    company, the typical programmer can be slightly arrogant, easily
    irritated, the explanation for which might be too much work, not very
    competent and not living very joyful days. So in the end I don't see
    anything specific to Medicine, but something much larger. I'm a student
    at a large university---what can I say about professors? They're very
    easily offended with students' lack of interest; they inadvertently and incorrectly take a lot of things personally; my overall conclusion is
    that they're not doing very well health-wise, not living very joyful
    days (they might miss days in which there was more glamour in the
    profession, when they feel they would be better regarded). Something
    like that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Thu Aug 13 15:39:50 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition
    says XEmacs started out with coloring? IIRC, Stallman or someone would
    have said that the idea was not properly designed. I can't recall, but
    I might research the question and report back here.


    The Emacs schism was not fundamentally technical: it happened because cooperation with RMS is impossible. Lucid needed some features in what
    would have been Emacs 19 to support a programming environment (for C++, I think, not Lisp, despite them being Lucid) and were willing to donate the
    time to implement them & donate the results (remember Emacs 18 had an
    entirely minimal interface to X: equivalent to running it in a terminal emulator). And ... cooperation with RMS turned out to be impossible. So LEmacs happened, which became XEmacs after Lucid died.

    I wasn't there, but I was around a few months later and perhaps before the split was really final. I perhaps no longer have the trove of emails from
    the split: they made depressing reading.

    (If you're thinking of posting a followup explaining why cooperation with
    RMS is, in fact, possible, just ... don't, please.)
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 13 12:46:56 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    ADDENDUM

    On Tue, 11 Aug 2026 12:20:00 -0400, George Neuner
    <gneuner2@comcast.net> wrote:

    On Mon, 10 Aug 2026 10:48:48 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    George Neuner <gneuner2@comcast.net> writes:

    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo <anton@safunu.org>
    wrote:

    How about the [Racket] macro system? So perfect, yet so annoying. >>>>>One thing I love about Common Lisp is precisely macro's (lack of) >>>>>hygiene. I'm totally fine with complete guarantee. Anaphoric >>>>>macros are so useful. (No idea how to implement them in Racket >>>>>---impossible?)

    Racket has its roots in Scheme. Scheme is defined in terms of source
    /text/ rather than the compiler's AST. So there is no real equivalent >>>> of Lisp's AST macros.

    :
    Is there an article out there that elaborate your paragraph here? I'd >>>like to learn more about these differences. I suppose the Scheme people >>>would have very strong arguments to go their way.

    :

    It is implicit in the semantics sections of the R_RS documents. Might
    be explicit in some of them, I don't recall - the earlier documents
    tended to contain more detail about intent, but I haven't (re)read any
    of them in ages. I'm sure I've seen it explicitly stated somewhere,
    but it may have been in some book.
    [One of my college professors was Mitchell Wand who co-wrote
    "Essentials of Programming Languages" and served on the Scheme
    defining committee for many years.]

    TLDR; Scheme's formal semantics are based on the syntax of forms in
    the /external/ representation - ie. the source text - not on any
    compiler's internal representation.

    R6RS has in Appendix (A) a discussion of the formal semantics in which
    they do state that Scheme's denotation semantics are based on
    /strings/. Unfortunately the statement is offhand and the discussion
    itself is non-normative.

    So far I haven't been able to find it stated explicitly in any
    normative (authoritative) source, but I don't have access to the ISO
    or IEEE standard documents.

    That's okay---you've already enlightened me enough here, which I
    appreciate.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 13 12:19:58 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 12/08/2026 8:01 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 11/08/2026 4:41 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    [...]

    Unhelpfully, Lawrence is always talking about some sort of select in
    Python, and then talks about polling in Linux, when he knows we don't
    care about the Linux kernel here in comp.lang.lisp, because the Steel
    Banks Common Lisp encapsulates the kernel for us.

    No sarcasm here. Lawrence has been doing a great service to the
    current USENET. We can say whatever we want about his knowledge or
    opinions or whatever, but he keeps a lot of people distracted here
    and I'm sure these people are all looking for a distraction. And his
    distractions are not all inadequate. He's usually bring up on-topic
    things that allows people here to exercise their own skills. If
    these contributions are too shallow---well---I'd say that's something
    we can say about most USENET traffic these days. Because we're very
    low volume these days, I think shallow contributions are better than
    nothing. I prefer the shallow chat than no chat at all.

    And I prefer polite chat, such as the one we are now having. Thank you.

    Yeah---rudeness in USENET is a reflection of the health state of its participants.

    I can only talk about my own skillset in Common Lisp, which I will prob-
    ably have to say is not that great, having used it much less in anger
    than C -- and prior to that, C++ but that's a different story -- and so
    I got myself all the Lisp books I have amassed, most or all of them al-
    ready mentioned in various topics here in comp.lang.lisp.

    That said, life happened, and continues to happen, so I don't know when
    I'll get to increase my skillset in Lisp. As everyone in comp.lang.c
    knows, I'm currently going through Appel's compiler book in C, and well,
    also took a detour by re-reading Loudon's /Mastering Algorithms in C/,
    which while somewhat basic in the C, is very good at giving practical examples of the data structures in question.

    I've previously mentioned a similar book in Lisp, by Domkin. I'll get
    to it one of these decades.

    I've thankfully read this one by Kyle Loudon as well. Keep your
    studying going slowly, but constantly. There's no rush. Things
    meaningfully evolve as fast as everybody says. There's no royal road to knowledge and wisdom; no AI-road either. Keep it up; be careful with
    your time on the USENET.

    And no, I don't know why Lawrence is always pretending to be a Python
    influencer here in comp.lang.lisp. I hope he's getting paid for it.

    From what I can tell, Lawrence never really caught the Lisp
    culture---it can be seen in how he writes Lisp in the occasion he
    does it. This means his criticism aren't very serious. He loves
    Python, which is a way of saying---``thanks, Lisp, for the things
    you've done for me.''

    I'm not sure I did either, to be honest. I just find it fascinating in
    many ways, and wish to increase my own skillset in Lisp, and of course,
    get a better immersion in the culture.

    Try to understand when, why and how people did what they did. In other
    words, I think history is very important in studying. New is not always better.

    Personally, I think Lisp people need -- well, need is a strong word, but
    I'll go with it -- to get a little bit more behind the notion of practi- cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de- tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.

    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)

    Source:
    https://www.sbcl.org/manual/

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.

    That's what Racket claims. They claim it to be real-world, batteries
    included and whatnot. They also create executable binaries like SBCL
    does above.

    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three
    dimensional game objects.

    What do you think?

    I never think about games, thankfully. I've played video-games from 11
    to 14 years old, replacing them completely with UNIX, a great
    investment.

    Economically speaking, if CL had more users, there'd be more books. I
    don't have much need for Common Lisp (strictly speaking) books myself.
    I'm not trying myself to read more books on the language. What I'm
    doing is writing more Common Lisp and reading more of it. What
    certainly helps me is for people to use it, which then indirectly asks
    for more books (but for the wrong reasons: the beginner often thinks
    that something new is required for him to invest his time; reading an
    old book seems like a waste of time for so many of them, but that's only because they're beginners and might be for the rest of their lives).

    * Here I'm making fun of the YouTubian culture of only ever talk** about videos, and never anything published in books. "This guy made a video
    about something, and I'm going to talk about too" is the typical intro duction, if I remember correctly. I don't watch much of YouTube any-
    more.

    ** I'm going to leave this grammatical error.

    Yeah---knowing how to use a natural language includes knowing how to
    violate ``its grammar'' as well.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Thu Aug 13 16:14:56 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.


    In practise the answer is 'raco exe' which makes an executable. You have
    to have a suitable main function &c, but it's not hard.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 01:24:03 2026
    From Newsgroup: comp.lang.lisp

    On 13/08/2026 11:19 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 12/08/2026 8:01 PM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 11/08/2026 4:41 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 06/08/2026 5:48 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 05 Aug 2026 13:13:42 -0300, Anton Antimo wrote:

    [...]

    Unhelpfully, Lawrence is always talking about some sort of select in
    Python, and then talks about polling in Linux, when he knows we don't
    care about the Linux kernel here in comp.lang.lisp, because the Steel
    Banks Common Lisp encapsulates the kernel for us.

    No sarcasm here. Lawrence has been doing a great service to the
    current USENET. We can say whatever we want about his knowledge or
    opinions or whatever, but he keeps a lot of people distracted here
    and I'm sure these people are all looking for a distraction. And his
    distractions are not all inadequate. He's usually bring up on-topic
    things that allows people here to exercise their own skills. If
    these contributions are too shallow---well---I'd say that's something
    we can say about most USENET traffic these days. Because we're very
    low volume these days, I think shallow contributions are better than
    nothing. I prefer the shallow chat than no chat at all.

    And I prefer polite chat, such as the one we are now having. Thank you.

    Yeah---rudeness in USENET is a reflection of the health state of its participants.

    I can only talk about my own skillset in Common Lisp, which I will prob-
    ably have to say is not that great, having used it much less in anger
    than C -- and prior to that, C++ but that's a different story -- and so
    I got myself all the Lisp books I have amassed, most or all of them al-
    ready mentioned in various topics here in comp.lang.lisp.

    That said, life happened, and continues to happen, so I don't know when
    I'll get to increase my skillset in Lisp. As everyone in comp.lang.c
    knows, I'm currently going through Appel's compiler book in C, and well,
    also took a detour by re-reading Loudon's /Mastering Algorithms in C/,
    which while somewhat basic in the C, is very good at giving practical
    examples of the data structures in question.

    I've previously mentioned a similar book in Lisp, by Domkin. I'll get
    to it one of these decades.

    I've thankfully read this one by Kyle Loudon as well. Keep your
    studying going slowly, but constantly. There's no rush. Things
    meaningfully evolve as fast as everybody says. There's no royal road to knowledge and wisdom; no AI-road either. Keep it up; be careful with
    your time on the USENET.

    And no, I don't know why Lawrence is always pretending to be a Python
    influencer here in comp.lang.lisp. I hope he's getting paid for it.

    From what I can tell, Lawrence never really caught the Lisp
    culture---it can be seen in how he writes Lisp in the occasion he
    does it. This means his criticism aren't very serious. He loves
    Python, which is a way of saying---``thanks, Lisp, for the things
    you've done for me.''

    I'm not sure I did either, to be honest. I just find it fascinating in
    many ways, and wish to increase my own skillset in Lisp, and of course,
    get a better immersion in the culture.

    Try to understand when, why and how people did what they did. In other words, I think history is very important in studying. New is not always better.

    Personally, I think Lisp people need -- well, need is a strong word, but
    I'll go with it -- to get a little bit more behind the notion of practi-
    cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de-
    tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.

    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)

    Source:
    https://www.sbcl.org/manual/

    And herein lies the conundrum. I believe I took a quick glance at the
    manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have expectations of finding it in the first place.

    And now I found myself speaking like 17th century royalty.


    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.

    That's what Racket claims. They claim it to be real-world, batteries included and whatnot. They also create executable binaries like SBCL
    does above.

    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three
    dimensional game objects.

    What do you think?

    I never think about games, thankfully. I've played video-games from 11
    to 14 years old, replacing them completely with UNIX, a great
    investment.

    I believe there is something to be learned from making a fully grown
    video game, yet I have never done so. My brief stint as a /professional
    game developer/ was done with Unity, in C#, and I believe the game never
    got finished. What I have done is read a few book about game develop-
    ment -- many of them bought during this time frame -- and am now think-
    ing a small game done with SDL2 or SDL3 is worth exploring simply be-
    cause of the manual game loop. It's not often that we get to make our
    own loop, when we create graphical applications.

    And depending on how we create server applications, we don't either. If
    my recollection is correct about this, Hunchentoot would be a good exam-
    ple.

    There are other /programming patterns/ that show up almost exclusively
    in interactive games, well worth exploring now and then.


    Economically speaking, if CL had more users, there'd be more books. I
    don't have much need for Common Lisp (strictly speaking) books myself.
    I'm not trying myself to read more books on the language. What I'm
    doing is writing more Common Lisp and reading more of it. What
    certainly helps me is for people to use it, which then indirectly asks
    for more books (but for the wrong reasons: the beginner often thinks
    that something new is required for him to invest his time; reading an
    old book seems like a waste of time for so many of them, but that's only because they're beginners and might be for the rest of their lives).


    Well, I don't only mean beginner books. I mean some of the more ad-
    vanced books as well, when it comes to C. Of course /Common Lisp Re-
    cipes/, and /The Common Lisp Condition System/ should be good examples
    that I'll get to read one of these decades. Here I'm thinking of Adam Tornhill's /Patterns in C/. There are even several more, some of which
    I've lost track of, because I believe they were only available as a PDF
    and I neglected to print them out.

    Right now I'm not inclined to cross post this to comp.lang.c, and ask if
    they'd be willing to fill in some of those blanks.

    Hm, as-is, there seems to be a /blank/ in my knowledge, when it comes to thinking of an equivalent book in Lisp. Specifically about these /patt-
    erns/, and how to use them.

    Perhaps there is no need? After all, the original patterns book in Java
    was all about working around deficiencies in the Java programming lang-
    uage, and maybe Common Lisp has few enough of those we don't care about
    a specific set of patterns?

    Or is this simply covered in /Common Lisp Recipes/ and I forgot?


    * Here I'm making fun of the YouTubian culture of only ever talk** about
    videos, and never anything published in books. "This guy made a video
    about something, and I'm going to talk about too" is the typical intro
    duction, if I remember correctly. I don't watch much of YouTube any-
    more.

    ** I'm going to leave this grammatical error.

    Yeah---knowing how to use a natural language includes knowing how to
    violate ``its grammar'' as well.


    Have a nice day, and Lisp well!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 01:31:05 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 12:14 AM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.


    In practise the answer is 'raco exe' which makes an executable. You have
    to have a suitable main function &c, but it's not hard.



    Well, aside from technically correct answers, I was talking about the
    culture. In my recollection, and by now I guess that would be an old
    Racket,* there was no emphasis on creating binaries in the Racket intro- ductory material, nor user interface. It's more like, here's a pro-
    gramming language, use it!

    And until binaries are habitually made with Racket, and by that I mean production binaries, with code signatures for the Microsoft and fruit
    vendor platforms, that's not likely to change.


    Best wishes, and happy Racketteering!

    * Pun totally intended afterwards.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 01:36:46 2026
    From Newsgroup: comp.lang.lisp

    On 13/08/2026 6:35 PM, bixbox wrote:
    Mario Rosell <mario@mariorosell.es> writes:

    Hello everyone!

    I want to learn Common Lisp, but I don't really know what resources to
    use.

    What did you all use to learn? Is that even relevant? Is this newsgroup
    active?

    Book already mentioned that was very useful to me, apologies to re-post
    1. Practical Common Lisp
    2. OnLisp
    3. Land Of Lisp

    one of my favorites but it's maybe controversial is Let Over Lambda

    A proper setup with Emacs with Sly, and lately I was able to enable
    open local HyperSpec from a symbol ( that was a game changer for my brain that can not hold to much info and unfortunately I have to use C++ at work).

    Quicklisp is very very handy, and I'm trying to setup quicklisp lookup textinfo from symbol as well similar to the HyperSpec, but the mileage
    vary here.

    Yes, I think it's a very good idea to point beginners at both QuickLisp,
    and Peter's book at the same time. It's also not helpful to say /just
    use Slime/ if the beginner in question isn't used to Emacs. It can be
    much more fruitful to just set up a Lisp-enough environment in the text
    editor of choice -- by that I mean the choice of the student -- and then
    let the student move on to Emacs when warranted.

    There are Lisp environments for a lot of text editors out there, and I
    guess such could be called /resources to learn Common Lisp/ as well.


    Happy Lisping!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ram@ram@zedat.fu-berlin.de (Stefan Ram) to comp.lang.lisp on Thu Aug 13 17:39:43 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote or quoted: >Perhaps there is no need? After all, the original patterns book in Java

    Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M.,
    Fiksdahl-King, I., & Angel, S. (1977). A Pattern Language:
    Towns, Buildings, Construction. Oxford University Press.

    Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1994).
    Design Patterns: Elements of Reusable Object-Oriented Software
    (1st ed.). Addison-Wesley Professional. With examples in
    Smalltalk and C++.

    Gabriel, R. P. (1996). Patterns of Software: Tales from the
    Software Community. Oxford University Press.

    1996-01 Release of Java

    Grand, M. (1998). Patterns in Java, Volume 1: A Catalog of
    Reusable Design Patterns Illustrated with UML. John Wiley &
    Sons.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 13 16:52:28 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    Anton Antimo <anton@safunu.org> wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition
    says XEmacs started out with coloring? IIRC, Stallman or someone would
    have said that the idea was not properly designed. I can't recall, but
    I might research the question and report back here.

    The Emacs schism was not fundamentally technical: it happened because cooperation with RMS is impossible. Lucid needed some features in what
    would have been Emacs 19 to support a programming environment (for C++, I think, not Lisp, despite them being Lucid) and were willing to donate the time to implement them & donate the results (remember Emacs 18 had an entirely minimal interface to X: equivalent to running it in a terminal emulator). And ... cooperation with RMS turned out to be impossible. So LEmacs happened, which became XEmacs after Lucid died.

    I wasn't there, but I was around a few months later and perhaps before the split was really final. I perhaps no longer have the trove of emails from the split: they made depressing reading.

    (If you're thinking of posting a followup explaining why cooperation with
    RMS is, in fact, possible, just ... don't, please.)

    Thank you for describing the matter. You must be the best one here to elaborate on the schism? Can you elaborate it more technically? For
    instance, there's font locking today on the GNU EMACS---was it done in a dramatically different way relative to LEmacs?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Thu Aug 13 20:35:34 2026
    From Newsgroup: comp.lang.lisp

    I suppose that a typical medic is of a different personality type than
    a typical computer programmer. I do not think that being overworked is
    the overriding cause of the behavior of medics and programmers.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.emacs.xemacs on Fri Aug 14 05:04:27 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 3:52 AM, Anton Antimo wrote:
    tfb <tfb@work.it.out> writes:

    Anton Antimo <anton@safunu.org> wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition
    says XEmacs started out with coloring? IIRC, Stallman or someone would
    have said that the idea was not properly designed. I can't recall, but
    I might research the question and report back here.

    The Emacs schism was not fundamentally technical: it happened because
    cooperation with RMS is impossible. Lucid needed some features in what
    would have been Emacs 19 to support a programming environment (for C++, I
    think, not Lisp, despite them being Lucid) and were willing to donate the
    time to implement them & donate the results (remember Emacs 18 had an
    entirely minimal interface to X: equivalent to running it in a terminal
    emulator). And ... cooperation with RMS turned out to be impossible. So
    LEmacs happened, which became XEmacs after Lucid died.

    I wasn't there, but I was around a few months later and perhaps before the >> split was really final. I perhaps no longer have the trove of emails from >> the split: they made depressing reading.

    (If you're thinking of posting a followup explaining why cooperation with
    RMS is, in fact, possible, just ... don't, please.)

    Thank you for describing the matter. You must be the best one here to elaborate on the schism? Can you elaborate it more technically? For instance, there's font locking today on the GNU EMACS---was it done in a dramatically different way relative to LEmacs?

    Just to chime in for the newcomers who don't know about this publicly
    available summary.

    https://www.xemacs.org/Documentation/21.5/html/internals_4.html

    And.

    https://www.xemacs.org/About/XEmacsVsGNUemacs.html

    That said, I do hope tfb is willing to write out a technical summary, or
    even a social one like in the first link.

    Note that since then, GNU Emacs did indeed add loadable modules in C.


    Adding comp.emacs.xemacs to the discussion, because that group shouldn't
    be empty all the time.


    Happy text editing in XEmacs!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Thu Aug 13 18:59:07 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:


    An LLM is an emulation of a neural net. There's plenty of study
    material regarding neural nets.


    thank you.

    Modern implementations forgo the traditional graph representation and
    instead are based on matrix math. Ie. you take a bunch of inputs,
    multiply each input by a weight, offset the result by adding some
    value, then summ and pass the summ put through a (possibly per node)
    equation to get an output. That ptoentially feeds into the inputs of
    the next layer of nodes.

    The difficulty is in getting the topology correct. Too many nodes,
    the nodes start to specialize, too few nodes the results are fuzzy.
    Bad connection scheme - either it doesn't work or training becomes
    very difficult. NNs have been studied since the 1970s, and there are
    known topologies to create various kinds of recognizers and types of
    (app specific) memories. You can (sort of) plug and play using these
    as modules. But still a lot of it is just trial and error. That's why
    so much effort is needed to build them.

    I think I'm starting to see how loose these LLMs can get.


    LLMs [I agree it's a stupid name] are hidden node models having tens
    of thousands (or more) of nodes, and many millions of inputs [and
    weights and offsets]. You can't build one without a supercomputer.

    This is an excellent point I neglected to think about. I will be telling
    him how this kinda works. Big, Fast computers using lots of energy :) Nothing new...

    There's a PHd and potential billions of $$$ waiting if you can figure
    out how to make a NN reliably forget something it has learned, without retraining from scratch and without affecting anything else it knows.

    another very important point.

    is it possible to use a truth maintenance system? Just curious, it would probably take up too much space and time. Just a jtms is a lot of
    overhead. You could try to use an LTMS but we all know that this just
    leads to more wasted space and aggravation. I would think an ATMS would
    work; I dunno, I do not have a super computer or a billion dollars.

    Have fun!

    thank you so much for your excellent explanation. I really appreciate
    this. Asking someone about LLMs these days and they talk for hours and
    such have you.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Thu Aug 13 19:25:00 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    On Sun, 09 Aug 2026 19:12:49 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:


    I'm not aware that Racket can run over Cygwin. If it can, I would bet
    that GUI/graphical programs won't work.

    Certainly you can create an interface to Cygwin and use it directly.
    [You can do this with pretty much any library.]


    Yeah, i figured that no graphics would be their thing. I do remeber the
    cygwin people talking about make an X Window type interface. dunno how
    they plan to do that when the software changes ever other day that it rains.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Thu Aug 13 23:46:05 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 13 Aug 2026 13:40:15 -0000 (UTC), Anthk GM wrote:

    On 2026-08-02, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    Common Lisp is a museum-worthy spec by this point. There needs to
    be something more modern, not so full of legacy baggage tied to
    old, proprietary, pre-POSIX OS platforms which are all extinct by
    now.

    SBCL tells me otherwise, ditto with the Kandria engine, or projects
    like Nyxt. Also, Coalton + Quilc in quantum mechanics basically
    makes any 'legacy' assumption on CL laughable.

    IrCOm sure they do have their own extensions to make up for the
    deficiencies of Common Lisp. But then, they are no longer rCLCommonrCY,
    are they?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Thu Aug 13 23:58:22 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 13 Aug 2026 11:42:36 -0300, Anton Antimo wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my
    intuition says XEmacs started out with coloring? IIRC, Stallman or
    someone would have said that the idea was not properly designed.

    Why not start here <https://www.xemacs.org/Documentation/21.5/html/xemacs-faq_1.html#Q1_002e6_002e1>.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 13 20:58:01 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 13/08/2026 11:19 PM, Anton Antimo wrote:

    [...]

    Personally, I think Lisp people need -- well, need is a strong word, but >>> I'll go with it -- to get a little bit more behind the notion of practi- >>> cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de- >>> tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.
    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)
    Source:
    https://www.sbcl.org/manual/

    And herein lies the conundrum. I believe I took a quick glance at the manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have expectations of finding it in the first place.

    Try the ``executable'' keyword; you'll find this:

    --8<-------------------------------------------------------->8---
    Executable Delivery: The :executable argument to
    sb-ext:save-lisp-and-die can produce a "standalone" executable
    containing both an image of the current Lisp session and an SBCL
    runtime.
    --8<-------------------------------------------------------->8---

    Source:
    https://www.sbcl.org/manual/

    [...]

    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three
    dimensional game objects.

    What do you think?

    I never think about games, thankfully. I've played video-games from
    11
    to 14 years old, replacing them completely with UNIX, a great
    investment.

    By the way, have a look at these (broken) lines above. Your Mozilla Thunderbird is not knowing how to properly handle quotes. I once hacked
    it around to make sure it wouldn't mess up quotes like that, but it
    wasn't too obvious how to do it. (It's also Thunderbird that's making sometimes give too much vertical space and sometimes too little. USENET
    has traditionally used fixed-fonts. With this Thunderbird culture,
    you'll always violate that culture.)

    Economically speaking, if CL had more users, there'd be more books.
    I don't have much need for Common Lisp (strictly speaking) books
    myself. I'm not trying myself to read more books on the language.
    What I'm doing is writing more Common Lisp and reading more of it.
    What certainly helps me is for people to use it, which then
    indirectly asks for more books (but for the wrong reasons: the
    beginner often thinks that something new is required for him to
    invest his time; reading an old book seems like a waste of time for
    so many of them, but that's only because they're beginners and might
    be for the rest of their lives).

    Well, I don't only mean beginner books. I mean some of the more ad-
    vanced books as well, when it comes to C. Of course /Common Lisp Re-
    cipes/, and /The Common Lisp Condition System/ should be good examples
    that I'll get to read one of these decades. Here I'm thinking of Adam Tornhill's /Patterns in C/. There are even several more, some of which
    I've lost track of, because I believe they were only available as a PDF
    and I neglected to print them out.

    Right now I'm not inclined to cross post this to comp.lang.c, and ask if they'd be willing to fill in some of those blanks.

    Hm, as-is, there seems to be a /blank/ in my knowledge, when it comes to thinking of an equivalent book in Lisp. Specifically about these /patt- erns/, and how to use them.

    Perhaps there is no need? After all, the original patterns book in Java
    was all about working around deficiencies in the Java programming lang-
    uage, and maybe Common Lisp has few enough of those we don't care about
    a specific set of patterns?

    Or is this simply covered in /Common Lisp Recipes/ and I forgot?

    I have no idea. It'd be great to have more books on Lisp, but that'd
    take more writers and more readers too. Such is life. Looking on the
    bright side, I think Lisp is one of the easiest languages to read and
    there's more Lisp software out there that I could read likely in my
    lifetime. Who knows, maybe we'd learn more by reading source-code than
    by reading books? (A serious question.) Maybe it's a blessing we don't
    have too many books to read on this language. I propose we try out this possibility.

    Have a nice day, and Lisp well!

    Thank you! You too.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Fri Aug 14 00:11:51 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 13 Aug 2026 11:42:36 -0300, Anton Antimo wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my
    intuition says XEmacs started out with coloring? IIRC, Stallman or
    someone would have said that the idea was not properly designed.

    A bit more informative as to the details, from someone with first-hand knowledge: <https://www.jwz.org/doc/lemacs.html>.

    (He does describe the XEmacs account I linked to earlier as
    rCLpusillanimousrCY ...)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Thu Aug 13 17:16:06 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:
    Thank you for describing the matter. You must be the best one here to elaborate on the schism? Can you elaborate it more technically? For instance, there's font locking today on the GNU EMACS---was it done in a dramatically different way relative to LEmacs?

    I spoke with RMS about this at some length back in the day. I don't
    remember the specifics but yes it involved disagreements about the X
    interface. I do remember that he said that it was philosophically ok to
    fork a codebase if such a disagreement couldn't be solved. He
    considered that to be one of the virtues of free software.

    That is, he didn't find the XEmacs split to be morally objectionable,
    but he was somewhat disappointed that it had come to that.

    I'm not big on putting blames on personalities in a thing like this, but
    I would say RMS and JWZ can both be difficult. So putting both in the
    same "room" might not have worked out so well.

    I don't know how different GNU Emacs and XEmacs are from each other
    nowadays. I do know that GNU Emacs's X support has gotten fancier since
    those days.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Thu Aug 13 17:31:52 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    Hm, as-is, there seems to be a /blank/ in my knowledge, when it comes to thinking of an equivalent book in Lisp. Specifically about these /patt- erns/, and how to use them.

    Winston and Horn "Lisp" was a favorite way back in the day:

    https://en.wikipedia.org/wiki/LISP_(book)

    It was originally part of the book "Artificial Intelligence" but the
    Lisp part split off into a separate volume, per the Wikipedia article
    above.

    The thing is, CL's design makes some sense, but only up to a point.
    It's not holistic like Scheme, so don't expect too much consistency.
    CL's unifying purpose was to maintain some level of commonality with a
    bunch of incompatible predecessor Lisps of varying origin. It didn't
    try to run earlier dialects without modification, but it tried to keep
    the porting effort manageable, as I understand it. Old timers here will
    know more about this than I do. There are some good history documents
    around whose names I don't remember.

    In my case I found CLTL1 to be pretty understandable after first gaining
    an understanding of Lisp by reading through the Emacs Lisp interpreter
    source code (written in C) and mucking around with some Emacs Lisp code.
    The CADR manual was also enlightening, even though I never actually used
    a CADR or any other Lisp machine (I guess that's a sign of a deprived childhood). See:

    https://tumbleweed.nu/r/lm-3/uv/chinual.html

    As for Scheme, I think of it more as an assembly language for a cosmic
    sized computer, than as something for humans program much in directly.
    Others believe the opposite.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 13:42:08 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 7:58 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 13/08/2026 11:19 PM, Anton Antimo wrote:

    [...]

    Personally, I think Lisp people need -- well, need is a strong word, but >>>> I'll go with it -- to get a little bit more behind the notion of practi- >>>> cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer >>>> him- -- or her- -- self. There is very little attention paid to the de- >>>> tails of creating binaries to share with friends. And by this, I mean >>>> the parts of the programmer facing documentation. I believe the Steel >>>> Banks Common Lisp manual does not mention how to create binary executa- >>>> bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.
    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)
    Source:
    https://www.sbcl.org/manual/

    And herein lies the conundrum. I believe I took a quick glance at the
    manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have
    expectations of finding it in the first place.

    Try the ``executable'' keyword; you'll find this:

    --8<-------------------------------------------------------->8---
    Executable Delivery: The :executable argument to
    sb-ext:save-lisp-and-die can produce a "standalone" executable
    containing both an image of the current Lisp session and an SBCL
    runtime.
    --8<-------------------------------------------------------->8---

    Source:
    https://www.sbcl.org/manual/


    Please be patient with me. Here is a screenshot. I'm afraid the link
    is ridiculously long, and I don't use url shorteners anymore.


    https://www.dropbox.com/scl/fi/07asmp90gza39utr55wro/SBCL-manual-execu.jpg?rlkey=jd3tcevbchchpsge37xfmjh1j&st=pk2y5hvh&dl=0

    What I'm looking at here seems to be the word "execu" -- or the prefix
    of which -- not being found. Should I have continued to type the whole
    word? I thought this worked like Emacs' incremental search, and as I
    typed more characters, it would search longer words, until it wouldn't
    find what I've typed so far.

    Is this perhaps a matter of not using the right browser? I mean, what
    browser do the team players behind S.B.C.L. habitually use themselves?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 14:04:59 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 8:31 AM, Paul Rubin wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    Hm, as-is, there seems to be a /blank/ in my knowledge, when it comes to
    thinking of an equivalent book in Lisp. Specifically about these /patt-
    erns/, and how to use them.

    Winston and Horn "Lisp" was a favorite way back in the day:

    https://en.wikipedia.org/wiki/LISP_(book)

    It was originally part of the book "Artificial Intelligence" but the
    Lisp part split off into a separate volume, per the Wikipedia article
    above.

    Thank you. I've added both to my cart. Though I'm likely to just buy
    them next year or something. These bookstores have a nice shelf called
    /save for later/, but will sell to someone else when they run out of
    stock.


    The thing is, CL's design makes some sense, but only up to a point.
    It's not holistic like Scheme, so don't expect too much consistency.
    CL's unifying purpose was to maintain some level of commonality with a
    bunch of incompatible predecessor Lisps of varying origin. It didn't
    try to run earlier dialects without modification, but it tried to keep
    the porting effort manageable, as I understand it. Old timers here will
    know more about this than I do. There are some good history documents
    around whose names I don't remember.

    I once tried to get a hold of LeLisp and other older European Lisps, but
    was unable to, a few years ago. Maybe that situation has changed.

    I've since lost interest in all of these old[er] Lisp dialects, and
    stick to Common Lisp in the general, and the Steel Banks' implementation
    in particular these days.


    In my case I found CLTL1 to be pretty understandable after first gaining
    an understanding of Lisp by reading through the Emacs Lisp interpreter
    source code (written in C) and mucking around with some Emacs Lisp code.
    The CADR manual was also enlightening, even though I never actually used
    a CADR or any other Lisp machine (I guess that's a sign of a deprived childhood). See:

    I've read through some of the XEmacs internals. It's necessary to make loadable extensions in C. I'm not sure I gained much understanding of
    how to code Lisp during that adventure.


    https://tumbleweed.nu/r/lm-3/uv/chinual.html

    Thank you. I'm glancing at this now. It seems interesting at first
    glance, and I may add this to my entertainment reading section. I also
    found an interesting summary at


    https://cnbbooks.github.io/zylisp-guide/part1/01-intro/origins/zetalisp.html

    and please excuse the U.R.L. length. I quote.

    > ZetaLisp's innovations extended beyond Flavors to include proper
    > lexical closures, efficient vectors, stack groups for
    > coroutine-like control structures, locatives for low-level
    > memory access, rational numbers, multiple return values,
    > structures, the generalized assignment mechanism setf, and
    > advanced memory management through CDR-coding. The language was
    > "the Lisp dialect with the most influence on the design of
    > Common Lisp" according to multiple sources, with Flavors
    > evolving into CLOS (Common Lisp Object System). ZetaLisp ran on
    > dedicated Lisp Machine hardware with tagged architecture
    > enabling parallel type checking without performance penalties,
    > supporting applications from the Macsyma computer algebra system
    > to sophisticated AI research.

    And as I'm writing this, I don't know what this cnbbooks zylisp-guide
    is.


    As for Scheme, I think of it more as an assembly language for a cosmic
    sized computer, than as something for humans program much in directly.
    Others believe the opposite.

    Hmm, I guess that's not a bad way to describe Scheme. And follows natu-
    rally from the old S.I.C.P. lectures; which I may want to re-watch in
    the near future, as entertainment. There's only so much tolerance I
    have for the selection at the usual streaming services.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Fri Aug 14 07:14:34 2026
    From Newsgroup: comp.lang.lisp


    Ar an dara l|i d|-ag de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    On Tue, 11 Aug 2026 18:31:24 +0100, Aidan Kehoe wrote:

    If you use any emacs itrCOs hard to avoid Lisp. Emacs Lisp is not a paragon of good design nor of good implementation-- (aset
    (symbol-name nil) 0 ?\u0192) , (fillarray obarray 0) , anyone?--so
    the natural thing is to look around for something better. The
    consensus within XEmacs was that Common Lisp was better. On
    investigating, yes, it is.

    ItrCOs a museum-worthy spec. Needs updating to, at least support POSIX-type features that we take for granted nowadays.

    ItrCOs better than Emacs Lisp. (I admit, with RMS not as active, GNU Emacs including their Emacs Lisp, has made impressive progress over the last few years, but itrCOs still shaped by years of his technical decisions, and the development culture was shaped by him.)

    Even if the update process is manual, e.g. when IrCOm using Debian and migrating a server to a new VM, I do not actually want to spend my
    time working out with trial and error what invocation of certbot
    will allow me to put Letsencrypt certificates on a new server that
    already has Apache installed. (Spoiler; spin down Apache, use
    certbot --certonly, which spins up its own HTTP server.)

    But you need to be able to keep the certs up to date without having to
    shut down Apache (or whatever web server yourCOre using) each time.

    Trust the standard Debian packages to take care of this automatically.

    This wasnrCOt practical. In any event I wasnrCOt asking for help, just making the
    point that this is work that is not actually what I want to use my computer for.

    [...] I have never developed any web app from scratch in PHP. The only time IrCOve used it is to maintain existing code, or write plugins for existing code (WordPress, WooCommerce).

    As a language, its features read like a shopping list of sadness.

    Yep. And, of course, itrCOs one of the most popular programming languages around.
    Similarly, as far as I can tell the most used Lisp is AutoCAD Lisp. This is not the most full-featured or well-thought-through Lisp out there.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 14:28:42 2026
    From Newsgroup: comp.lang.lisp

    On 13/08/2026 12:31 AM, Stefan Ram wrote:
    tfb <tfb@work.it.out> wrote or quoted:
    A very long time ago, Lisp had many unique features. Today it has exactly >> one, but that feature is critical. It just seems weird to me to ignore its >> defining characteristic. Not wrong: weird.

    Reddit concluded that with macros they were now supposed to learn
    to read several entirely unique, personalized programming languages,
    and preferred to rewrite their system in Python.

    Python's wrappers and resource contexts give developers a way to
    pass executable blocks to functions or objects achieving what devel-
    opers often use macros for without exposing the chaotic power of
    full AST manipulation.
    The price for that is the need to rewrite the codebase in whatever
    dialect of Python is current. I've previously mentioned people ditch-
    ing Python because 2.7 happened; or rather didn't happen.

    And I've heard of instances of Python code becoming unPythonic at a
    3.n to 3.n+1 change. That's liable to escalate in the future.

    Another reaction to macros, in a Lisp code base, would simply be to not
    use them. Or remove them whenever found to be unnecessary. This is
    similar to the discipline needed to maintain a large C++ codebase, so
    it's not like this /social problem/ is unique to Lisp. Nor unknown in
    the industry.

    There are other downsides of choosing Python, which I'll not expand on
    in this fullowup. Suffice to say, that based on hard earned experience,
    it's a very bad programming language/environment to use in production.


    Have a nice day in comp.lang.lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Fri Aug 14 14:37:51 2026
    From Newsgroup: comp.lang.lisp

    On 12/08/2026 6:14 AM, Kaz Kylheku wrote:
    On 2026-08-10, Andreas Eder <a_eder_muc@web.de> wrote:
    On So 09 Aug 2026 at 05:26, Johann 'Myrkraverk' Oskarsson wrote:
    I've found the Common Lisp macro system annoying enough that I rarely
    use it. I'm OK with functions most of the time, and CLOS the rest of
    the time. And only resort to macros when I can't do anything else in
    the situation.

    That us exactly where it should be used - when there is no other way.

    I don't agree, because that amounts to macros never being used.

    Thank you for reading my mind. As it happens, you got it wrong, and I
    suggest you take another class in telepathy. At minimum, your license
    should be revoked, and you yourself subjected to a brutal interrogation
    by the /inquisition/ for misusing telepathy. I'm sure Eisenhorn is on
    the case.

    Anyway, what I meant to be getting at, is there are /patterns/ in Lisp
    that cannot be done with mere functions. I forgot exactly which pattern
    I last used in anger that was impossible to make a function, so I'll let
    you divine several examples. Have fun.


    It's never the case that there is no other way, because in place of
    any macro, you can write the expansion by hand.

    They can also be done by the text editor. XEmacs' skeletons come to
    mind.


    Please enjoy rewriting all your macros as skeletons, it should be a good exercise for you!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Fri Aug 14 06:47:23 2026
    From Newsgroup: comp.lang.lisp

    On Fri, 14 Aug 2026 07:14:34 +0100, Aidan Kehoe wrote:

    Ar an dara l|i d|-ag de m|! L||nasa, scr|!obh Lawrence DrCOOliveiro:

    [Common Lisp is] a museum-worthy spec. Needs updating to, at least
    support POSIX-type features that we take for granted nowadays.

    ItrCOs better than Emacs Lisp.

    Emacs Lisp at least has process-control features. Common Lisp is still
    full of baggage from before the prevalence of POSIX features that we
    take for granted now.

    Emacs Lisp, at least, is not burdened by that sort of baggage.

    But you need to be able to keep the certs up to date without having to
    shut down Apache (or whatever web server yourCOre using) each time.

    Trust the standard Debian packages to take care of this automatically.

    This wasnrCOt practical. In any event I wasnrCOt asking for help ...

    But you clearly need it, since you are just making work for yourself.

    As a language, [PHPrCOs] features read like a shopping list of sadness.

    Yep. And, of course, itrCOs one of the most popular programming
    languages around.

    I think the most innovative web applications are primarily being done
    with various forms of JavaScript these days, e.g. Node, Jamstack. Even
    Python can handle WebSockets, which PHP has a bit of trouble with.

    Similarly, as far as I can tell the most used Lisp is AutoCAD Lisp.
    This is not the most full-featured or well-thought-through Lisp out
    there.

    No macros, no lexical binding, suffer the Lisp syntax without the
    benefits ... can you say rCLworst of both worldsrCY?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Fri Aug 14 09:27:47 2026
    From Newsgroup: comp.lang.lisp


    Ar an tri|| l|i d|-ag de m|! L||nasa, scr|!obh Anton Antimo:

    Aidan Kehoe <kehoea@parhasard.net> writes:

    [...] My first degree was 1998-2002 and the professor (clearly taking shelter from the first AI winter) assigned the GNU Emacs manual as required reading for the first class. (This is, I understand, not typical.)

    Very atypical these days. Your first degree must have been Computer Science? So you got two degrees. Having a degree or not in such areas,
    I think that understanding the fundamentals of computers and programming
    is a pretty good skill these days. There might be other areas I miss
    for sheer lack of wisdom here.

    Certainly helpful when IrCOm making LAN changes or switching the practice management software to a new server and can do it on the weekend, rather than close down the place for a day.

    To be honest the fundamentals are not the biggest help; it is the experience debugging things and having a feel for what the underlying problem is likely to be, that allows you to prioritise investigating one plausible cause over another.

    I took a ``programming 102'' engineering class a few years ago in which
    the professor offered us a ZIP package containing the GNU EMACS set up
    with Python. Students on the first day of class protested against their ``programming 101'' (a Python primer) saying it was essentially useless
    with no real-world anything (which I fully agree: that course's real objective was to teach us the syntax of Python [with no OOP, which is
    the job of ``programming 102'']).

    The professor replied saying he would present us with some illustrations
    of real-world stuff. To my surprise, one of these things was the GNU
    EMACS. His EMACS came with all of its default configuration but some additional ones for people to run Python and ESHELL. (To run it, we'd double click on a icon on the desktop.) Students were welcome to ignore
    it all and use Python's IDLE or whatever, which I think 99% of them did. What students couldn't ignore, which was cool (lol), was that the way to turn in homework was through fossil. The professor introduced us to
    fossil in another lecture, saying he chose fossil over git due to
    slightly greater simplicity (compared to git, which I couldn't quite
    see). I was likely the one exception that didn't struggle with
    fossil----I had never heard of it until then, but I've been using git
    for years.

    I hadnrCOt come across it. Anything the SQLite people do or use tends to be excellent, which is a good sign.

    Anyway, after these lectures, he went on with the course, which didn't work very well at all because I think after the GNU EMACS and fossil most students had already given up on him---there were many other professors teaching the same course in a way that it had a lot less new things to learn.

    At that point XEmacs was a better editor so after using GNU Emacs for
    a few weeks I switched to XEmacs. It still meets my needs and I have
    no plan to switch away from it.

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition
    says XEmacs started out with coloring? IIRC, Stallman or someone would
    have said that the idea was not properly designed. I can't recall, but
    I might research the question and report back here.

    I wasnrCOt around then. In 1998 the GNU Emacs GUI was remedial and there was a lot more momentum to XEmacs development and engagement. These have both changed in favour of GNU Emacs.

    [...] If you use any emacs itrCOs hard to avoid Lisp. Emacs Lisp is not a paragon of good design nor of good implementation-- (aset (symbol-name nil) 0 ?\u0192) , (fillarray obarray 0) , anyone?--so the natural thing is to look around for something better. The consensus within XEmacs was that Common Lisp was better. On investigating, yes, it is. But, XEmacs needs work, no-one else is doing it, so my software work these days is C with a very Common-Lisp-oriented Emacs Lisp.

    I tried the code above on the GNU EMACS. The first crashes it
    immediately. The second doesn't seem to do its job anymore, throwing a
    type error. They must have created a new type called obarray. Saying (type-of obarray) produces obarray, while fillarray expects a vector.

    Ah, theyrCOve improved that, then. Unclear to my why they didnrCOt just use a hash
    table. Gerd M||llman implemented the right thing, CL packages, here: https://github.com/gerd-moellmann/emacs-with-cl-packages . Stallman hated that, as is his way, so thatrCOs probably why theyrCOve done what they did. ItrCOs on my
    todo list (and already started) to integrate GerdrCOs code into XEmacs.

    We currently just use a hash table for obarray, but this has the disadvantage that you can #'clrhash on it, which has the same problem as #'fillarray.

    (I certainly donrCOt want to have to migrate well-written PHP of twenty years ago that carefully wrapped access to a database using then-best-practice APIs because those APIs are unmaintained and
    removed, but that is entirely on me, we all know PHP is terrible, and
    I knew it then. But Debian shouldnrCOt be terrible, and in the grand scheme of things it isnrCOt terrible.)

    What did you write 20 years ago?

    Just a blog, some utility code to backup my pinboard.in account, and allow 403 redirects to the underlying URL when I supply a combination of tags from there to a script on my server (I find this means I donrCOt need to port my local bookmarks from machine to machine), and code to access a copyrighted German dictionary whose entries I had extracted from a CDROM. (I was living in Germany at the time and my German was not where it is now.)

    That's indeed PHP's prime time. I know the language. I used it seriously back then as well. I never went into PHP 4, remaining in PHP 3 for as long as I could until I gave up on PHP completely---I've always appreciated language stability.

    Yep, itrCOs very valuable. Though *very* tempting as a language developer to deprecate then remove things.

    [...] And speaking of Medicine, how is it disrespectful these days as well, but I won't digress on this (and it's perhaps just something that plagues the entirety of society).

    What do you mean? Respect towards and from medicine varies by
    country. Doctors are regularly assaulted in India by family members of patients unhappy with the patientsrCO care. I get Christmas presents.

    It is indeed. If my sources are correct, in the United States (for example), we get deaths due to medical error top ranked---I don't mean
    top 1st, but highly ranked (top 3 a while ago?).

    Preventable deaths are mostly diet, exercise, smoking, public health related, together with easy access to a GP.

    I have plenty of US tourists who attend me, and I am impressed by the technical interventions done for previous acute issues they have had. Diet, exercise and easy access to a GP are often not great.

    But what I had meant was that I get the feeling from hearing from the population that the attention and time doctors spend with patients now
    has been greatly reduced; that doctors are often rude, get easily
    irritated and so on. That then makes me think they might be working too much.

    My understanding (though I havenrCOt worked in the US) is that the insurance companies over the last couple of decades introduced pre-authorisations and other overhead that effectively decreases the amount reimbursed for the time spent dealing with the patients. This meant that it was no longer (usually) practical to set up on your own, since the administration work and staff to deal with the insurance companies needed to be amortised over multiple clinicians. So most doctors over there are now employed, and if yourCOre expected
    to work at the intensity of a business owner with little to no financial upside for working harder, itrCOs easy to get irritated. And, in my experience, it is easier to be happy when yourCOre making most of the decisions that influence your
    work environment yourself.

    I in fact see a parallel with programmers: in the typical company, the typical programmer can be slightly arrogant, easily irritated, the explanation for which might be too much work, not very competent and not living very joyful days. So in the end I don't see anything specific to Medicine, but something much larger. I'm a student at a large university---what can I say about professors? They're very easily offended with students' lack of interest; they inadvertently and incorrectly take a lot of things personally; my overall conclusion is that they're not doing very well health-wise, not living very joyful days (they might miss days in which there was more glamour in the profession, when they feel they would be better regarded). Something like that.

    IMO a lot of the Computer Science professors were under-socialised and had no fundamental interest in dealing with people. The lecturers in medicine (who were normally working doctors) were much more socially skilled and teaching came easier to them.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Fri Aug 14 01:33:41 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@parhasard.net> writes:
    ItrCOs better than Emacs Lisp. (I admit, with RMS not as active, GNU Emacs including their Emacs Lisp, has made impressive progress over the last few years, but itrCOs still shaped by years of his technical decisions, and the development culture was shaped by him.)

    Emacs Lisp grew a lot in the past decade or two mostly because computers
    became a lot bigger. Remember Emacs was originally written on a VAX
    11/750 with (iirc) 2MB of memory and < 1/1000th the speed of a modern
    PC. Emacs itself was said, in a not entirely nice way, to stand for
    "eight megabytes and constantly swapping". So it's shaped by the
    technical constraints of historical hardware as well as by anyone's
    personal development approach.

    CL has some weirdness about stuff like file and network operations
    because of its own history, which was to abstract over various other
    Lisps of the 1970s-80s, which were mostly not POSIX hosted. Yes it's
    dated, but it still has attractions or else we wouldn't be here.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Fri Aug 14 01:52:39 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    > ZetaLisp's innovations extended beyond Flavors to include proper

    I think that paragraph is a historical misstatement: Zetalisp was
    branched from Lisp Machine Lisp (developed on the CADR) but there were
    other branches too. Most of the stuff in the paragraph was present on
    the CADR, i.e. before the branches happened or the name Zetalisp was
    coined. Zetalisp eventually became the most advanced of the branches
    but that was later. RMS would throw a fit if he saw himself listed as a developer of Zetalisp ;).

    Zylisp looks partly interesting, partly meh.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 10:25:46 2026
    From Newsgroup: comp.lang.lisp

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    IrCOm sure they do have their own extensions to make up for the
    deficiencies of Common Lisp. But then, they are no longer rCLCommonrCY,
    are they?


    Right, right, in just the same way all the other implementations of the
    Python standard implement identical sets of extensions to it ... oh, wait.

    I have to ask: are you consciously trying to pick the most stupid thing to
    say at any point?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Fri Aug 14 03:27:13 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    Right, if the language you already has supports every construct anyone
    might ever want to do anything, then nobody needs macros.

    No language has 100% of constructs anyone might ever want. If it has
    90% and requires a little stretching for the other 10%, it's doing ok.
    Lisp starts maybe 50% and uses macros to make up for the rest. Like
    where other languages have "=" as a generic assignment operator, Lisp
    has a complicated setf macro that handles part of the semantic analysis
    phase of a more traditional compiler.

    Do they say that? Which ones? This one thinks that domain-specific
    and application-specific languages are useful and thinks that
    languages with facilities which allow the simple incremental
    construction of such languages are therefore also useful.

    There's more to language than syntax, even if you find syntax important.
    E.g. some users want fancy type systems including for their DSL's.
    There are Lisp dialects that have that, but it's unfeasible in CL other
    than through the Turing tarpit of macros.

    I've mentioned this link before and it is pretty good:

    https://www.cs.kent.ac.uk/people/staff/dat/miranda/wadler87.pdf
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 10:27:55 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> wrote:

    Person A: 'The Emacs schism was not fundamentally technical'

    Person B: 'Can you elaborate it more technically?'

    Can you see the problem here?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 10:27:56 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    And herein lies the conundrum. I believe I took a quick glance at the manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have expectations of finding it in the first place.

    Um, section 2.4.3 Generating Executables, in the manual. It's not quite in
    the first page on my screen, but, ad they say, RTFM.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp,comp.lang.c,comp.os.linux.misc on Fri Aug 14 12:26:56 2026
    From Newsgroup: comp.lang.lisp

    (Given I'm commenting on the content of the online manual on a Linux
    system, I'm adding and followingup-to comp.os.linux.misc.)

    On 2026-08-11, Lawrence DrCOOliveiro wrote:

    On Mon, 10 Aug 2026 17:41:30 -0300, Anton Antimo wrote:

    For select (called unix-fast-select in SBCL), see sb-unix.

    select(2) is considered an archaic way of doing things these days,
    because of its ABI limitations. The modern way is poll() <https://manpages.debian.org/poll(2)> (POSIX) or even epoll() <https://manpages.debian.org/epoll(7)> (Linux-specific).

    The online manual here (a GNU/Linux system) says:

    "poll, ppoll - wait for some event on a file descriptor"

    Perhaps that should be rewritten. Reading further, it's not singular,
    but that description with "*A* file descriptor" does make it sound like
    poll is not a suitable replacement for select.
    --
    Nuno Silva

    (Not subscribed to comp.lang.c)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp on Fri Aug 14 12:46:45 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-14, Johann 'Myrkraverk' Oskarsson wrote:

    On 14/08/2026 7:58 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 13/08/2026 11:19 PM, Anton Antimo wrote:

    [...]

    Personally, I think Lisp people need -- well, need is a strong word, but >>>>> I'll go with it -- to get a little bit more behind the notion of practi- >>>>> cality. I mean, the Steel Banks Common Lisp is fine, but many others >>>>> aimed at beginners are exclusively geared towards facing the programmer >>>>> him- -- or her- -- self. There is very little attention paid to the de- >>>>> tails of creating binaries to share with friends. And by this, I mean >>>>> the parts of the programmer facing documentation. I believe the Steel >>>>> Banks Common Lisp manual does not mention how to create binary executa- >>>>> bles? I believe I learned that from /Stack Overflow/ which everyone >>>>> here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.
    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)
    Source:
    https://www.sbcl.org/manual/

    And herein lies the conundrum. I believe I took a quick glance at the
    manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have
    expectations of finding it in the first place.

    Try the ``executable'' keyword; you'll find this:

    --8<-------------------------------------------------------->8---
    Executable Delivery: The :executable argument to
    sb-ext:save-lisp-and-die can produce a "standalone" executable
    containing both an image of the current Lisp session and an SBCL
    runtime.
    --8<-------------------------------------------------------->8---

    Source:
    https://www.sbcl.org/manual/


    Please be patient with me. Here is a screenshot. I'm afraid the link
    is ridiculously long, and I don't use url shorteners anymore.

    https://www.dropbox.com/scl/fi/07asmp90gza39utr55wro/SBCL-manual-execu.jpg?rlkey=jd3tcevbchchpsge37xfmjh1j&st=pk2y5hvh&dl=0

    (Please consider changing www. to dl. when sharing dropbox links. It
    seems this one needs the rlkey GET parameter, but it still works as a
    direct link once changed to "dl.".)

    What I'm looking at here seems to be the word "execu" -- or the prefix
    of which -- not being found. Should I have continued to type the whole
    word? I thought this worked like Emacs' incremental search, and as I
    typed more characters, it would search longer words, until it wouldn't
    find what I've typed so far.

    You have "Whole words" enabled, uncheck that.

    Is this perhaps a matter of not using the right browser? I mean, what browser do the team players behind S.B.C.L. habitually use themselves?
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp on Fri Aug 14 12:52:47 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-13, Johann 'Myrkraverk' Oskarsson wrote:

    On 14/08/2026 12:14 AM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.

    In practise the answer is 'raco exe' which makes an executable. You have
    to have a suitable main function &c, but it's not hard.

    Well, aside from technically correct answers, I was talking about the culture. In my recollection, and by now I guess that would be an old Racket,* there was no emphasis on creating binaries in the Racket intro- ductory material, nor user interface. It's more like, here's a pro-
    gramming language, use it!

    And until binaries are habitually made with Racket, and by that I mean production binaries, with code signatures for the Microsoft and fruit
    vendor platforms, that's not likely to change.

    For students, it'd perhaps be much more valuable to teach them how to
    disable anything that nags if the resulting binary doesn't carry a
    signature made with a certificate from the CA system, especially when it
    needs to be a more expensive certificate and/or requires ID validation.

    And perhaps teach them about more suitable means to sign executables,
    like OpenPGP, that actually is based on a web of trust and not on some centralized issuer?

    Best wishes, and happy Racketteering!

    Running afoul of RICO, are we? :-P

    * Pun totally intended afterwards.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.emacs.xemacs on Fri Aug 14 08:16:12 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 14/08/2026 3:52 AM, Anton Antimo wrote:
    tfb <tfb@work.it.out> writes:

    Anton Antimo <anton@safunu.org> wrote:

    I never ran XEmacs, but I watched a documentary once that said that
    XEmacs was born out of something to do with font locking---my intuition >>>> says XEmacs started out with coloring? IIRC, Stallman or someone would >>>> have said that the idea was not properly designed. I can't recall, but >>>> I might research the question and report back here.

    The Emacs schism was not fundamentally technical: it happened because
    cooperation with RMS is impossible. Lucid needed some features in what
    would have been Emacs 19 to support a programming environment (for C++, I >>> think, not Lisp, despite them being Lucid) and were willing to donate the >>> time to implement them & donate the results (remember Emacs 18 had an
    entirely minimal interface to X: equivalent to running it in a terminal
    emulator). And ... cooperation with RMS turned out to be impossible. So >>> LEmacs happened, which became XEmacs after Lucid died.

    I wasn't there, but I was around a few months later and perhaps before the >>> split was really final. I perhaps no longer have the trove of emails from >>> the split: they made depressing reading.

    (If you're thinking of posting a followup explaining why cooperation with >>> RMS is, in fact, possible, just ... don't, please.)

    Thank you for describing the matter. You must be the best one here
    to elaborate on the schism? Can you elaborate it more technically?
    For instance, there's font locking today on the GNU EMACS---was it
    done in a dramatically different way relative to LEmacs?

    Just to chime in for the newcomers who don't know about this publicly available summary.

    https://www.xemacs.org/Documentation/21.5/html/internals_4.html

    And.

    https://www.xemacs.org/About/XEmacsVsGNUemacs.html

    That said, I do hope tfb is willing to write out a technical summary, or
    even a social one like in the first link.

    Thank you. I'm still reading, but that's likely enough---let's free tfb
    from the task (unless we have further questions).

    Note that since then, GNU Emacs did indeed add loadable modules in C.

    Adding comp.emacs.xemacs to the discussion, because that group shouldn't
    be empty all the time.

    Yes---the USENET is meant for users, so let's use it.

    Happy text editing in XEmacs!

    Writing this from

    GNU Emacs 30.2 (build 2, x86_64-unknown-linux-gnu, GTK+ Version
    3.24.50, cairo version 1.18.4) of 2026-01-19.

    Have a good day.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Fri Aug 14 08:20:47 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    [...]

    LLMs [I agree it's a stupid name] are hidden node models having tens
    of thousands (or more) of nodes, and many millions of inputs [and
    weights and offsets]. You can't build one without a supercomputer.

    On the names. I don't think LLM is such a stupid name---it describes
    what it is (at least for now, since sizes evolve over time). But isn't
    ChatGPT even sillier? Who came up with the idea of tagging GPT on the
    name of the thing? I suppose the idea was to make it very clear it was
    not a person? In that case, they shouldn't be done like it's always
    been done: GPT meaning [G]PT is not a [P]erson, [T]hanks (for asking)! (Lol---I'm so good at this.)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Fri Aug 14 08:04:54 2026
    From Newsgroup: comp.lang.lisp

    C||il|!n Niocl|is|!n Glost|-ir <thanks-to@Taf.com> writes:

    I suppose that a typical medic is of a different personality type than
    a typical computer programmer. I do not think that being overworked is
    the overriding cause of the behavior of medics and programmers.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    I'd fully agree that it's not the root cause for sure. A depressed
    person could plunge into work, say, but could plunge into alcohol or
    other as well. Don't take all the vagueness I wrote too deeply.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 12:16:35 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:

    No language has 100% of constructs anyone might ever want. If it has
    90% and requires a little stretching for the other 10%, it's doing ok.

    No single language has 1% of constructs anyone might ever want. In fact
    there is no number which is small enough that any single language contains
    that proportion, because the number of such constructs is not bounded
    above. If you think it is, then I am sorry for you.

    A 'single language' here means 'a language without functions whose domains
    and ranges are programs', and in particular functions whose domain is
    programs written in some other language and whose range is programs written
    in the base language. Such 'single languages' don't really exist because
    you can always use them to write such functions. And the fact that people endlessly do something equivalent to this should be a hint.

    A weaker definition of 'single language' would be a system where facilities
    for creating functions which do this are not part of the base language.
    Common Lisp is not a single language; the Scheme standards were for a long
    time although probably no implementations were. The Scheme standard no
    longer is. The C standard is(unless it's changed a lot).


    There's more to language than syntax, even if you find syntax important.
    E.g. some users want fancy type systems including for their DSL's.
    There are Lisp dialects that have that, but it's unfeasible in CL other
    than through the Turing tarpit of macros.


    So you mean 'CL can't do this thing if you disallow the facility it has to enable you to do this thing and many other things'. Well, yes that's
    vacuous but true.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 12:30:01 2026
    From Newsgroup: comp.lang.lisp

    Nuno Silva <nunojsilva@invalid.invalid> wrote:

    For students, it'd perhaps be much more valuable to teach them how to
    disable anything that nags if the resulting binary doesn't carry a
    signature made with a certificate from the CA system, especially when it needs to be a more expensive certificate and/or requires ID validation.


    On the Mac, executables built with raco exe don't need signatures at least
    when they're command-line tools and being used on the machine where they
    were created (and perhaps by the user who built them). I don't know about graphical programs but I suspect not then either.

    Students who are trying to ship executables rather than source code ...
    well, they can learn how to do that.

    This whole thing is just another brick in the wall of reasons people give
    not to use Lisp. Somehow that wall never has any bricks at all for Python.
    You might think people are making things up, mightn't you?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp on Fri Aug 14 13:30:43 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-14, Anton Antimo wrote:

    George Neuner <gneuner2@comcast.net> writes:

    [...]

    LLMs [I agree it's a stupid name] are hidden node models having tens
    of thousands (or more) of nodes, and many millions of inputs [and
    weights and offsets]. You can't build one without a supercomputer.

    On the names. I don't think LLM is such a stupid name---it describes
    what it is (at least for now, since sizes evolve over time). But isn't ChatGPT even sillier? Who came up with the idea of tagging GPT on the
    name of the thing? I suppose the idea was to make it very clear it was
    not a person? In that case, they shouldn't be done like it's always
    been done: GPT meaning [G]PT is not a [P]erson, [T]hanks (for asking)! (Lol---I'm so good at this.)

    One I've seen used that's adequate is "Generative Autocomplete".

    I'd also propose "GIGO As A Service".
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ram@ram@zedat.fu-berlin.de (Stefan Ram) to comp.lang.lisp on Fri Aug 14 12:49:29 2026
    From Newsgroup: comp.lang.lisp

    Nuno Silva <nunojsilva@invalid.invalid> wrote or quoted:
    One I've seen used that's adequate is "Generative Autocomplete".

    The first "L" in "LLM" is what distinguishes those LLM from
    LMs which can be described as "glorified autocompleters".
    LLMs have additional features like emergent efficient internal
    representations of abstract concepts and their relations.

    For one example, today's chatbots can follow meta-constraints
    (like, "Summarize this article in 50 words"). A raw model
    would just continue writing more text similar to the prompt.

    LLMs have recently solved some math problems human mathematicians
    were not able to solve for decades. There is no way you can subsume
    such behavior under "autocomplete".


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Fri Aug 14 12:51:30 2026
    From Newsgroup: comp.lang.lisp

    I think it's worth understanding what macros actually mean.

    Most programming languages are dictatorships: a small, usually
    self-elected, self-important group of people designs a language, and
    thousands or millions of serfs have to suffer the consequences of their choices.

    Sometimes there is a pretense of some limited form of democracy: perhaps
    you, as a mere serf, can join the politburo and have a vote on what happens
    to the language. Sometimes this involves a payment to some nebulous
    standards organisation. Sometimes you can comment on suggested changes; sometimes people might listen to those comments. Sometimes the politburo
    is not largely made up of representatives (either explicit or implicit) of
    huge corporations who care not one jot about your interests.

    Changes, when they happen at all, take years. The language is ossified
    almost as soon as it exists.

    Almost always, for large systems, there will be tools built on top of the ossified substrate language which allow people to write programs in a way
    which actually matches their problem domain. Those tools are, in fact, *programming languages*, although they're usually implemented in an ad-hoc
    way by people who don't even realise that what they are doing is designing
    a programming language. They are therefore predictably horrible. If you
    have not used such an ad-hoc language you probably have not worked on a
    large system.

    Sometimes people make a better decision: they take an existing (usually dynamically typed as basically nobody likes static typing in the real
    world, usually either not compiled or dynamically compiled) language which
    has a good interface to the ossified substrate and expose functionality
    written in the ossified substrate to the more flexible surface language.
    NumPy and all its relations are the canonical example of this.

    That's at least better than the thing implemented using m4 on top of
    Fortran or whatever. But the thing written in m4 on top of Fortran is
    *still* better than using Fortran directly (and this is not because
    Fortran, today, is a bad language, which is is not, it's because it's an ossified language).

    Quite often what happens is that user or group of users of a language gets
    so fed up with this process that they design a new language which better
    meets their needs, perhaps starting with one of the ad-hoc languages above.
    That language then develops its own self-important politburo, becomes ossified.

    Recurse.

    Lisp chose something else. Lisp chose not to be a dictatorship, but to
    treat its users as adults capable of making their own decisions: decisions which were as good as the decisions of the politburo if not better.
    Decisions which, certainly, relfected the needs of the users making the decisions rather than some distant observer.

    Lisp looked at what *actually happens* in the world rather than in the
    heads of the politburo members, and it saw that what happened was the
    endless invention of new languages, either for specific problem domains, or just because the existing languages were so terrible. And it said, 'OK,
    let's make that a feature, not something you have to fight your way
    towards. Let's build a language whose defining feature is that it lets you build languages. Let's allow it to let you build languages
    *incrementally*, rather than putting some enormous barrier in your way. So
    you can take an existing language and define some extensions to it, and
    those extensions wil have exactly the same status as the original language does.'

    If you disagree with the decisions of the politburo you don't have to wait
    five years for the members to die and the decision to change, you can just
    make the system do what you want, today.

    Lisp understood that this means you have to make some compromises. The
    most significant is that the syntax of the language must have very low commitment to the semantics. That makes the language rather austere, but
    it means that you, the user of the language, get to say what the semantics
    is, without having to jump through some huge ring of fire and getting
    burned in the process.

    Lisp is a system built by people who understand how utterly stupid the
    claim that any programming language contains 90% of all the constructs
    anyone will ever need is.

    Lisp is a democracy. It is perhaps more than a democracy: it either is or
    is close to an anarchy. Anarchies obviously work only if their citizens
    are actually adults and if they are willing to cooperate with one another. But, well, Lisp assumes you are. If you're not an adult, or if you can't
    deal with cooperating with other people in the design of the language
    you're going to use, or if you like someone telling you what to do then,
    well, do what thou wilt.

    Lisp understands that a consequence of this anarchy is that different
    groups of users working on different projects will end up using differing languages, or dialects (*a shprakh iz a dyalekt mit an armey un flot*, famously), and it also understands that *that's what happens anyway*,
    except the languages and dialects people end up using are usually things created using tools whose only datatype is the string.

    Like I say: if you're happy to live as a serf in a dictactorship, or if you feel you might become a dictator, then that's OK. But please, stay the
    fuck away from those of us who want not to be serfs or dictators, and who
    want to make our own decisions in a community of our equals.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 15 01:19:43 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 6:27 PM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    And herein lies the conundrum. I believe I took a quick glance at the
    manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have
    expectations of finding it in the first place.

    Um, section 2.4.3 Generating Executables, in the manual. It's not quite in the first page on my screen, but, ad they say, RTFM.


    You sir tfb, may get off your arrogant horse, remove the prick from your
    arse hole, stick it down your throat, then print out

    Message-ID: <SUxfS.292910$aXr.34899@fx18.ams4>

    and eat it!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 15 01:33:32 2026
    From Newsgroup: comp.lang.lisp

    On 14/08/2026 7:52 PM, Nuno Silva wrote:
    On 2026-08-13, Johann 'Myrkraverk' Oskarsson wrote:

    On 14/08/2026 12:14 AM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    If I'm not mistaken, we also have this problem with Racket. Racket is >>>> aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.

    In practise the answer is 'raco exe' which makes an executable. You have >>> to have a suitable main function &c, but it's not hard.

    Well, aside from technically correct answers, I was talking about the
    culture. In my recollection, and by now I guess that would be an old
    Racket,* there was no emphasis on creating binaries in the Racket intro-
    ductory material, nor user interface. It's more like, here's a pro-
    gramming language, use it!

    And until binaries are habitually made with Racket, and by that I mean
    production binaries, with code signatures for the Microsoft and fruit
    vendor platforms, that's not likely to change.

    For students, it'd perhaps be much more valuable to teach them how to
    disable anything that nags if the resulting binary doesn't carry a
    signature made with a certificate from the CA system, especially when it needs to be a more expensive certificate and/or requires ID validation.

    That would certainly help me. I have repeat nags because my self made
    binaries get modified by CL.EXE when it decides it's a good idea to incrementally link. I think that's not related to signatures, though I
    don't know. But that's also not a discussion for comp.lang.lisp, since
    as far as I know, nobody uses CL.EXE to link Common Lisp.

    That said, have you ever thought to put your own self signed certificate
    into the system? I did that once, when testing H.T.T.P.S. validation on Windows 10 development system. In my tests, the new self signed /system certificate/ just worked. Albeit, I did not do that for code signing.

    I believe that would be an excellent second semester exercise, for
    webservers built on top of Common Lisp. My preference is Hunchentoot,
    though I don't recall ever using it directly with encryption. I usually
    leave that to a front-end Apache, and Apache also runs on Windows.
    There used to a set of binaries done by Microsoft, I believe, and I'm
    not sure who is now making Apache binaries for the eleven Windows, and
    I'm not looking it up since it's outside the scope of comp.lang.lisp.

    So, for people with more experience in eleven Windows than I have, how
    would one create a self signed certificate, start a webserver with
    Hunchentoot -- or another Common Lisp framework -- and encrypt the conn-
    ection with that very same self signed certificate, and have it work in
    regular browsers because it's also part of the system's roots of trust?

    I mean, I did that last step on my own, I'm sure other people can figure
    that out too. /Never mind I forgot how to do it/.


    And perhaps teach them about more suitable means to sign executables,
    like OpenPGP, that actually is based on a web of trust and not on some centralized issuer?

    There are also social issues in the /web of trust/, but we don't need to discuss all of that here in comp.lang.lisp.


    Best wishes, and happy Racketteering!

    Running afoul of RICO, are we? :-P
    No, I'm not so "lucky" to get payments for other people's criminal acti- vities. Do you?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Fri Aug 14 12:03:18 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    No single language has 1% of constructs anyone might ever want.

    If I can code fluently in a language, that is, I can think entirely
    about the application-level problem I'm trying to solve and not putting
    much effort into choosing language constructs, then it's supplying 100%
    of what I want at least at that moment. That's great.

    If I have to sometimes stop and think about language constructs and come
    up with something that works but isn't entirely natural, but this
    doesn't happen too often, I'm still satisfied. That's the 90% that I
    mean.

    If you're saying that even CL only has 1%, then what's so great about
    CL? Do you really think you can fix the other 99% with macros? That
    seems unrealistic.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Fri Aug 14 12:08:15 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    Sometimes there is a pretense of some limited form of democracy: perhaps
    you, as a mere serf, can join the politburo and have a vote on what happens to the language.

    I haven't seen this url in a while but I guess it's time to post it
    again.

    https://www.marktarver.com/bipolar.html
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Sat Aug 15 10:01:05 2026
    From Newsgroup: comp.lang.lisp


    Ar an ceathr|| l|i d|-ag de m|! L||nasa, scr|!obh Paul Rubin:

    I haven't seen this url in a while but I guess it's time to post it
    again.

    https://www.marktarver.com/bipolar.html

    Thanks, glad to have read that.
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?Q?St=C3=A9phane?= CARPENTIER@sc@fiat-linux.fr to comp.lang.lisp on Sat Aug 15 12:58:27 2026
    From Newsgroup: comp.lang.lisp

    Le 14-08-2026, Paul Rubin <no.email@nospam.invalid> a |-crit-a:
    I haven't seen this url in a while but I guess it's time to post it
    again.

    https://www.marktarver.com/bipolar.html

    This url is not that news and I never saw it anywhere. Maybe you already
    sent it but as my ISP is broken, I don't see all the messages. So it's
    the first time I see this link.

    Many thanks for this.

    It tells me things about me which don't concern you. But it told me
    things about LISP which always eluded me.

    The fact is that LISP is almost never used is the real life. I know
    stump, nyxt and guix are LISP programs, but they represent less than
    0.[n]01% of users (I have no clue about the number of zeros represented
    by n here, but I'd say you can put a big number).

    Because if I know that LISP inspired a lot of things actually used in
    other programming languages, I know that nobody actually is learning
    LISP or computer history or anything that could explain why so many
    messages about LISP are shared compared with the number of people using
    it in a day to day basis.

    I'm not a programmer, but as computer science is allowing me to get
    things in my stomach (and as a French guy, what I put in my stomach is
    very important don't belittle that part), I have to follow up on what's happening in computer world. And I found a lot of things about LISP.
    Don't get me wrong. I find something like 1% of blogs/articles/whatever
    related to LISP. You can think it as small, but compared to what LISP is
    used in real life, it's huge. For each article/blog/whatever about C or
    C++ or COBOL, I can see at least ten articles/blog/whatever about LISP.
    And it's something.

    And I wondered about it from a long, long time. And this links explains
    a lot, thanks.
    --
    Si vous avez du temps |a perdre :
    https://scarpet42.gitlab.io
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anthk GM@anthk@disroot.org to comp.lang.lisp on Sat Aug 15 22:29:56 2026
    From Newsgroup: comp.lang.lisp

    On 2026-02-21, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Sat, 21 Feb 2026 12:25:06 +0100, Mario Rosell wrote:

    Just for fun. It seems like a pretty interesting language.

    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 donrCOt matter any more.

    And also, which particular Lisp do you want to learn? There are a
    number in common use today:

    * In the rCLLisp-2rCY camp: Emacs Lisp, SBCL
    * In the rCLLisp-1rCY camp: GNU Guile

    And thatrCOs just what I think of as the most notable ones.

    Guile and every other Scheme it's both lib, SRFI and R_RS incompatible
    with each other. CL with ANSI and the HyperSpec in the end
    can be ironicaly much smaller and compact.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 15 23:38:54 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 15 Aug 2026 22:29:56 -0000 (UTC), Anthk GM wrote:

    On 2026-02-21, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    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 donrCOt matter
    any more.

    And also, which particular Lisp do you want to learn? There are a
    number in common use today:

    * In the rCLLisp-2rCY camp: Emacs Lisp, SBCL
    * In the rCLLisp-1rCY camp: GNU Guile

    And thatrCOs just what I think of as the most notable ones.

    Guile and every other Scheme it's both lib, SRFI and R_RS
    incompatible with each other. CL with ANSI and the HyperSpec in the
    end can be ironicaly much smaller and compact.

    But is it any better for compatibility? What are these rCLANSIrCY and rCLHyperSpecrCY you talk about? Are they additional, shall we say
    informal, attempts at standards beyond Common Lisp?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sat Aug 15 19:44:38 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 13 Aug 2026 11:20:20 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    Personally, I think Lisp people need -- well, need is a strong word, but
    I'll go with it -- to get a little bit more behind the notion of practi- >cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de- >tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    Games with Gabe wrote* about that extensively in his YouTube video, at

    https://www.youtube.com/watch?v=IbDAmvUwo5c

    and I heartily agree.

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.


    The biggest issue I see with learning Racket is the sheer weight of
    its documentation. The reference is pushing ~1,800 pages and the user
    guide is twice that.

    It all could use a better [relational] index. The docs /are/ indexed,
    but if you don't know what keyword(s) to search for, it can be hard to
    find relevant information. Racket's preferred terminology is a mashup
    that stems from many sources.


    Racket isn't really aimed at students - its predescessor PLT Scheme
    /was/ aimed at teaching, but Racket is meant for general development.
    Racket is not a Scheme, but it is closely related.

    The main distribution bundle includes a large number of libraries and development tools, and additionally there are hundreds of user
    contributed packages.

    Racket /does/ remain popular for teaching because of the (relative)
    ease of creating DSLs having arbitrary [ie. non-sexpr] syntax that
    will compile to and interoperate with Racket. It is fairly easy to
    mix and match modules written using different DSLs.

    There are a number of subset "teaching languages", R5RS and R6RS
    Scheme implementations, and others, all implemented as DSLs.


    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three dimensional
    game objects.

    YMMV. I think the LAST thing we need is more games. Too many gamers
    need to pull their heads out of the game and go get a life.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sat Aug 15 21:12:15 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 13 Aug 2026 18:59:07 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:

    is it possible to use a truth maintenance system? Just curious, it would >probably take up too much space and time. Just a jtms is a lot of
    overhead. You could try to use an LTMS but we all know that this just
    leads to more wasted space and aggravation. I would think an ATMS would
    work; I dunno, I do not have a super computer or a billion dollars.

    The difficulty would be in interfacing it.

    The notion of "state" in a neural network is a matrix of numeric
    values. That state is distributed over some or all the nodes and
    there is no equivalent of, e.g., a simple string or a token value
    (enum, etc.), that could be passed to a separate oracle to check.

    Technically it is possible to generate such a token as an output, feed
    it to an oracle, and take the oracle's reply back as a new input ...
    but that could represent a significant bottleneck in processing.



    The big problem I see with LLMs is how they are being used.

    Neural networks essentially are fast pattern matchers ... but there is
    no getting around the fact that any matches are statistical, and their
    weight depends crucially on context.

    Likewise the "memory" of the NN is content addressed and matches in
    the memory are statistical. Recall that the "state" is a matrix - you
    put a matrix in, you get another matrix out. Making the "memory"
    larger [encoding more data] only serves to reduce the accuracy of any
    potential matches.

    YMMV. To my thinking, /generating/ output by "learned" associations
    from a fuzzy match of content addressed memory, and /relying/ on that
    output to be somehow accurate is kin to madness.



    I believe NNs absolutely do have a place - input matching for dispatch
    in rule based decision systems. Rule systems can do fuzzy logic, they
    can explain their reasoning when asked, they don't hallucinate, they
    won't lie to the user, and their rule sets can be modified to deal
    with new situations. Moreover, any NNs involved will be (relatively)
    small and easily retrained or replaced if necessary.

    The problem with rule systems mainly is user perception: since the
    advent of LLMs, rule based logic no longer is considered to be "AI".
    This is due to media propaganda and not real technical argument - but
    if you try to sell a rule based system, it is almost guaranteed that
    someone will want to know why you aren't using an "AI" instead.

    YMMV. If it's artificially constructed and it does something
    "intelligent" [for some definition], then I consider that it is AI.

    [Many years of OEM development has taught me that it can be difficult
    to challenge what users have read or heard in the media - no matter
    what the actual truth may be. The Vorlons say, "Understanding is a
    3-edged sword: your side, their side, and the truth." But sometimes I
    have to fight the urge to "educate" someone with a clue bat.]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Sun Aug 16 13:56:20 2026
    From Newsgroup: comp.lang.lisp

    Nuno Silva <nunojsilva@invalid.invalid> writes:

    On 2026-08-14, Anton Antimo wrote:

    George Neuner <gneuner2@comcast.net> writes:

    [...]

    LLMs [I agree it's a stupid name] are hidden node models having tens
    of thousands (or more) of nodes, and many millions of inputs [and
    weights and offsets]. You can't build one without a supercomputer.

    On the names. I don't think LLM is such a stupid name---it describes
    what it is (at least for now, since sizes evolve over time). But isn't
    ChatGPT even sillier? Who came up with the idea of tagging GPT on the
    name of the thing? I suppose the idea was to make it very clear it was
    not a person? In that case, they shouldn't be done like it's always
    been done: GPT meaning [G]PT is not a [P]erson, [T]hanks (for asking)!
    (Lol---I'm so good at this.)

    One I've seen used that's adequate is "Generative Autocomplete".

    That's a pretty good one.

    I'd also propose "GIGO As A Service".

    That's even better (but only as a nice joke).

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Sun Aug 16 15:26:14 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    I think it's worth understanding what macros actually mean.

    [...]

    I think that's a pretty good description of the whole thing. Thanks for writing and posting it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Sun Aug 16 15:29:04 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 14/08/2026 7:58 AM, Anton Antimo wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    On 13/08/2026 11:19 PM, Anton Antimo wrote:
    [...]

    Personally, I think Lisp people need -- well, need is a strong word, but >>>>> I'll go with it -- to get a little bit more behind the notion of practi- >>>>> cality. I mean, the Steel Banks Common Lisp is fine, but many others >>>>> aimed at beginners are exclusively geared towards facing the programmer >>>>> him- -- or her- -- self. There is very little attention paid to the de- >>>>> tails of creating binaries to share with friends. And by this, I mean >>>>> the parts of the programmer facing documentation. I believe the Steel >>>>> Banks Common Lisp manual does not mention how to create binary executa- >>>>> bles? I believe I learned that from /Stack Overflow/ which everyone >>>>> here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    See SBCL's sb-ext:save-lisp-and-die.
    (sb-ext:save-lisp-and-die #P"my-executable.exe"
    :toplevel #'my-package:main
    :executable t
    :save-runtime-options t)
    Source:
    https://www.sbcl.org/manual/

    And herein lies the conundrum. I believe I took a quick glance at the
    manual, looked at the able of contents, and even tried ctrl+f and the
    terms /binary/ or /binaries/, and /executable/, and found nothing.

    Being /technically/ in the manual does not help if one cannot easily
    find what one is looking for. It also doesn't help if one doesn't have
    expectations of finding it in the first place.
    Try the ``executable'' keyword; you'll find this:
    --8<-------------------------------------------------------->8---
    Executable Delivery: The :executable argument to
    sb-ext:save-lisp-and-die can produce a "standalone" executable
    containing both an image of the current Lisp session and an SBCL
    runtime.
    --8<-------------------------------------------------------->8---
    Source:
    https://www.sbcl.org/manual/


    Please be patient with me. Here is a screenshot. I'm afraid the link
    is ridiculously long, and I don't use url shorteners anymore.

    https://www.dropbox.com/scl/fi/07asmp90gza39utr55wro/SBCL-manual-execu.jpg?rlkey=jd3tcevbchchpsge37xfmjh1j&st=pk2y5hvh&dl=0

    What I'm looking at here seems to be the word "execu" -- or the prefix
    of which -- not being found. Should I have continued to type the whole
    word? I thought this worked like Emacs' incremental search, and as I
    typed more characters, it would search longer words, until it wouldn't
    find what I've typed so far.

    Is this perhaps a matter of not using the right browser? I mean, what browser do the team players behind S.B.C.L. habitually use themselves?

    I suggest you download the HTML, look inside with your text editor, then troubleshoot your browser later.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Sun Aug 16 15:06:40 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    [...]

    YMMV. I think the LAST thing we need is more games. Too many gamers
    need to pull their heads out of the game and go get a life.

    Lol. A man after my own heart.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Sun Aug 16 15:27:59 2026
    From Newsgroup: comp.lang.lisp

    St|-phane CARPENTIER <sc@fiat-linux.fr> writes:

    [...]

    I'm not a programmer, but as computer science is allowing me to get
    things in my stomach (and as a French guy, what I put in my stomach is
    very important don't belittle that part), I have to follow up on what's happening in computer world. And I found a lot of things about LISP.
    Don't get me wrong. I find something like 1% of blogs/articles/whatever related to LISP. You can think it as small, but compared to what LISP is
    used in real life, it's huge. For each article/blog/whatever about C or
    C++ or COBOL, I can see at least ten articles/blog/whatever about LISP.
    And it's something.

    Interesting.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 18 21:23:08 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Tue, 11 Aug 2026 18:35:58 -0000 (UTC), C||il|!n Niocl|is|!n Glost|-ir wrote:

    Is BASh on Windoze without its features on gratis operating systems?

    ItrCOs not about gratis, itrCOs about libre.

    Why do you damn people keep making this more difficult to understand.
    It's like when ESR started to use ``free software''(tm).

    :)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 18 21:26:17 2026
    From Newsgroup: comp.lang.lisp

    C||il|!n Niocl|is|!n Glost|-ir <thanks-to@Taf.com> writes:


    Is BASh on Windoze without its features on gratis operating systems?


    so long as there is no other encumbered software to do the job of the born again shell... Thank you!



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 18 21:35:37 2026
    From Newsgroup: comp.lang.lisp

    Kaz Kylheku <046-301-5902@kylheku.com> writes:

    On 2026-08-10, Paul Rubin <no.email@nospam.invalid> wrote:


    Suppressing evaluation is not the same thing as delaying evaluation.
    Macfros suppress evaluation so that the expression can be given an
    arbitrary meaning. One such meaning could be that evaluation is delayed,
    e.g. classic (delay <form>) macro, returning a promise. That's only a
    small point in a large universe.


    if you start to combine quote and quasi-q suck like `(list ',@ ) it gets ugly but hygenic-macros and late evaluation is one of the best features
    about lisp macros.

    This one is from zerox building problem solvers. I use this all the time. The `defun will delay evaluation while the ,(gen ... ) will force it. Not to mention the variable capture. TeX reminds me of this, but it get too
    compilated for me...

    (defun generate-body-procedure (pattern var body)
    (let ((newly-bound (pattern-free-variables pattern)) env docstring)
    (when var (push var newly-bound))
    (setq docstring (format nil "Body procedure when pattern: |~w| matches." pattern))
    (setq body (with-pushed-variable-bindings newly-bound (fully-expand-body body))
    env (append newly-bound
    (scratchout newly-bound *bound-vars*)))
    `(defun ,(generate-rule-procedure-name pattern "BODY") ,env
    ,docstring
    ,@body)))



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Aug 18 21:59:57 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    steve g <Sgonedes1977@gmail.com> wrote:

    I liked the idea of

    (with-current-readtable (xyz)
    ...)



    That is unuseful unless the body is a bunch of file compilations / loads.
    It should be apparent why.

    I don't follow.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Tue Aug 18 21:34:40 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> writes:
    but hygenic-macros and late evaluation is one of the best features
    about lisp macros.

    Lisp (CL) doesn't have hygienic macros, I thought. It took a long while
    for Scheme to standardize its version.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.edu.languages.natural on Wed Aug 19 13:03:53 2026
    From Newsgroup: comp.lang.lisp

    On 10/08/2026 6:49 AM, steve g wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    I try to keep in shape by reading books in languages I'm not using. Or
    converse with people about programming languages I don't use anymore,
    such as Pascal.

    I've managed to keep my French more or less intact, but could use a
    brush up on Danish, and of course German as I said. I'm sure I'll
    find something to inspire me to keep practicing German. After all,
    I'm struggling to read Asterisk and Obelisk in Latin.


    Best wishes, and happy language studies in comp.lang.lisp!


    Have you tried shortwave radio? You'll get all kinds of people talking different languages; not to mention it is rather entertaining.

    Dear steve g,

    No, I have not yet had the pleasure of playing with short wave radio,
    and I fear -- well, fear is a strong word, but I'll go with it -- I
    won't be able to add more hobbies in the short term.

    I have practiced a little bit of French in the form of short instant
    messages lately, but feel it's time to bring up the big guns and read
    a book, and start the video course I've had dormant for a long time.

    A friend offered to join me for French studies, but is a bit busy with
    work until later this month, so we plan to start the French then. Today however, I have made my own plans to start the Japanese course.

    And now I find myself writing in three line abstract paragraphs like
    Mild Shock, so I wonder if Mild Shock is also interested in studying
    languages, and which ones? I believe Mild Shock already knows German,

    but off hand forgot if he reads comp.lang.lisp, and comp.edu.languages. natural, which I added for the natural language discussion we're having.
    And on this last line, I noticed I failed to add Lisp to the discussion.


    Have a nice day in comp.lang.lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Wed Aug 19 17:53:54 2026
    From Newsgroup: comp.lang.lisp

    C||il|!n Niocl|is|!n Glost|-ir <thanks-to@Taf.com> writes:

    Steve G <SGonedes1977@GMail.com> wrote: |----------------------------------------------------------------------------|
    |"Aidan Kehoe <kehoea@parhasard.net> writes: |
    |[. . .] |
    | |
    |[. . .] |
    |[. . .] stallman [. . .] |
    |he is sometimes very prophetic. I recommend reading his essay on the |
    |right to read." |
    |----------------------------------------------------------------------------|

    Dear Mister Stephen G:

    I had bought many books. They have been robbed. I never got to read
    them :(

    same here.


    I do not write cursive writings. I am an Asperger autist.

    try and use a computer...

    A neighbor in Ireland recently alleged to me that children here are
    not taught to write handwriting at all - not just not cursive
    handwritings! Handwriting is too important to be neglected!

    yes; I think they use handwriting to help rehabilitate stroke patients.
    the nuero-plasticity of the brain thing. Pennmanship is neurologically
    based - there are no two people on earth who have the same handwriting
    (a long story...). this why they probably they are fearful of it.

    A journalist reported more than 3 years ago that a primary school
    which is located at the end of a route of circa 5.5 miles (according
    to
    HTTPS://WWW.ViaMichelin.com
    ) from me stopped using books! A primary school might be what you call
    an elementary school. The pupils in a primary school are younger than teenagers. A neighbor is related to a teacher here. This teacher
    laughed at a relative because this non-teacher relative uses a
    dictionary instead of Google.

    Last time I went to school every person could go to the library and rent/download
    the books. they got pissed off at me again.

    If I am on the bus; why not study for class? Waiting 2 hours to get to
    the library to study is assinine. The ebook revolution has happend. Let
    the students read for free!


    |----------------------------------------------------------------------------|
    |"[. . .] you |
    |did not even tell me to quit smoking cigarettes :)" |
    |----------------------------------------------------------------------------|

    Do not smoke :)


    I have quit smoking 5 times. Yes, I still smoke :)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Wed Aug 19 17:57:12 2026
    From Newsgroup: comp.lang.lisp

    bixbox <noreply@example.invalid> writes:

    Mario Rosell <mario@mariorosell.es> writes:

    Hello everyone!

    I want to learn Common Lisp, but I don't really know what resources to
    use.

    start using emacs. Read the tutorial and the built in manual. It does take
    some time, a couple of weekes until you feel like you are in a home.


    What did you all use to learn? Is that even relevant? Is this newsgroup
    active?


    absolutely.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Thu Aug 20 10:16:06 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> writes:

    bixbox <noreply@example.invalid> writes:

    Mario Rosell <mario@mariorosell.es> writes:

    Hello everyone!

    I want to learn Common Lisp, but I don't really know what resources to
    use.

    start using emacs. Read the tutorial and the built in manual. It does take some time, a couple of weekes until you feel like you are in a home.

    Yes, I think using the GNU EMACS for writing Lisp is definitely
    interesting. I would say that experienced Lisp writers also use
    paredit-mode. Have a look at some demo video of paredit-mode.

    But for learning Common Lisp, I think it makes little sense for you to
    study GNU EMACS Lisp. They're different.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Fri Aug 21 02:12:47 2026
    From Newsgroup: comp.lang.lisp

    On Tue, 18 Aug 2026 21:34:40 -0700, Paul Rubin
    <no.email@nospam.invalid> wrote:

    steve g <Sgonedes1977@gmail.com> writes:
    but hygenic-macros and late evaluation is one of the best features
    about lisp macros.

    Lisp (CL) doesn't have hygienic macros, I thought. It took a long while
    for Scheme to standardize its version.

    You are correct - Lisp doesn't have hygienic macros. However, Lisp
    macros can be made safe(r) [for some definition] through careful use
    of (gensym).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 22 02:28:49 2026
    From Newsgroup: comp.lang.lisp

    On 16/08/2026 7:44 AM, George Neuner wrote:
    On Thu, 13 Aug 2026 11:20:20 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    Personally, I think Lisp people need -- well, need is a strong word, but
    I'll go with it -- to get a little bit more behind the notion of practi-
    cality. I mean, the Steel Banks Common Lisp is fine, but many others
    aimed at beginners are exclusively geared towards facing the programmer
    him- -- or her- -- self. There is very little attention paid to the de-
    tails of creating binaries to share with friends. And by this, I mean
    the parts of the programmer facing documentation. I believe the Steel
    Banks Common Lisp manual does not mention how to create binary executa-
    bles? I believe I learned that from /Stack Overflow/ which everyone
    here in comp.lang.lisp knows is not a good place to learn how to do
    anything; not anymore.

    Games with Gabe wrote* about that extensively in his YouTube video, at

    https://www.youtube.com/watch?v=IbDAmvUwo5c

    and I heartily agree.

    If I'm not mistaken, we also have this problem with Racket. Racket is
    aimed at students, mostly, learning to code in Scheme, or the Scheme
    dialect that is Racket, but not how to create binaries to share their
    work with their loved ones who don't code.


    The biggest issue I see with learning Racket is the sheer weight of
    its documentation. The reference is pushing ~1,800 pages and the user
    guide is twice that.

    It all could use a better [relational] index. The docs /are/ indexed,
    but if you don't know what keyword(s) to search for, it can be hard to
    find relevant information. Racket's preferred terminology is a mashup
    that stems from many sources.


    Racket isn't really aimed at students - its predescessor PLT Scheme
    /was/ aimed at teaching, but Racket is meant for general development.
    Racket is not a Scheme, but it is closely related.

    The main distribution bundle includes a large number of libraries and development tools, and additionally there are hundreds of user
    contributed packages.

    Racket /does/ remain popular for teaching because of the (relative)
    ease of creating DSLs having arbitrary [ie. non-sexpr] syntax that
    will compile to and interoperate with Racket. It is fairly easy to
    mix and match modules written using different DSLs.

    There are a number of subset "teaching languages", R5RS and R6RS
    Scheme implementations, and others, all implemented as DSLs.


    So I believe we need more books about Common Lisp. Especially how to
    make production games in Common Lisp. I mean, the Steel Banks Common
    Lisp garbage collector cannot be worse than the old one in Unity, and
    I currently believe C.L.O.S. is eminently suitable for three dimensional
    game objects.

    YMMV. I think the LAST thing we need is more games. Too many gamers
    need to pull their heads out of the game and go get a life.


    I disagree. Not about gamers, they absolutely need to get a life, but
    about the games. It's generally hard for me to find games I personally
    enjoy, so I've started to amass a library of game making related books.

    Of course, that can be just a symptom of my severe Tsundoku, but a
    creature can dream of making games in the future.

    Plus, making games is a completely different activity from playing them.


    Happy game making in Common Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Fri Aug 21 15:23:45 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 22 Aug 2026 02:28:49 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 16/08/2026 7:44 AM, George Neuner wrote:

    YMMV. I think the LAST thing we need is more games. Too many gamers
    need to pull their heads out of the game and go get a life.


    I disagree. Not about gamers, they absolutely need to get a life, but
    about the games. It's generally hard for me to find games I personally >enjoy, so I've started to amass a library of game making related books.

    Of course, that can be just a symptom of my severe Tsundoku, but a
    creature can dream of making games in the future.

    I don't play games - I drive fast cars and fly small planes.
    [Yes, I have a private pilot license.]

    For fun I dabble in programming languages, compilers and runtimes.


    Plus, making games is a completely different activity from playing them.

    A good point. Programming a game might be more fun than playing one.

    OTOH, I worked in HRT machine vision QA/QC for over a decade, so now I
    find graphics largely to be boring. Currently I do databases, and
    occasionally middleware apps to support them.

    Enough about me.


    Happy game making in Common Lisp!

    To each their own. 8-)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Sat Aug 22 07:54:06 2026
    From Newsgroup: comp.lang.lisp

    On 22/08/2026 3:23 AM, George Neuner wrote:
    On Sat, 22 Aug 2026 02:28:49 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 16/08/2026 7:44 AM, George Neuner wrote:

    YMMV. I think the LAST thing we need is more games. Too many gamers
    need to pull their heads out of the game and go get a life.


    I disagree. Not about gamers, they absolutely need to get a life, but
    about the games. It's generally hard for me to find games I personally
    enjoy, so I've started to amass a library of game making related books.

    Of course, that can be just a symptom of my severe Tsundoku, but a
    creature can dream of making games in the future.

    I don't play games - I drive fast cars and fly small planes.
    [Yes, I have a private pilot license.]

    Happy flying! Or speeding! I'll be sure to let you know if I ever make
    true my old dream of getting a helicopter license.


    For fun I dabble in programming languages, compilers and runtimes.

    Yes, that is indeed fun. I have amassed quite an extensive library on
    the subject. Though not in Common Lisp. Compiler literature, at least
    in physical copies -- is lacking in the language of the Lisp.



    Plus, making games is a completely different activity from playing them.

    A good point. Programming a game might be more fun than playing one.

    OTOH, I worked in HRT machine vision QA/QC for over a decade, so now I
    find graphics largely to be boring. Currently I do databases, and occasionally middleware apps to support them.

    Fair enough. I am also not at all impressed by the modern game engines,
    and have no desire to pick up a project in Unity again.

    Here in Common Lisp, I'd be delighted to make use of SDL2 or SDL3
    bindings, along with the OpenGL for a simple game.

    I have also been in databases on and off for the past sixteen years, and
    have -- I would not say extensive -- but enough experience in tuning
    both Postgres and MariaDB that you can feel free, if your database sys-
    tem needs to handle about million people per day -- possibly more, but I stopped counting at million -- to ask tuning questions.

    I have not seen fit to subscribe to any of the database groups yet, so
    please let me know which ones you'd like to use for such discussions.

    In the mean time, we can discuss SQLite bindings for S.B.C.L, because I
    did not find anything of the sort with a casual websearch. Is there
    such a thing already in QuickLisp?


    Best wishes, and happy database queries on Common Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sat Aug 22 00:00:42 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> wrote:
    I think it's worth understanding what macros actually mean.

    Most programming languages are dictatorships: a small, usually
    self-elected, self-important group of people designs a language, and thousands or millions of serfs have to suffer the consequences of their choices.

    Sometimes there is a pretense of some limited form of democracy: perhaps
    you, as a mere serf, can join the politburo and have a vote on what happens to the language. Sometimes this involves a payment to some nebulous standards organisation. Sometimes you can comment on suggested changes; sometimes people might listen to those comments. Sometimes the politburo
    is not largely made up of representatives (either explicit or implicit) of huge corporations who care not one jot about your interests.

    Changes, when they happen at all, take years. The language is ossified almost as soon as it exists.

    Almost always, for large systems, there will be tools built on top of the ossified substrate language which allow people to write programs in a way which actually matches their problem domain. Those tools are, in fact, *programming languages*, although they're usually implemented in an ad-hoc way by people who don't even realise that what they are doing is designing
    a programming language. They are therefore predictably horrible. If you have not used such an ad-hoc language you probably have not worked on a
    large system.

    Sometimes people make a better decision: they take an existing (usually dynamically typed as basically nobody likes static typing in the real
    world, usually either not compiled or dynamically compiled) language which has a good interface to the ossified substrate and expose functionality written in the ossified substrate to the more flexible surface language. NumPy and all its relations are the canonical example of this.

    That's at least better than the thing implemented using m4 on top of
    Fortran or whatever. But the thing written in m4 on top of Fortran is *still* better than using Fortran directly (and this is not because
    Fortran, today, is a bad language, which is is not, it's because it's an ossified language).

    Quite often what happens is that user or group of users of a language gets
    so fed up with this process that they design a new language which better meets their needs, perhaps starting with one of the ad-hoc languages above.
    That language then develops its own self-important politburo, becomes ossified.

    Recurse.

    Lisp chose something else. Lisp chose not to be a dictatorship, but to
    treat its users as adults capable of making their own decisions: decisions which were as good as the decisions of the politburo if not better. Decisions which, certainly, relfected the needs of the users making the decisions rather than some distant observer.

    Lisp looked at what *actually happens* in the world rather than in the
    heads of the politburo members, and it saw that what happened was the
    endless invention of new languages, either for specific problem domains, or just because the existing languages were so terrible. And it said, 'OK, let's make that a feature, not something you have to fight your way
    towards. Let's build a language whose defining feature is that it lets you build languages. Let's allow it to let you build languages
    *incrementally*, rather than putting some enormous barrier in your way. So you can take an existing language and define some extensions to it, and
    those extensions wil have exactly the same status as the original language does.'

    If you disagree with the decisions of the politburo you don't have to wait five years for the members to die and the decision to change, you can just make the system do what you want, today.

    Lisp understood that this means you have to make some compromises. The
    most significant is that the syntax of the language must have very low commitment to the semantics. That makes the language rather austere, but
    it means that you, the user of the language, get to say what the semantics is, without having to jump through some huge ring of fire and getting
    burned in the process.

    Lisp is a system built by people who understand how utterly stupid the
    claim that any programming language contains 90% of all the constructs
    anyone will ever need is.

    Lisp is a democracy. It is perhaps more than a democracy: it either is or
    is close to an anarchy. Anarchies obviously work only if their citizens
    are actually adults and if they are willing to cooperate with one another. But, well, Lisp assumes you are. If you're not an adult, or if you can't deal with cooperating with other people in the design of the language
    you're going to use, or if you like someone telling you what to do then, well, do what thou wilt.

    Lisp understands that a consequence of this anarchy is that different
    groups of users working on different projects will end up using differing languages, or dialects (*a shprakh iz a dyalekt mit an armey un flot*, famously), and it also understands that *that's what happens anyway*,
    except the languages and dialects people end up using are usually things created using tools whose only datatype is the string.

    Like I say: if you're happy to live as a serf in a dictactorship, or if you feel you might become a dictator, then that's OK. But please, stay the
    fuck away from those of us who want not to be serfs or dictators, and who want to make our own decisions in a community of our equals.

    Let me mention some decision of the polibiuro that I do not like.

    1) I am a Unix man and doing

    (compile-file "foo/bar.lisp" :output-file "baz/bar.fasl")

    I want output to live is file "baz/bar.fasl" relative to current
    directory. But polibiuro decided differently. I solve this in
    Blub way, that is writing wrapper function that converts
    "baz/bar.fasl" to absolute path and then calls 'compile-file'.

    2) Program that I am developing has a user language which is implemented converting user input to Lisp and then using 'eval' to evaluate it.
    That is good, but there is a catch: from users point of view "T"
    is a perfectly good variable name. But polibiuro decided that
    it is reserved. I could try to work around this using packages,
    but this has serious drawback. So I solve this in Blub way,
    that is convertion replaces "T" by a different name.

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list.
    I would like "NIL" to be a constant symbol which when evaluated
    gives empty list. That I could fix with packages. But there is
    a catch: I want my symbols to print in natural way, without
    package prefix and the same for empty list. And for that I did
    not found a solution.

    4) In a function I would like RETURN to return a current function,
    even if there are blocks inside. I think that a macro could help
    with this, but this would be rather hairy macro needind to walk
    trough arbitrary Lisp code. So in Blub spirit I live with the
    problem.

    5) I create symbols from strings. For my sanity I want symbols
    in source exactly (including case) to match strings used to
    create symbols. But I dislike shouting, so I would prefer lower
    case symbols in my source. I can partially solve this: I can
    create a package called "common-lisp" (in lower case) and populate
    it with lower case versions of symbols from "COMMON-LISP". That
    somewhat works for functions, that is I can assign to 'symbol-funtion'
    to get the same function as for corresponding symbol in "COMMON-LISP".
    I could probably handle macros and special forms in similar way.
    And probably constants too. I probably could handle variables
    using symbol macros. But there is a trouble with functions: functions
    in "COMMON-LISP" expect upper case keywords. To have lower case
    keywords I would have to replace each Common Lisp function by a
    wrapper which converts keyword arguments. And presumably, Lisp
    printer would print "expanded" version of my code, so I would
    loose correspondence with my sources. So ATM in Blub spirit
    I decided that it is too much work to change the language.

    BTW: IIUC Allegro CL has resonable solution to this. But I am
    using free Lisp-s and unwilling to swich to closed source
    system.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 22 01:11:14 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 19 Aug 2026 17:57:12 -0400, steve g wrote:

    bixbox <noreply@example.invalid> writes:

    I want to learn Common Lisp, but I don't really know what
    resources to use.

    start using emacs.

    Emacs isnrCOt Common Lisp.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 22 01:23:02 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 22 Aug 2026 00:00:42 -0000 (UTC), Waldek Hebisch wrote:

    Let me mention some decision of the polibiuro that I do not like.

    1) I am a Unix man and doing

    (compile-file "foo/bar.lisp" :output-file "baz/bar.fasl")

    I want output to live is file "baz/bar.fasl" relative to current
    directory. But polibiuro decided differently. I solve this in
    Blub way, that is writing wrapper function that converts
    "baz/bar.fasl" to absolute path and then calls 'compile-file'.

    Note how the defaults for input-file are filled in from *input-pathname-defaults*, but the same does not apply to output-file: <https://www.lispworks.com/documentation/HyperSpec/Body/f_cmp_fi.htm>.

    This is what I mean by Common Lisp being full of baggage for catering
    to non-POSIX operating systems which are all extinct now.

    2) Program that I am developing has a user language which is
    implemented converting user input to Lisp and then using 'eval' to
    evaluate it. That is good, but there is a catch: from users point of
    view "T" is a perfectly good variable name. But polibiuro decided
    that it is reserved. I could try to work around this using packages,
    but this has serious drawback. So I solve this in Blub way, that is convertion replaces "T" by a different name.

    Or alternatively, you shouldnrCOt be equivalencing user-defined
    variables directly to Lisp variables.

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list. I would
    like "NIL" to be a constant symbol which when evaluated gives empty
    list.

    You want more than one empty-list object? I think that is
    traditionally treated as a rCLsingletonrCY (not just in Lisp), which means
    the answer is rCLnorCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Fri Aug 21 12:28:16 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    On Tue, 18 Aug 2026 21:34:40 -0700, Paul Rubin
    <no.email@nospam.invalid> wrote:

    steve g <Sgonedes1977@gmail.com> writes:
    but hygenic-macros and late evaluation is one of the best features
    about lisp macros.

    Lisp (CL) doesn't have hygienic macros, I thought. It took a long while >>for Scheme to standardize its version.

    You are correct - Lisp doesn't have hygienic macros. However, Lisp
    macros can be made safe(r) [for some definition] through careful use
    of (gensym).

    And in practice that happens to be enough.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sat Aug 22 12:07:45 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list. I would
    like "NIL" to be a constant symbol which when evaluated gives empty
    list.

    You want more than one empty-list object? I think that is
    traditionally treated as a rCLsingletonrCY (not just in Lisp), which means the answer is rCLnorCY.

    No, a single empty list object. I just want symbol NIL to be
    a real symbol distingushable from empty list. Consider
    * (setf a '( 1 ))
    (1)
    * (cdr a)
    NIL
    * (symbolp (cdr a))
    T
    * (eq (cdr a) 'NIL)
    T

    It would be better is the second line gave empty list, not a symbol.
    More important third and fourth line both should return false.
    OTOH the following still should hold

    * (eq (cdr a) NIL)
    T
    * (if (cdr a) "bad" "good")
    "good"

    And compare the above to

    (setf b (cdr a))
    NIL
    * (eq (cdr a) 'b)
    NIL
    * (eq (cdr a) b)
    T

    b is ordirnary symbol, after assignment evaluating b gives empty
    list, but _symbol_ b is different than empty list. The same
    should hold for NIL.

    If you think a bit current behaviour is highly unintuitive and
    requires some trickery to implement but is mandated by the
    Common Lisp specification.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sat Aug 22 18:13:00 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 22 Aug 2026 07:54:06 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 22/08/2026 3:23 AM, George Neuner wrote:
    On Sat, 22 Aug 2026 02:28:49 +0800, Johann 'Myrkraverk' Oskarsson
    <johann@myrkraverk.invalid> wrote:

    On 16/08/2026 7:44 AM, George Neuner wrote:


    For fun I dabble in programming languages, compilers and runtimes.

    Yes, that is indeed fun. I have amassed quite an extensive library on
    the subject. Though not in Common Lisp. Compiler literature, at least
    in physical copies -- is lacking in the language of the Lisp.

    Biggest obstacles [to Lisp] are closures, dynamic scoping, and GC -
    most everything else is transferrable from other languages.

    Closures and GC are covered by modern texts - explicit examples are
    sorely lacking, but the discussions are good enough that you can
    figure out how to implement things.

    Dynamic scoping - if you care - is something you really have to figure
    out on your own. Not that it's /that/ hard, but making it efficient
    and [possibly] dealing with multiple threads both are PITA.


    Plus, making games is a completely different activity from playing them.

    A good point. Programming a game might be more fun than playing one.

    OTOH, I worked in HRT machine vision QA/QC for over a decade, so now I
    find graphics largely to be boring. Currently I do databases, and
    occasionally middleware apps to support them.

    Fair enough. I am also not at all impressed by the modern game engines,
    and have no desire to pick up a project in Unity again.

    Here in Common Lisp, I'd be delighted to make use of SDL2 or SDL3
    bindings, along with the OpenGL for a simple game.

    I have also been in databases on and off for the past sixteen years, and
    have -- I would not say extensive -- but enough experience in tuning
    both Postgres and MariaDB that you can feel free, if your database sys-
    tem needs to handle about million people per day -- possibly more, but I >stopped counting at million -- to ask tuning questions.

    Haven't had opportunity to play with MariaDB. I have worked a lot
    with Postgresql [and with Sybase back in the day], and some with
    SQLServer, MySQL and SQLite.


    I have not seen fit to subscribe to any of the database groups yet, so
    please let me know which ones you'd like to use for such discussions.

    Most of the Usenet DBMS groups are dead - moved to web forums.


    In the mean time, we can discuss SQLite bindings for S.B.C.L, because I
    did not find anything of the sort with a casual websearch. Is there
    such a thing already in QuickLisp?

    Where applicable, I prefer to write my apps in Racket.

    Racket has an excellent webserver framework, and a nice DB query
    library with connection pooling and native protocol support for ODBC,
    SQLite, Postgresql, MySQL and Cassandra. https://docs.racket-lang.org/db/index.html

    [I've heard that the MySQL module also works for MariaDB but I have no
    direct experience with that.]


    Additionally, Ryan Culpepper has created a library for composing and
    working with SQL queries as sexprs. It interfaces directly to the DB
    library.
    https://docs.racket-lang.org/sql/index.html


    Of course, before I learned about Ryan's library, I had created my own
    macros to enable embedding raw SQL into Racket. At compile time, my
    macros turn SQL into a quasi-quote form, executed at runtime to handle
    embedded Racket code, which ultimately produces a query string
    compatible with the DB library.

    My take on it is different than Ryan's: his is meant to produce
    standard [but generic] SQL - mine lets you write explicitly in the
    unique SQL dialect of your target DBMS engine(s).

    Thirteen of one, baker's dozen of the other. 8-)


    Best wishes, and happy database queries on Common Lisp!

    I find Lisp intellectually interesting, but the truth is that at heart
    I'm a Schemer. Sorry.
    [Racket really isn't a Scheme per se, but it's close enough.]
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 22 22:24:50 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:

    I just want symbol NIL to be a real symbol distingushable from empty
    list.

    But this is a fundamental part of the traditional way that Lisp works:
    an rCLempty listrCY isnrCOt really a list at all, it is just a pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the need for a
    special symbol to denote it.

    In Python, on the other hand, an empty list is constructed with an
    expression like rCL[]rCY, an empty tuple with rCL()rCY, and both of these are distinct from the rCLNonerCY object.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sat Aug 22 23:08:44 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:

    I just want symbol NIL to be a real symbol distingushable from empty
    list.

    But this is a fundamental part of the traditional way that Lisp works:
    an rCLempty listrCY isnrCOt really a list at all, it is just a pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the need for a
    special symbol to denote it.

    No, you do not need special symbol to denote empty list, "()" works
    fine:

    * ()
    NIL

    And I do not want to upset people that write NIL to get empty
    list, writing NIL would still give you empty list.

    Concering tradition, I suspect that basically the same behaviour
    appears in newer Lisp system "because it was always done that way".

    But it seem to be rather specific to Lisp, there are other system
    having similar handling of lists and I know of no other repeating
    Lisp misfeature.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sat Aug 22 23:22:39 2026
    From Newsgroup: comp.lang.lisp

    On Sat, 22 Aug 2026 23:08:44 -0000 (UTC), Waldek Hebisch wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:

    I just want symbol NIL to be a real symbol distingushable from
    empty list.

    But this is a fundamental part of the traditional way that Lisp
    works: an rCLempty listrCY isnrCOt really a list at all, it is just a
    pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the
    need for a special symbol to denote it.

    No, you do not need special symbol to denote empty list, "()" works
    fine:

    * ()
    NIL

    But that equivalence is the very thing you were complaining about.
    Whereas in Python:

    ldo@theon:~> python3
    Python 3.14.6 (main, Jun 10 2026, 18:54:31) [GCC 15.2.0] on linux
    Type "help", "copyright", "credits" or "license" for more information.
    >>> [] == []
    True
    >>> () == ()
    True
    >>> () == None
    False
    >>> [] == None
    False

    Concering tradition, I suspect that basically the same behaviour
    appears in newer Lisp system "because it was always done that way".

    It has to do with the implementation. A list consists of cons
    structures linked together via pointers. An empty list consists of no
    cons structures, hence there is nothing to point to.

    But it seem to be rather specific to Lisp, there are other system
    having similar handling of lists and I know of no other repeating
    Lisp misfeature.

    I can think of one: multiple-value-return. This requires the creation
    of a whole mechanism involving data structures that are not really
    data structures.

    Python and JavaScript have a simpler approach to the same concept: destructuring assignment.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Sat Aug 22 23:48:53 2026
    From Newsgroup: comp.lang.lisp

    Aidan Kehoe <kehoea@Parhasard.net> wrote: |------------------------------------------------------------------------| |"Are you by any chance writing your posts using a large language model?"| |------------------------------------------------------------------------|

    No. This is a refereeing report about an LLM submission
    for "Journal of Information Science": HTTP://Gloucester.Insomnia247.NL/Evil_which_is_so-called_science/Pauline_Rafferty_or_Allen_Foster/Journal_of_Information_Science/JIS-26-1328/Referee_report_JIS-26-1328.odt
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sun Aug 23 00:23:20 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
    On Sat, 22 Aug 2026 23:08:44 -0000 (UTC), Waldek Hebisch wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Sat, 22 Aug 2026 12:07:45 -0000 (UTC), Waldek Hebisch wrote:

    I just want symbol NIL to be a real symbol distingushable from
    empty list.

    But this is a fundamental part of the traditional way that Lisp
    works: an rCLempty listrCY isnrCOt really a list at all, it is just a
    pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the
    need for a special symbol to denote it.

    No, you do not need special symbol to denote empty list, "()" works
    fine:

    * ()
    NIL

    But that equivalence is the very thing you were complaining about.

    I am affraid you do not understand what I want. I can do the
    following:

    * (shadow "NIL")
    T
    * (defconstant nil ())
    NIL
    * (eq 'NIL NIL)
    COMMON-LISP:NIL
    * NIL
    COMMON-LISP:NIL
    * ()
    COMMON-LISP:NIL
    *

    So, I can have my NIL that is different than empty list, but which
    when evaluated gives empty list. After that I can distinguish
    "my" symbols from lists. The problem which I can not solve is
    that empty list is printed as 'COMMON-LISP:NIL' instead of '()'.
    And Common Lisp functions still will treat empty list as a symbol.

    Concering tradition, I suspect that basically the same behaviour
    appears in newer Lisp system "because it was always done that way".
    <snip>
    It has to do with the implementation. A list consists of cons
    structures linked together via pointers. An empty list consists of no
    cons structures, hence there is nothing to point to.

    Actually, in Common Lisp empty list is almost a cons cell. Namely,
    you can do:

    * (car nil)
    NIL
    * (cdr nil)
    NIL
    *

    Usually it is implemented by special data in memory that looks like
    a cons cell, with CAR and CDR that point to itself. Function that
    check for NIL simply compare address with address of NIL.

    Common Lisp arranges data structure representing NIL so that it
    also looks like a symbol. Quite possible that this led to some
    simplification in first implementation (say skipping explicit case
    for empty list in printing code). But it actually is a buden
    for modern implementations. Not a big burden, but implementers
    must make sure that layout of cons cell and layout of symbols
    are compatible enough. Or alternatively sprinkle generated code
    with checks for special case of empty list which would likely
    decrease performance.

    But it seem to be rather specific to Lisp, there are other system
    having similar handling of lists and I know of no other repeating
    Lisp misfeature.

    I can think of one: multiple-value-return. This requires the creation
    of a whole mechanism involving data structures that are not really
    data structures.

    multiple-value-return is a different story. One can easily get
    equivalent effect with explict stack. And one can implement
    multiple values using a stack + markers. But AFAICS motivation
    for multiple values is to generate more efficient code and more
    efficient implementation will return first few values in
    machine registers. That saves allocation of intermediate container
    that would became garbage after return. In other words,
    multiple values require extra effort from implementation and
    programmers using them, but leads to more efficient code.
    One can debate if the effect is worth the effoet. OTOH nothing
    forces you to return multiple values from your functions.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Madhu@enometh@meer.net to comp.lang.lisp on Sun Aug 23 21:03:45 2026
    From Newsgroup: comp.lang.lisp

    * George Neuner <jg7h8ldp0ka3hd8nan3spb6avc199q53k6@4ax.com> :
    Wrote on Fri, 21 Aug 2026 15:23:45 -0400:


    I don't play games - I drive fast cars and fly small planes.

    So you're not part of the 200-250 billion dollar market, big deal.

    [Yes, I have a private pilot license.]

    For fun I dabble in programming languages, compilers and runtimes.
    Plus, making games is a completely different activity from playing them.

    A good point. Programming a game might be more fun than playing one.

    OTOH, I worked in HRT machine vision QA/QC for over a decade, so now I
    find graphics largely to be boring. Currently I do databases, and occasionally middleware apps to support them.

    I think the fundamental principle on which the programming industry is bankrolled is based on what was enunciated by brooks in "no silver
    bullet" -- the goose that lays golden eggs. given bankable developments
    in hardware and consumption, given access to fiat capital from satan's
    wazoo, and given the power to launder it, the creation of an essentially managable but fake "developer market" is inevitable. you may have
    perceived tfb to be petulant when he characterised the "serfs", but they
    really operate as a "middle class" ratifying the leadership and
    producing the consumption patterns that are needed (apart from the
    occasional profits in wage arbitrage).

    "programming glory" goes to shit. the discipline of graphics has
    essentially been thrown away, replaced and shaped with by "hardware developments", and it is in the interests of the bankers managing the
    deficts to bless the slop. (i'm surprised if tfb still in adam smith)

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 23 15:47:29 2026
    From Newsgroup: comp.lang.lisp

    antispam@fricas.org (Waldek Hebisch) writes:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list. I would
    like "NIL" to be a constant symbol which when evaluated gives empty
    list.

    You want more than one empty-list object? I think that is
    traditionally treated as a rCLsingletonrCY (not just in Lisp), which means >> the answer is rCLnorCY.

    No, a single empty list object. I just want symbol NIL to be
    a real symbol distingushable from empty list. Consider



    I usually use deconstant or define symbol macro.

    (deconst +eof+ '+eof+)

    ; SLIME 2.27
    CL-USER> (defconstant +eof+ '+eof+)

    CL-USER> +eof+
    +EOF+

    CL-USER> (defconstant +eol+ '(nil . nil))
    +EOL+
    CL-USER> +eol+
    (NIL)
    CL-USER>

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Aug 23 15:58:03 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    On Sat, 22 Aug 2026 07:54:06 +0800, Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 22/08/2026 3:23 AM, George Neuner wrote:
    On Sat, 22 Aug 2026 02:28:49 +0800, Johann 'Myrkraverk' Oskarsson
    <johann@myrkraverk.invalid> wrote:

    On 16/08/2026 7:44 AM, George Neuner wrote:

    Haven't had opportunity to play with MariaDB. I have worked a lot
    with Postgresql [and with Sybase back in the day], and some with
    SQLServer, MySQL and SQLite.


    Yes! Another sybase user. That was some good software!

    Most of the Usenet DBMS groups are dead - moved to web forums.

    I just started looking into using GDBM. If you want an easy solution
    (shameless plug in) I believe Allegro Common Lisp has build in database features.

    AllegroCache - Object Persistence in LisP, AlegroGraph The AI Agent for
    your Knowledge Graph Solution. These are available to limited extent via
    their website.

    In the mean time, we can discuss SQLite bindings for S.B.C.L, because I
    did not find anything of the sort with a casual websearch. Is there
    such a thing already in QuickLisp?


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Aidan Kehoe@kehoea@parhasard.net to comp.lang.lisp on Sun Aug 23 21:57:01 2026
    From Newsgroup: comp.lang.lisp



    Ar an tr|!|| l|i is fiche de m|! L||nasa, scr|!obh steve g.:

    antispam@fricas.org (Waldek Hebisch) writes:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    3) I would like to so symbolic computation with arbitrary symbols. For >>> my purpose a symbol is always different from a list. But polibiuro
    decided that "NIL" is identical to the empty list. I would like "NIL" to >>> be a constant symbol which when evaluated gives empty list.

    You want more than one empty-list object? I think that is traditionally >> treated as a rCLsingletonrCY (not just in Lisp), which means the answer is
    rCLnorCY.

    No, a single empty list object. I just want symbol NIL to be
    a real symbol distingushable from empty list. Consider

    If your priority is purity, there is not reason for end-of-list to be a symbol.

    (defconstant end-of-list (let ((result (cons 0 0)))
    (setf (car result) result
    (cdr result) result)))

    ThatrCOs a constant for which (car end-of-list) will give end-of-list as will (cdr end-of-list). Your implementation will need to handle circularity
    with grace.

    This makes the implementation of #'listp simpler; it just becomes #'consp. You would need to use #'endp to detect the end of the list, but thatrCOs recommended
    anyway.

    Nothing is compatible with this and you will have constant work if you wish to use your lists like that. But, yes, itrCOs more semantically pure.

    I usually use deconstant or define symbol macro.

    (deconst +eof+ '+eof+)

    ; SLIME 2.27
    CL-USER> (defconstant +eof+ '+eof+)

    CL-USER> +eof+
    +EOF+

    CL-USER> (defconstant +eol+ '(nil . nil))
    +EOL+
    CL-USER> +eol+
    (NIL)
    CL-USER>
    --
    rCyAs I sat looking up at the Guinness ad, I could never figure out /
    How your man stayed up on the surfboard after fourteen pints of stoutrCO
    (C. Moore)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sun Aug 23 22:21:28 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 23 Aug 2026 21:57:01 +0100, Aidan Kehoe wrote:

    If your priority is purity, there is not reason for end-of-list to
    be a symbol.

    There is this assumption, is there, that rCLlistrCY must mean the
    traditional Lisp implementation in terms of two-field cells, so
    processing always involves a lot of pointer-chasing?

    I donrCOt think there is any such assumption in Python, just for
    example. Expressions of the form rCL[...]rCY are said to construct
    rCLlistsrCY, but the underlying implementation is more likely to be a flex array (to use Algol 68 terminology).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sun Aug 23 22:37:36 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:
    antispam@fricas.org (Waldek Hebisch) writes:

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list. I would
    like "NIL" to be a constant symbol which when evaluated gives empty
    list.

    You want more than one empty-list object? I think that is
    traditionally treated as a rCLsingletonrCY (not just in Lisp), which means >>> the answer is rCLnorCY.

    No, a single empty list object. I just want symbol NIL to be
    a real symbol distingushable from empty list. Consider



    I usually use deconstant or define symbol macro.

    (deconst +eof+ '+eof+)

    ; SLIME 2.27
    CL-USER> (defconstant +eof+ '+eof+)

    CL-USER> +eof+
    +EOF+

    CL-USER> (defconstant +eol+ '(nil . nil))
    +EOL+
    CL-USER> +eol+
    (NIL)
    CL-USER>

    Yes, I can get half way by using packages and shadowing real NIL. But
    in such approach Common Lisp still considers empty list to be a symbol
    and prints it a symbol. More radical approach as above means that
    I can no longer use standard Common Lisp functions so I need to add
    "buggy and slow implementation of half of the Common Lisp" to my
    program.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Sun Aug 23 23:47:32 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 23 Aug 2026 22:37:36 -0000 (UTC), Waldek Hebisch wrote:

    More radical approach as above means that I can no longer use
    standard Common Lisp functions so I need to add "buggy and slow implementation of half of the Common Lisp" to my program.

    Some have proposed coming up with more modern Lisps as an alternative
    to Common Lisp. Are any of them realistic yet?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Mon Aug 24 01:42:30 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 23 Aug 2026 21:03:45 +0530, Madhu <enometh@meer.net> wrote:

    * George Neuner <jg7h8ldp0ka3hd8nan3spb6avc199q53k6@4ax.com> :
    Wrote on Fri, 21 Aug 2026 15:23:45 -0400:


    I don't play games - I drive fast cars and fly small planes.

    So you're not part of the 200-250 billion dollar market, big deal.

    [Yes, I have a private pilot license.]

    For fun I dabble in programming languages, compilers and runtimes.
    Plus, making games is a completely different activity from playing them.

    A good point. Programming a game might be more fun than playing one.

    OTOH, I worked in HRT machine vision QA/QC for over a decade, so now I
    find graphics largely to be boring. Currently I do databases, and
    occasionally middleware apps to support them.

    I think the fundamental principle on which the programming industry is >bankrolled is based on what was enunciated by brooks in "no silver
    bullet" -- the goose that lays golden eggs.

    Absolutely.

    The problem I see is that some people become so engrossed in their
    games that they forget to get a life. And most people who will play a
    game are not capable of creating one - so games don't really add much
    to the ranks of developers.

    I had an Atari and there were some kiosk arcade games I enjoyed when I
    was in high (secondary) school. Never really got into any computer
    based games.


    given bankable developments
    in hardware and consumption, given access to fiat capital from satan's
    wazoo, and given the power to launder it, the creation of an essentially >managable but fake "developer market" is inevitable. you may have
    perceived tfb to be petulant when he characterised the "serfs", but they >really operate as a "middle class" ratifying the leadership and
    producing the consumption patterns that are needed (apart from the
    occasional profits in wage arbitrage).

    "programming glory" goes to shit. the discipline of graphics has
    essentially been thrown away, replaced and shaped with by "hardware >developments", and it is in the interests of the bankers managing the
    deficts to bless the slop. (i'm surprised if tfb still in adam smith)

    Not to mention that the average developer today has taken no CS or CE
    courses, knows one or two languages at best, and has skills which are
    not very far advanced beyond script kiddie. Many [most?] are not
    capable of (re)creating even basic library functions that they use
    routinely.

    YMMV, but in my opinion a great many software "developers" would be
    doing the world a favor by finding other employment.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Mon Aug 24 01:24:37 2026
    From Newsgroup: comp.lang.lisp

    antispam@fricas.org (Waldek Hebisch) writes:
    Yes, I can get half way by using packages and shadowing real NIL. But
    in such approach Common Lisp still considers empty list to be a symbol

    I think the Lisp machines had that, and they got it from Maclisp, which
    may have inherited it from even older Lisps. CL by intention retained
    quirks like that to keep supporting pre-CL codebases. I don't know how
    CL's other ancestors like Interlisp handled empty lists. Anyway, if you
    want Scheme, you know where it is.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 08:46:55 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:
    tfb <tfb@work.it.out> writes:
    No single language has 1% of constructs anyone might ever want.

    If I can code fluently in a language, that is, I can think entirely
    about the application-level problem I'm trying to solve and not putting
    much effort into choosing language constructs, then it's supplying 100%
    of what I want at least at that moment. That's great.


    Here's the thing: you are one person. There are, shockingly, other people
    in the world who might want to write programs. You may also have noted
    that more than one programming language exists. Although you are clearly
    happy with whatever language it is you use and never inclined to look at anything else, perhaps some if these other languages might exist because
    other people might want a different set of constructs, don't you think?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 08:56:05 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:


    I don't follow.


    Consider (with-current-readtable (...) <form>): what is the current
    readtable when <form> is read?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 08:57:16 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:


    I don't follow.


    Consider (with-current-readtable (...) <form>): what is the current
    readtable when <form> is read?
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 09:17:26 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:

    You are correct - Lisp doesn't have hygienic macros. However, Lisp
    macros can be made safe(r) [for some definition] through careful use
    of (gensym).


    CL macros are never really safe in general: you can pretty much deal with
    names the macro introduces, but you *can't* deal with names it refers to getting rebound outside the macro. Or rather, the language can't:
    convention can. You can say 'this package is to be treated like the CL
    package in terms of rebinding', for instance.

    There are also lots of nice tricks to make gensyms less painful to use such
    as my metatronic macros:

    (defmacro/m with-foo ((form &body body)
    `(let ((<it> ,form)) ... <it> ...))

    will ensure that <it> is a gensym.

    In practice CL-style macros with some tools around them appear to be sufficient.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp on Mon Aug 24 09:46:45 2026
    From Newsgroup: comp.lang.lisp

    Steve G <Sgonedes1977@GMail.com> wrote: |---------------------------------------------------------------------|
    |"> Dear Mister Stephen G: |
    |
    I had bought many books. They have been robbed. I never got to read|
    them :( |
    | |
    |same here." | |---------------------------------------------------------------------|

    Dear Mister Steve G:

    I am sorry and I empathize :(

    |---------------------------------------------------------------------|
    |"> I do not write cursive writings. I am an Asperger autist. |
    | |
    |try and use a computer... |
    | |
    |[. . .]" | |---------------------------------------------------------------------|

    These robbed books became robbed whilst these robbers also robbed many
    more of my properties inlcuding three computers plus an Apple
    smartphone plus an external hard disk plus many USB flash sticks plus
    optical discs. It took me a long time trying to get a (new) computer
    of my own again. As for getting these robbed properties back, a lawyer
    for me had said years ago: "I keep my expectations low." Almost no
    progress on this issue has been made! :(
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to comp.lang.lisp,comp.edu.languages.natural on Mon Aug 24 10:15:09 2026
    From Newsgroup: comp.lang.lisp

    |------------------------------------------------------------------------|
    |"I try to keep in shape by reading books in languages I'm not using. Or| |converse with people about programming languages I don't use anymore, | |such as Pascal. |
    | | |I've managed to keep my French more or less intact, but could use a | |brush up on Danish, and of course German as I said. [. . .] |
    |[. . .]" | |------------------------------------------------------------------------|

    |------------------------------------------------------------------------|
    |"I have practiced a little bit of French in the form of short instant | |messages lately, but feel it's time to bring up the big guns and read |
    |a book, and start the video course I've had dormant for a long time. |
    | |
    |[. . .]" | |------------------------------------------------------------------------|

    HTTPS://WWW.BookLooker.De
    is good for German really cheap books.

    Lireka.com
    sells French books cheaply internationally. It gave me a discount code
    to share with persons, which I could give you but I think that this
    discount code might be restricted to family members instead of random
    persons whom I do not know :)

    N.B. I do not do French (though I 'read' a dissertation in French).
    Lireka.com
    sold a book to me which I bought as a present for a Francophone
    friend.

    Consider reading news:fr.comp.*

    (I did upload a solicitation to buy a product in news:fr.comp.lang.ada
    (which is archived in HTTP://Gloucester.Insomnia247.NL/Ada/fr.comp.lang.ada_on_18th_August_2026.mbox.txt
    ), but coworkers translated to French for me.)

    A lady of Swedish nationality thought that I am Danish because of how
    I 'spoke' Swedish. I met a man on March 18th, 2026 who used to reside
    and work in Denmark and Sweden. He said that I spoke in an accent like
    a Danish accent, so he asked me am I Danish. Cf. HTTP://Gloucester.Insomnia247.NL/gardai/Where_are_you_from/2026-03-18h_We_can_t_accept_documents_where_we_re_not_sure_of_the_legalities_I_m_not_going_to_refer_to_a_book_arsa_bean_cuirte_2026_03_18_14_55_06_mdat_deleted_by_dd_faad_ffmpeg.M4A
    at circa 2:09:47! I expect that persons in Denmark understand
    virtually Swedish. Danish has a reputation for being the hardest of
    Norwegian; Danish; and Swedish. I do not mean to be offensive: these
    '3' language's' strike me as being dialects of one language. I like
    Swedish. I studied Swedish. I never study Danish and Norwegian.

    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 10:17:54 2026
    From Newsgroup: comp.lang.lisp

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    But this is a fundamental part of the traditional way that Lisp works:
    an rCLempty listrCY isnrCOt really a list at all, it is just a pointer that points nowhere (in C: NULL; in Lisp: NIL). Hence the need for a
    special symbol to denote it.

    TLDR: not really, NIL is very weird in CL. This does not have to be the
    case in a Lisp.

    The empty list is indeed magic (it is the unique object which is a list but
    not a cons) but there need be no symbol to denote it: it can just be ().
    For example: Scheme, which does this.

    In CL and its ancestors, NIL is a very weird thing: it is not just a symbol bound to the empty list (the way T is just a symbol bound to itself), but rather the empty list is three things: a list, not a cons, *and a symbol*. (symbolp '()) is true in CL: the equivalent is false in Scheme. If this
    was not true in CL: if NiL was just an ordinary symbol bound to the empty
    list, which was not a symbol, then (eq 'nil '()) would be false.

    It's also interesting as to whether () should be self-evaluating in CL.
    Even if NIL *was* just an ordinary symbol then the CL evaluation rules say
    it should be self-evaluating, because the only objects which are not are symbols, and conses. (The rules for what should be self-evaluating in CL arrived fairly late on, I think).
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 10:17:56 2026
    From Newsgroup: comp.lang.lisp

    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    Python and JavaScript have a simpler approach to the same concept: destructuring assignment.


    One more time: destructuring binding, which CL has, is not a substitute for multiple values.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 10:24:27 2026
    From Newsgroup: comp.lang.lisp

    Waldek Hebisch <antispam@fricas.org> wrote:

    Yes, I can get half way by using packages and shadowing real NIL. But
    in such approach Common Lisp still considers empty list to be a symbol
    and prints it a symbol. More radical approach as above means that
    I can no longer use standard Common Lisp functions so I need to add
    "buggy and slow implementation of half of the Common Lisp" to my
    program.

    Never use shadow: define a package which is CL except NIL is its own symbol (yes,
    i know this is opinion, but I have never seen a use fir shadiw which was
    not just a botch).

    There is considerable control over the printer (specifically the pretty printer). You probably can't *always* prevent () printing as CL:NIL but
    you certainly can in the great majority of cases.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 11:08:38 2026
    From Newsgroup: comp.lang.lisp

    This article (which, as you say is old now, if not in this form)
    misdiagnoses what is happening.

    Yes, BBMs are a thing (I am not one: I am *lazy* which is its own problem,
    and I make mo claim to brilliance), and yes, there are perhaps more of them
    in Lisp than elsewhere. But the reason is more complicated.

    People who are, in whatever way is required, smart, will want to do things which are hard in the right way. A subset of those people will be BBMs.
    That means that fields which are hard will necessarily get more BBMs,
    because of the first 'B'.

    Fields which are hard are also never going to be popular, just because not
    many people are smart in the right way to do them.

    General relativity is hard: nobody berates it because not many people can
    hack it. Because it is hard it is also not popular: again nobody berates
    it because of that.

    Lisp is not popular because a lot of its best uses are doing hard things. Python is popular because a lot of its best uses are doing easy things (or things which are, as a programming problem, easy). There is nothing wrong
    with using a language designed for doing easy things when what you want to
    do is an easy thing: my problem with Python is that its notion of interface stability is a bad joke: even so I write plenty of tools in Python.

    Like the article says: 'the answer is that there is no problem with Lisp, because Lisp is, like life, what you make of it'.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 19:38:57 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 4:46 PM, tfb wrote:
    Paul Rubin <no.email@nospam.invalid> wrote:
    tfb <tfb@work.it.out> writes:
    No single language has 1% of constructs anyone might ever want.

    If I can code fluently in a language, that is, I can think entirely
    about the application-level problem I'm trying to solve and not putting
    much effort into choosing language constructs, then it's supplying 100%
    of what I want at least at that moment. That's great.


    Here's the thing: you are one person. There are, shockingly, other people
    in the world who might want to write programs. You may also have noted
    that more than one programming language exists. Although you are clearly happy with whatever language it is you use and never inclined to look at anything else, perhaps some if these other languages might exist because other people might want a different set of constructs, don't you think?


    Dear tfb,

    I have no idea what you're talking about. To me, Paul is absolutely
    correct. Being fluent in a programming language means I don't have to
    look things up constantly, such as figuring out what the various &
    symbols mean in Rust -- that's a recent adventure of mine, so I'm in-
    cluding comp.lang.misc until we have comp.lang.rust -- and it does get
    old fast.

    Working in an unfamiliar programming means I'm not fluent, and I cannot
    just write whatever I want -- I mean, the Rust compiler explicitly does
    not allow me to just /inline "Common Lisp"/ if I may speak in C++
    tokens; the equivalent Rust would probably be something like /inl Lisp {
    /* Common Lisp goes here */ }/, using AWK matching syntax for emphasis
    -- so I'm resorting to actually have to read the book, because constant-
    ly looking things up got old several days ago.

    This of course delays my chapter one project of /Writing a C Compiler/
    by Nora Sandler; so I'm including comp.lang.c in this discussion as
    well, for obvious reasons.


    So my question to you, dear tfb, when exactly do you not know a pro-
    gramming language, and when was the last time this happened to you?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 24 19:41:49 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 7:08 PM, tfb wrote:
    This article (which, as you say is old now, if not in this form)
    misdiagnoses what is happening.

    Yes, BBMs are a thing (I am not one: I am *lazy* which is its own problem, and I make mo claim to brilliance), and yes, there are perhaps more of them in Lisp than elsewhere. But the reason is more complicated.

    People who are, in whatever way is required, smart, will want to do things which are hard in the right way. A subset of those people will be BBMs.
    That means that fields which are hard will necessarily get more BBMs,
    because of the first 'B'.

    Fields which are hard are also never going to be popular, just because not many people are smart in the right way to do them.

    General relativity is hard: nobody berates it because not many people can hack it. Because it is hard it is also not popular: again nobody berates
    it because of that.

    Lisp is not popular because a lot of its best uses are doing hard things. Python is popular because a lot of its best uses are doing easy things (or things which are, as a programming problem, easy). There is nothing wrong with using a language designed for doing easy things when what you want to
    do is an easy thing: my problem with Python is that its notion of interface stability is a bad joke: even so I write plenty of tools in Python.

    Like the article says: 'the answer is that there is no problem with Lisp, because Lisp is, like life, what you make of it'.


    Dear tfb,

    I believe you are wrong about Python's popularity. Python is popular
    because of constant effort by /Python influencers/ such as our very own Lawrence D'Oliveiro. It's not exactly easy for anyone to use, in the
    long term.


    Best wishes, and happy Python programming in comp.lang.python!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 24 19:44:01 2026
    From Newsgroup: comp.lang.lisp

    On 22/08/2026 9:23 AM, Lawrence DrCOOliveiro wrote:
    On Sat, 22 Aug 2026 00:00:42 -0000 (UTC), Waldek Hebisch wrote:

    Let me mention some decision of the polibiuro that I do not like.

    1) I am a Unix man and doing

    (compile-file "foo/bar.lisp" :output-file "baz/bar.fasl")

    I want output to live is file "baz/bar.fasl" relative to current
    directory. But polibiuro decided differently. I solve this in
    Blub way, that is writing wrapper function that converts
    "baz/bar.fasl" to absolute path and then calls 'compile-file'.

    Note how the defaults for input-file are filled in from *input-pathname-defaults*, but the same does not apply to output-file: <https://www.lispworks.com/documentation/HyperSpec/Body/f_cmp_fi.htm>.

    This is what I mean by Common Lisp being full of baggage for catering
    to non-POSIX operating systems which are all extinct now.


    So, erm, what's wrong with the baggage that is stdin, and stdout in C?


    2) Program that I am developing has a user language which is
    implemented converting user input to Lisp and then using 'eval' to
    evaluate it. That is good, but there is a catch: from users point of
    view "T" is a perfectly good variable name. But polibiuro decided
    that it is reserved. I could try to work around this using packages,
    but this has serious drawback. So I solve this in Blub way, that is
    convertion replaces "T" by a different name.

    Or alternatively, you shouldnrCOt be equivalencing user-defined
    variables directly to Lisp variables.

    3) I would like to so symbolic computation with arbitrary symbols.
    For my purpose a symbol is always different from a list. But
    polibiuro decided that "NIL" is identical to the empty list. I would
    like "NIL" to be a constant symbol which when evaluated gives empty
    list.

    You want more than one empty-list object? I think that is
    traditionally treated as a rCLsingletonrCY (not just in Lisp), which means the answer is rCLnorCY.

    I'd hope not, but I cannot speak for anyone but myself. I myself use
    singleton objects when I implement programming languages. It just so
    happens I don't have a project in a finished enough state to share with comp.lang.lisp.


    Best wishes, and happy singleton objects!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 24 19:45:41 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 6:17 PM, tfb wrote:
    Lawrence D-|Oliveiro <ldo@nz.invalid> wrote:

    Python and JavaScript have a simpler approach to the same concept:
    destructuring assignment.


    One more time: destructuring binding, which CL has, is not a substitute for multiple values.


    Dear tfb,

    What are you talking about? Of course it is a substitute for multiple
    values. It's a design decision per function to return either a list or multiple values, and each has its pros and cons.

    So it's perfectly natural to return a list in some cases where multiple
    values would do the trick too.


    Happy returning multiple values!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 24 19:49:54 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 6:21 AM, Lawrence DrCOOliveiro wrote:
    On Sun, 23 Aug 2026 21:57:01 +0100, Aidan Kehoe wrote:

    If your priority is purity, there is not reason for end-of-list to
    be a symbol.

    There is this assumption, is there, that rCLlistrCY must mean the
    traditional Lisp implementation in terms of two-field cells, so
    processing always involves a lot of pointer-chasing?

    I donrCOt think there is any such assumption in Python, just for
    example. Expressions of the form rCL[...]rCY are said to construct rCLlistsrCY, but the underlying implementation is more likely to be a flex array (to use Algol 68 terminology).

    Dear Lawrence,

    As usual, you know nothing. That "list" does not imply a linked list
    is a malfunction in the Pythong. We, people who actually read algorithm
    books, and implement our own data structures, want linked lists when we
    mean "lists", and arrays -- or the GNU given vector like in C++ for
    weirdness' sake -- so this is only going to confuse people new to
    Pythong.

    Of course, as a Pythong influencer, you don't care about confusion in
    other people, but it's there nevertheless.


    Happy coding in Pythong!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Mon Aug 24 19:51:33 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 7:47 AM, Lawrence DrCOOliveiro wrote:
    On Sun, 23 Aug 2026 22:37:36 -0000 (UTC), Waldek Hebisch wrote:

    More radical approach as above means that I can no longer use
    standard Common Lisp functions so I need to add "buggy and slow
    implementation of half of the Common Lisp" to my program.

    Some have proposed coming up with more modern Lisps as an alternative
    to Common Lisp. Are any of them realistic yet?

    No, I think Paul Graham even gave up on his very own /ARC/, whatever
    that was meant to be.

    Yes, because Clojure is a thing, but then you have to use the JVM, and
    not the Pythong interpreter, so that rules you out.


    Best wishes, and happy making your own Lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Mon Aug 24 12:02:33 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:
    antispam@fricas.org (Waldek Hebisch) writes:
    Yes, I can get half way by using packages and shadowing real NIL. But
    in such approach Common Lisp still considers empty list to be a symbol

    I think the Lisp machines had that, and they got it from Maclisp, which
    may have inherited it from even older Lisps. CL by intention retained
    quirks like that to keep supporting pre-CL codebases. I don't know how
    CL's other ancestors like Interlisp handled empty lists. Anyway, if you
    want Scheme, you know where it is.

    I consider continuations to be most distingushing feature of
    Scheme. I have no use for continuations, but I need UNWIND-PROTECT.
    I need multidimensional arrays. I need good performance and
    portability to wide range of platforms. Common Lisp almost gives
    me this, that is reasonably good performance on major platforms
    and portablity at somewhat reduced performance to wide range of
    platforms. And I want reasonable compile time. ATM I am
    not aware of Scheme implementation that has features that I
    need.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.edu.languages.natural on Mon Aug 24 20:07:01 2026
    From Newsgroup: comp.lang.lisp

    On 10/08/2026 6:49 AM, steve g wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:

    I try to keep in shape by reading books in languages I'm not using. Or
    converse with people about programming languages I don't use anymore,
    such as Pascal.

    I've managed to keep my French more or less intact, but could use a
    brush up on Danish, and of course German as I said. I'm sure I'll
    find something to inspire me to keep practicing German. After all,
    I'm struggling to read Asterisk and Obelisk in Latin.


    Best wishes, and happy language studies in comp.lang.lisp!


    Have you tried shortwave radio? You'll get all kinds of people talking different languages; not to mention it is rather entertaining.

    Dear steve g,

    I admit I did not consider shortwave radio for language learning. A
    friend of mine suggested we'd group up and learn French together, and
    we're currently planning to visit Alliance Francaise this week. I hope
    that works out.

    I mean, I'll be renewing my own knowledge, and she'll be learning from
    scratch. I'm sure both of us will have lots of fun.

    I've added comp.edu.languages.natural to this discussion.


    Happy French in comp.lang.lisp!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 12:22:13 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    I have no idea what you're talking about.

    You really don't, no.

    Hint: I am not talking about whether you know the language you are using
    well enough, but whether the language you are using provides the constructs
    you need to address the problem you are solving in it succinctly.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 12:31:36 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I believe you are wrong about Python's popularity. Python is popular
    because of constant effort by /Python influencers/ such as our very own Lawrence D'Oliveiro. It's not exactly easy for anyone to use, in the
    long term.


    I can't think of any single thing that would put me off Python more than
    him.

    But more generally: no, I think this is false. For instance the existence
    of NumPy and a great number if libraries built on it have made a huge (and justified) difference to Python's popularity. Also remember that the
    choice for many tasks was shell script (very high ickyness, unsafe, no libraries), Perl (high ickyness, safe, libraries) or Python (low ickyness
    at first, safe, libraries). (Here 'safe' doesn't mean anything formal, it means things like no repeated evaluation of strings.)
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 12:49:32 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    What are you talking about? Of course it is a substitute for multiple values. It's a design decision per function to return either a list or multiple values, and each has its pros and cons.


    It is not, because you can ignore additional values (note Racket, at least,
    has got this spectacularly wrong). You can of course emulate multiple
    values with destructuring but it either makes every call look ugly or
    bloats the language by requiring functions which perform the same operation with two different interfaces. Example: gethash.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Stefan Monnier@monnier@iro.umontreal.ca to comp.lang.lisp on Sun Aug 23 23:08:27 2026
    From Newsgroup: comp.lang.lisp

    George Neuner [2026-08-22 18:13:00] wrote:
    Biggest obstacles [to Lisp] are closures, dynamic scoping, and GC -
    most everything else is transferrable from other languages.

    Closures and GC are covered by modern texts - explicit examples are
    sorely lacking, but the discussions are good enough that you can
    figure out how to implement things.

    Indeed closures and automatic memory management are nowadays supported
    by the vast majority of programming languages.

    Dynamic scoping - if you care - is something you really have to figure
    out on your own. Not that it's /that/ hard, but making it efficient
    and [possibly] dealing with multiple threads both are PITA.

    Efficiency was important back in the Maclisp days when all let-bindings
    used dynamic scoping. Nowadays you can expect that dynamically scoped let-bindings are relatively infrequent and thus in many settings they
    can tolerate naive implementations along the lines of

    (dlet ((VAR VAL)) EXP)
    ==>
    (let ((old (symbol-value 'VAR)))
    (unwind-protect
    (progn (set VAR VAL) EXP)
    (set VAR old)))

    and

    (defun symbol-value (var)
    (gethash (cons var (current-thread)) *dynamic-bindings*))

    (defun set (var val)
    (puthash (cons var (current-thread)) val *dynamic-bindings*))


    === Stefan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 13:18:29 2026
    From Newsgroup: comp.lang.lisp



    I simply accuse you of having poor reading comprehension, and even worse writing comprehension.

    Do you really think that a thread about language extensibility and whether
    any given language could have enough co structs to satisfy all posdible
    users of that language had suddenly changed topic to how familiar an
    individual was with a given language? Really? Oh well.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Mon Aug 24 09:56:05 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 24 Aug 2026 12:31:36 -0000 (UTC), tfb <tfb@work.it.out> wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    I believe you are wrong about Python's popularity. Python is popular
    because of constant effort by /Python influencers/ such as our very own
    Lawrence D'Oliveiro. It's not exactly easy for anyone to use, in the
    long term.


    I can't think of any single thing that would put me off Python more than
    him.

    +1


    But more generally: no, I think this is false. For instance the existence
    of NumPy and a great number if libraries built on it have made a huge (and >justified) difference to Python's popularity. Also remember that the
    choice for many tasks was shell script (very high ickyness, unsafe, no >libraries), Perl (high ickyness, safe, libraries) or Python (low ickyness
    at first, safe, libraries). (Here 'safe' doesn't mean anything formal, it >means things like no repeated evaluation of strings.)

    The problem with Python is that its wonderful libraries mostly could
    not be written /in/ Python because the implementations are so bloody
    slow.

    It's true that many high level languages make writing low level system
    code difficult or impossible - but Python is unique among the popular
    general purpose languages in that its performance is so bad as to make
    it effectively impossible to write /user/ code without using low level non-Python libraries.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 22:16:15 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 9:18 PM, tfb wrote:


    I simply accuse you of having poor reading comprehension, and even worse
    writing comprehension.

    Do you really think that a thread about language extensibility and whether any given language could have enough co structs to satisfy all posdible
    users of that language had suddenly changed topic to how familiar an individual was with a given language? Really? Oh well.


    Yes, because that's how human to human real world conversations work.
    Being strictly /on topic/ without any deviation is a social construct
    invented by psychopaths for psychopaths. It's because they can't deal
    with real human to human interactions, and have to /hide themselves/,
    and pretend.

    All. The. Time.

    You are being dangerously close to expose yourself as a psychopath, so I suggest you stop replying to me, and /touch grass/ or something.

    Side note, for people unfamiliar with the term psychopath in technology,
    please read this VICE article, and weep.


    https://www.vice.com/en/article/the-careers-that-attract-the-most-psychopaths-one-job-is-the-clear-winner/

    I have negative respect for psychopaths, for good reasons.


    Have a nice life outside of Usenet!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Mon Aug 24 10:24:26 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 23 Aug 2026 23:08:27 -0400, Stefan Monnier
    <monnier@iro.umontreal.ca> wrote:

    George Neuner [2026-08-22 18:13:00] wrote:
    Biggest obstacles [to Lisp] are closures, dynamic scoping, and GC -
    most everything else is transferrable from other languages.

    Closures and GC are covered by modern texts - explicit examples are
    sorely lacking, but the discussions are good enough that you can
    figure out how to implement things.

    Indeed closures and automatic memory management are nowadays supported
    by the vast majority of programming languages.

    Yes ... but I was talking about learning how to /implement/ them in
    the compiler that you are writing.


    Dynamic scoping - if you care - is something you really have to figure
    out on your own. Not that it's /that/ hard, but making it efficient
    and [possibly] dealing with multiple threads both are PITA.

    Efficiency was important back in the Maclisp days when all let-bindings
    used dynamic scoping. Nowadays you can expect that dynamically scoped >let-bindings are relatively infrequent ...

    In Lisp, that may be true. OTOH, dynamic scoping is useful enough
    that Racket has explicit support for it.

    https://docs.racket-lang.org/reference/parameters.html


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 19:29:43 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:
    On Sun, 23 Aug 2026 23:08:27 -0400, Stefan Monnier

    Efficiency was important back in the Maclisp days when all let-bindings
    used dynamic scoping. Nowadays you can expect that dynamically scoped
    let-bindings are relatively infrequent ...

    In Lisp, that may be true. OTOH, dynamic scoping is useful enough
    that Racket has explicit support for it.

    A thing can be both semantically important and not need an extremely
    efficient implementation. Dynamic binding being a really good example. Important enough (to me) that I had to implement it in Python but probably never having required a very efficient implementation.

    In particular Maclisp used dynamic scope only in the interpreter, unless variables were declared SPECIAL when the compiler would treat them the same way. Other Lisps of that era had similar semantics: Standard Lisp
    variables declared as FLUID had dynamic scope, otherwise they would have lexical scope but dynamic extent, for instance (there were also GLOBAL variables which had only toplevel bindings. Standard Lisp was a Lisp-1 and function names were global variables I think.

    I suspect elisp may be one of the few Lisps where dynamic bindings really
    once were the default everywhere. Turns out I had remembered a comment in
    the elisp new byte compiler source correctly: "No matter how hard you try,
    you can't make a racehorse out of a pig. you can, however, make a faster
    pig."
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 19:29:49 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:

    The problem with Python is that its wonderful libraries mostly could
    not be written /in/ Python because the implementations are so bloody
    slow.

    Exactly so: Python is the canonical scripting language. It irks me to say
    it, but such things can be useful, especially if you have shedloads of
    existing high-performance Fortran(-oid) code which needs glue.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Mon Aug 24 16:35:26 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:

    [...]

    The problem with Python is that its wonderful libraries mostly could
    not be written /in/ Python because the implementations are so bloody
    slow.

    It's true that many high level languages make writing low level system
    code difficult or impossible - but Python is unique among the popular
    general purpose languages in that its performance is so bad as to make
    it effectively impossible to write /user/ code without using low level non-Python libraries.

    So do you see Python as a glue language?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 20:10:08 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    Yes, because that's how human to human real world conversations work.
    Being strictly /on topic/ without any deviation is a social construct invented by psychopaths for psychopaths. It's because they can't deal
    with real human to human interactions, and have to /hide themselves/,
    and pretend.

    All. The. Time.

    You are being dangerously close to expose yourself as a psychopath, so I suggest you stop replying to me, and /touch grass/ or something.


    I must admit to being pretty amused by how quickly some random internet buffoon, who very obviously is not a native English speaker, has moved from accusing me of poor English reading comprehension rCo and 'writing comprehension', which as a native English speaker I assume must mean 'comprehensible writing', but I dunno rCo to saying I'm about to expose
    myself as a psychopath because I 'can't deal with human to human
    interactions' (which is ... funny). (I half expect the same person is now wondering whether I'm using an LLM because of the spaced dashes. Hint:
    no.)

    And now, because I admit to laughing at you, it will no doubt confirm
    whatever pop-psychology rubbish you want to believe about people you've
    never met and never will. No: quite ordinary people laugh at fools, it
    turns put: there's a whole genre of comedy based on that.

    So be it.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.lisp on Mon Aug 24 13:19:37 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    I have no idea what you're talking about.

    You really don't, no.

    Hint: I am not talking about whether you know the language you are using
    well enough, but whether the language you are using provides the constructs you need to address the problem you are solving in it succinctly.

    The person you're talking to has deliberately added cross-posts to comp.lang.misc and comp.lang.c. If you must reply to this troll,
    please limit your replies to comp.lang.lisp.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Mon Aug 24 20:37:30 2026
    From Newsgroup: comp.lang.lisp

    Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:

    The person you're talking to has deliberately added cross-posts to comp.lang.misc and comp.lang.c. If you must reply to this troll,
    please limit your replies to comp.lang.lisp.


    They did, didn't they. Sorry: my rather primitive newsreader makes that
    hard to see, but I should have noticed in any case. Sorry for wasting
    people's time (people who won't see this, but still, sorry).

    (I do have to wonder though: in the pop-psychology world, what term would
    be used for someone who adds a bunch of unrelated newsgroups in that way?)
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Mon Aug 24 18:34:06 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 24 Aug 2026 12:49:32 -0000 (UTC), tfb <tfb@work.it.out> wrote:

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:


    What are you talking about? Of course it is a substitute for multiple
    values. It's a design decision per function to return either a list or
    multiple values, and each has its pros and cons.


    It is not, because you can ignore additional values (note Racket, at least, >has got this spectacularly wrong).

    Holdover from Scheme which requires catching all returned values.

    However, Lisp has the failing that catching the 4th returned value
    requires catching the first 3 even though you don't care about them.


    You can of course emulate multiple
    values with destructuring but it either makes every call look ugly or
    bloats the language by requiring functions which perform the same operation >with two different interfaces. Example: gethash.

    What bugs me is that catching [however many] values with
    destructuring-bind in Lisp or the various *-values forms in Scheme
    requires unambigiously naming each of them.

    I actually prefer having to account for all the return values because
    I think it is less error prone - but I like to have syntax to ignore
    the values I have no interest in.

    Yes, I could create macros to do that - perhaps somebody already has -
    but other than date/time I just don't need to deal with multiple-value
    returns very often.

    YMMV.


    A while back I created a Modula3 inspired language that included
    multiple value returns, and used the underscore ('_') as a placeholder
    for ignored return values in calls.
    [I liked the visual of having a "hole" in the variable list.]

    ex:
    function somefunc( ... ): integer, integer, real, real;

    _ b c _ := somefunc( ... );
    w _ _ z := somefunc( ... );

    Similar to the way you'd use a dedicated single buffer for all leaf
    function stack frames, I used a single "junk" buffer as the target for
    any return value being ignored.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Mon Aug 24 16:45:20 2026
    From Newsgroup: comp.lang.lisp

    antispam@fricas.org (Waldek Hebisch) writes:
    I have no use for continuations, but I need UNWIND-PROTECT. I need multidimensional arrays. I need good performance and portability to
    wide range of platforms.

    I think dynamic-wind in Scheme is similar to UNWIND-PROTECT. Don't know
    about multi-dimensional arrays that aren't implementation specific, but depending what you're doing, you might want to go even further and use
    GPU bindings. You're probably more attuned than I am to the compiler situation. There have historically been some good compilers that
    weren't too slow, but IDK if they're currently maintained other than
    Racket.

    https://gambitscheme.org/ does seem to still be around. In fact it's
    more capable now than when I last looked at it. I might start playing
    with it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Mon Aug 24 16:59:02 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    Yes, because Clojure is a thing, but then you have to use the JVM, and
    not the Pythong interpreter, so that rules you out.

    I believe someone made a de-java-fied version of Clojure though I'm sure
    it still has lingering JVM smell. I've been wanting to look into it.

    Of more consequence, Lisp itself, especially in the 1990s and later,
    mostly gave way to languages with similar advantages and more direct applicability to common programming problems. Yes Python is one of
    those. Yes Python has quite a few attractions, and users don't
    experience its drawbacks much until they get more deeply into it. Yes I
    use it myself for my own routine tasks, only using other languages
    because of some inherent Python disadvantage (usually being too slow) or
    else because I want to use the other language for the sake of using it.

    The other main de facto Lisp replacement these days is Javascript, which
    has gotten very very capable, though I've managed to stay away from it
    because of the awful development culture around it (e.g. the notorious
    left pad library).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Mon Aug 24 17:10:51 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    Do you really think that a thread about language extensibility and whether any given language could have enough co structs to satisfy all posdible
    users of that language had suddenly changed topic to how familiar an individual was with a given language?

    Fluency does matter.

    If fluency in a language lets me do most of my daily tasks with at most occasional inconvenience, I'd call the language satisfactory. Stuff
    like macros make inconvenient things convenient. They don't make the impossible possible. And if the language makes enough everyday things convenient, it's ok with me if some inconvenient ones are left over.

    So I haven't felt lack of macros to be a serious shortcoming of non-Lisp languages. There are usually alternate mechanisms offered, like
    function decorators in Python.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Tue Aug 25 00:13:31 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 23 Aug 2026 00:23:20 -0000 (UTC), Waldek Hebisch wrote:

    The problem which I can not solve is that empty list is printed as 'COMMON-LISP:NIL' instead of '()'. And Common Lisp functions still
    will treat empty list as a symbol.

    So you have a problem with Common Lisp. Yet another reason, to me, why
    itrCOs a specification that is only museum-worthy at this point, not fit
    for production use today.

    Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    I can think of one: multiple-value-return. This requires the
    creation of a whole mechanism involving data structures that are
    not really data structures.

    multiple-value-return is a different story. One can easily get
    equivalent effect with explict stack.

    Explicit operand stacks have their own issues, not really relevant to
    this point.

    But AFAICS motivation for multiple values is to generate more
    efficient code and more efficient implementation will return first
    few values in machine registers.

    Nothing to prevent the implementation of destructuring assignment from
    doing the same.

    rCLPremature optimization is the root of all evil.rCY
    -- variously attributed to Donald Knuth or Tony Hoare

    That saves allocation of intermediate container that would became
    garbage after return.

    This is why some more modern languages, like Perl and Python, use reference-counting as a first resort, only falling back to garbage
    collection when they cannot avoid it. The temporary multivalue
    structure created in such a case can be immediately disposed after the assignment.

    A language design is not just a bunch of language features, but how
    they interact. The interaction between features in Common Lisp
    requires you to do things in a certain way, that makes it hard to
    benefit from more modern design concepts.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.edu.languages.natural on Mon Aug 24 17:13:30 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:
    I admit I did not consider shortwave radio for language learning.

    You could also try Youtube. But it's best to do it in real-life face to
    face conversations.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Tue Aug 25 00:18:36 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 24 Aug 2026 12:02:33 -0000 (UTC), Waldek Hebisch wrote:

    I consider continuations to be most distingushing feature of Scheme.

    Continuations are cool! I was disappointed to discover theyrCOre not
    considered a normal part of Lisp.

    I implemented my own little language which is closely modelled on
    PostScript, but drops the antiquated graphics model and adds lexical
    binding and continuations. It is true that the combination of an
    explicit operand stack with continuations can get a bit mind-boggling
    at times ...

    <https://gitlab.com/ldo/gxscript>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp on Tue Aug 25 10:26:42 2026
    From Newsgroup: comp.lang.lisp

    On 24/08/2026 10:24 PM, George Neuner wrote:
    On Sun, 23 Aug 2026 23:08:27 -0400, Stefan Monnier
    <monnier@iro.umontreal.ca> wrote:

    George Neuner [2026-08-22 18:13:00] wrote:
    Biggest obstacles [to Lisp] are closures, dynamic scoping, and GC -
    most everything else is transferrable from other languages.

    Closures and GC are covered by modern texts - explicit examples are
    sorely lacking, but the discussions are good enough that you can
    figure out how to implement things.

    Indeed closures and automatic memory management are nowadays supported
    by the vast majority of programming languages.

    Yes ... but I was talking about learning how to /implement/ them in
    the compiler that you are writing.

    Indeed, that is lacking. There's more stuff that's lacking in the
    compiler literature, but let's stick to those for now.

    For closures, they are somewhat easy, for some value of easy, but not
    at all obvious for the budding compiler programmer. And please forgive
    my somewhat superficial coverage of the topic. Right now I'm not in a
    position to browse through my library, nor experiment before this
    followup.

    I'll tentatively refer to Appel's /Compiling with Continuations/ and
    Christian Queinnec's /Principes d'Implamantation de Scheme et Lisp/ for
    tips on how to implement this.

    When we are talking about implementing Common Lisp in particular, or a
    language with closure in the general, we have to realize the implementa-
    tion of the function -- the binary code, if you will -- has to have a
    reference to the outer environment where all the /closed over/ -- I
    think that's the term -- variables are kept. This is of course not only
    to be able to manipulate the variables and not just local copies, but to
    keep references for the garbage collector not to collect them on its
    next run.

    Exactly how to keep this reference I leave as an /exercise for the
    reader/ and genuinely hope my book references are not far off.

    On the garbage collector itself, the book /Garbage Collection Handbook/,
    whose second edition is by Richard Jones, Antony Hosking, and Eliot Moss
    isn't all that helpful. Or at least, the first edition wasn't, and I'm
    not that hopeful it's been changed in the second edition. A budding
    compiler writer is necessitated to dig up the most pertinent references,
    and try to implement from them -- if at all going by the book.

    And by this I mean the advanced topics. Reference counting and a basic
    mark sweep collectors are covered reasonably well enough, and can be implemented directly from the book.

    It's when we start to think about threading that things become diffi-
    cult. And it's possible this gap in the garbage collector literature
    is what resulted in the Python's /global interpreter lock/, but I'm not
    Guido van Rossum, and cannot speak for his decision making.

    This global interpreter lock has made the default Python runtime
    environment extremely slow for decades, and I'm not digging up exactly
    how it's been fixed recently. For that I give the word to Lawrence
    D'Oliveiro -- I hope I got his name right this time -- who is our very
    own Pythong influencer, and knows exactly how the garbage collector in
    Pythong works.

    So a budding compiler writer is relegated to reading the implementation
    of Ravenbrook's /Memory Pool System/, or -- gasp -- even Boehm's et al.
    garbage collector for C and C++; and try to learn from the great
    masters that way.

    The most pernicious problem with that is a lot of people don't even know Ravenbrook's /Memory Pool System/ even exists. Therefore the budding
    compiler writer can't read it; and is often only told about Boehm's et
    at. collector -- and I must confess I haven't read its source code yet.



    Dynamic scoping - if you care - is something you really have to figure
    out on your own. Not that it's /that/ hard, but making it efficient
    and [possibly] dealing with multiple threads both are PITA.

    Efficiency was important back in the Maclisp days when all let-bindings
    used dynamic scoping. Nowadays you can expect that dynamically scoped
    let-bindings are relatively infrequent ...

    In Lisp, that may be true. OTOH, dynamic scoping is useful enough
    that Racket has explicit support for it.

    https://docs.racket-lang.org/reference/parameters.html




    In this followup I chose not to comment on /dynamic scoping/. Happy
    compiling Common Lisp to binary code!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Tue Aug 25 10:34:47 2026
    From Newsgroup: comp.lang.lisp

    On 25/08/2026 4:10 AM, tfb wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    Yes, because that's how human to human real world conversations work.
    Being strictly /on topic/ without any deviation is a social construct
    invented by psychopaths for psychopaths. It's because they can't deal
    with real human to human interactions, and have to /hide themselves/,
    and pretend.

    All. The. Time.

    You are being dangerously close to expose yourself as a psychopath, so I
    suggest you stop replying to me, and /touch grass/ or something.


    I must admit to being pretty amused by how quickly some random internet buffoon, who very obviously is not a native English speaker, has moved from accusing me of poor English reading comprehension rCo and 'writing comprehension', which as a native English speaker I assume must mean 'comprehensible writing', but I dunno rCo to saying I'm about to expose myself as a psychopath because I 'can't deal with human to human interactions' (which is ... funny). (I half expect the same person is now wondering whether I'm using an LLM because of the spaced dashes. Hint:
    no.)

    And I must admit being pretty amused by people whose only claim to
    language skills is to be /born in a country/. You may laugh, you may
    cry, I don't give a shit. The thing is, people with poor reading
    comprehension don't know it. They always, always, accuse the other
    person of being /poor at communicating/, and often cannot be corrected
    because they don't believe they can possibly be in the wrong.

    Thank you for proving my point about your poor reading comprehension.

    And just like Lewis Carrol when he wrote Alice in Wonderland, or Through
    the Looking Glass -- I don't care which book had this quote -- I use my
    words to mean what I mean, and not what you decide it means.

    And now, because I admit to laughing at you, it will no doubt confirm whatever pop-psychology rubbish you want to believe about people you've
    never met and never will. No: quite ordinary people laugh at fools, it
    turns put: there's a whole genre of comedy based on that.

    So be it.


    Fools laugh at people wiser than them, that's true. Thank you for prov-
    ing to me you're a fool.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Tue Aug 25 10:41:57 2026
    From Newsgroup: comp.lang.lisp

    On 25/08/2026 8:10 AM, Paul Rubin wrote:
    tfb <tfb@work.it.out> writes:
    Do you really think that a thread about language extensibility and whether >> any given language could have enough co structs to satisfy all posdible
    users of that language had suddenly changed topic to how familiar an
    individual was with a given language?

    Fluency does matter.

    If fluency in a language lets me do most of my daily tasks with at most occasional inconvenience, I'd call the language satisfactory. Stuff
    like macros make inconvenient things convenient. They don't make the impossible possible. And if the language makes enough everyday things convenient, it's ok with me if some inconvenient ones are left over.

    So I haven't felt lack of macros to be a serious shortcoming of non-Lisp languages. There are usually alternate mechanisms offered, like
    function decorators in Python.

    Thank you Paul. Now, if we're in the realm of impossible, there's very
    little that can be said to be truly /impossible/ in Common Lisp. This
    is because compilers like Steel Banks Common Lisp not only compile to
    pure binary code, they also offer Lisp syntax to just write the function
    in assembly. This is apparent to anyone who's delved into the inner
    guts of the compiler.

    Now, when we can just casually switch over to the assembly language, the /impossible/ is limited by the capabilities of the machine, and our
    patience to get whatever we want done.

    I mean, we can -- with enough patience and understanding, and reading of
    the code -- just overwrite the Common Lisp compiler, and the binaries it generates.

    I believe that's impossible in Python, so again I invite Lawrence D'Oli-
    veiro to correct me.

    And on the subject of macros, we can always template program like it's
    1976, and create our own textual code generator like Yacc. Though we
    don't have to create one in the context of parsing. This trick works
    equally in Python, and Common Lisp, but is for some reasons hardly ever
    used in practice today. Everyone seems to be hell bent on having the programmability of the programming language itself embedded in the de-
    fault compiler. Why is that?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Tue Aug 25 07:54:49 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> wrote:


    However, Lisp has the failing that catching the 4th returned value
    requires catching the first 3 even though you don't care about them.


    In CL this is what NTH-VALUE is designed to avoid (a na|>ve implementation
    does capture all the values but I expect implementations optimize it
    completely away in many good cases).


    What bugs me is that catching [however many] values with
    destructuring-bind in Lisp or the various *-values forms in Scheme
    requires unambigiously naming each of them.

    [...]

    A while back I created a Modula3 inspired language that included
    multiple value returns, and used the underscore ('_') as a placeholder
    for ignored return values in calls.
    [I liked the visual of having a "hole" in the variable list.]


    This is what I do. For instance

    (destructuring-match x
    ((_ _ v) ...)
    ...)

    and

    (for ((_ (in-naturals 10))
    ...)
    ...)

    I need to change my let-values macro to do the same thing, in fact.

    This is a really good case for language extensibility: the language you
    have is missing a feature which makes programs a pain to write and read (unneeded variables, and IGNORE declarations needed, but in fact unless you know more than you should need to about the implementation you likely need IGNORABLE (and then you give up on warnings you'd like to have so ...), so
    you just incrementally implement what you'd like on top of it.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Tue Aug 25 07:54:50 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:

    I think dynamic-wind in Scheme is similar to UNWIND-PROTECT.

    dynamic-wind has to deal with control in both directions because of continuations. The poster-child usage for UNWIND-PROTECT is implementing something like WITH-OPEN-FILE, which ensures a file gets closed on exit
    from a dynamic extent. Now add continuations and be endlessly entertained.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp,comp.lang.misc,comp.lang.c on Tue Aug 25 09:22:44 2026
    From Newsgroup: comp.lang.lisp

    oPaul Rubin <no.email@nospam.invalid> wrote:

    Fluency does matter.

    Absolutely so. Interestingly it's possible to not be fluent in languages
    (or language constructs) that you've designed: after Zyni and I wrote +atar
    (an iteration construct for CL), it took me months to become comfortable
    enough in it to use it to the exclusion of most of the standard ones. Some
    of this was worry about how large the support for it was (entirely silly on modern systems) and performance (we had benchmarks, but somehow these
    didn't help convince me), but part of it was just 'how do I get it to do
    that, erm ...'.


    If fluency in a language lets me do most of my daily tasks with at most occasional inconvenience, I'd call the language satisfactory. Stuff
    like macros make inconvenient things convenient. They don't make the impossible possible. And if the language makes enough everyday things convenient, it's ok with me if some inconvenient ones are left over.

    So I haven't felt lack of macros to be a serious shortcoming of non-Lisp languages. There are usually alternate mechanisms offered, like
    function decorators in Python.


    And that's fine. There are people for whom Fortran (I mean FORTRAN,
    probably, because modern Fortran is a large and flexible language only
    really related to anything older than Fortran 90 by some backward compatibility) is a language in which they are fluent and who feel no need
    for any other language. There is absolutely nothing wrong with that.

    But if I asserted that nobody should want a language other than FORTRAN,
    that would probably be something quite a lot of people would take issue
    with. And they would be right.

    If I asserted that *any single* programming language should be something
    every person is comfortable with then I think people would take issue with that, as well. There would probably be some extremists who would say,
    well, if only everyone saw and understood the blinding light of (Python|Ruby|Lisp) then they would achieve true happiness. But those
    people are pushing what is essentially a cult. And empirically those
    people are just wrong: if they were right, why are there so many
    programming languages? Why are there both Python cultists and Ruby
    cultists if there is more than one true language? Do we need some kind of purge of the nonbelievers?

    Well, perhaps there is some finite and fairly small set of languages that
    would meet everyone's requirements for comfort? If that were so, why do
    people endlessly invent new ones? If there is a finite set, we're clearly
    not close to reaching it yet.

    I suggest that the set of languages which would mean *everyone* was
    comfortable is not usefully finite. If hardware architecture was
    unchanging and there was a fixed set of problem domains it conceivably
    might be, but neither of those things is true. Modern Fortran has grown
    all sorts of new constructs designed to deal with what modern
    supercomputers look like, for instance.

    Language exploration and modification therefore matters. It may not matter
    for you, or for me: we may be fluent in and comfortable with our fixed languages (they might even be the same language). But *that means
    nothing*: it still matters.

    And (this is the contentious bit): I think that, since it matters, removing barriers to it also matters. It will never be easy, but it shouldn't
    require designing a whole new language to explore one idea. It should be possible to write functions in an existing language which map constructs expressing that new (or borrowed) idea into the existing language. Those functions have a name: macros. You may not want to use them: that is not
    an argument that they are not useful to other people, and to pretend it is would be as grotesquely arrogant as if I was to say that because *I* have
    no use for a church it should be demolished.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Madhu@enometh@meer.net to comp.lang.lisp on Wed Aug 26 07:47:18 2026
    From Newsgroup: comp.lang.lisp

    * George Neuner <73cp8lp5mo0cjf30neekrvt2611hckn72j@4ax.com> :
    Wrote on Mon, 24 Aug 2026 18:34:06 -0400:
    It is not, because you can ignore additional values (note Racket, at least, >>has got this spectacularly wrong).

    Holdover from Scheme which requires catching all returned values.

    However, Lisp has the failing that catching the 4th returned value
    requires catching the first 3 even though you don't care about them.

    this was covered upthread where it was mentioned that you can ignore the
    [first three] values, so the compiler [in theory] can not catch them.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Wed Aug 26 02:58:28 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 26 Aug 2026 07:47:18 +0530, Madhu wrote:

    However, Lisp has the failing that catching the 4th returned value
    requires catching the first 3 even though you don't care about
    them.

    this was covered upthread where it was mentioned that you can ignore
    the [first three] values, so the compiler [in theory] can not catch
    them.

    This is the old multiple-value-return rigmarole, isnrCOt it?

    Destructuring assignment is so much cleaner.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Tue Aug 25 22:13:06 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:
    There would probably be some extremists who would say, well, if only
    everyone saw and understood the blinding light of (Python|Ruby|Lisp)
    then they would achieve true happiness.

    The Blub fallacy. Yes it applies to CL just like to anything else.

    It should be possible to write functions in an existing language which
    map constructs expressing that new (or borrowed) idea into the
    existing language. Those functions have a name: macros.

    Meh, if the old language can express the new idea at all, then the new
    idea isn't that big of a change. Like try implementing Scheme
    continuations as macros in CL.

    There's a theoretical paper by Felleisen about what really adds
    expressive power to programming languages. Sadly, I don't understand
    it, but maybe someday.

    https://www2.ccs.neu.edu/racket/pubs/scp91-felleisen.pdf
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Madhu@enometh@meer.net to comp.lang.lisp on Wed Aug 26 11:33:37 2026
    From Newsgroup: comp.lang.lisp

    * Paul Rubin <87fr01mplp.fsf@nightsong.com> :
    Wrote on Tue, 25 Aug 2026 22:13:06 -0700:

    The Blub fallacy. Yes it applies to CL just like to anything else.

    Caveat.

    Blub a bunch of other modern "fallacies" is a product of "israeli
    propaganda". it does not automatically apply, and is wont to be applied
    in situations it does not apply, for propagnda points.

    the fallacy itself is cleverly constructed as a thought engineering brainwashing mindcontrol tool, and the application to argument serves
    the purpose of identifying those who apply the argument, rather than
    those on whom the argument is directed. (kindof like dunning-kruger)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Wed Aug 26 00:56:45 2026
    From Newsgroup: comp.lang.lisp

    St|-phane CARPENTIER <sc@fiat-linux.fr> writes:
    The fact is that LISP is almost never used is the real life. I know
    stump, nyxt and guix are LISP programs,

    I'd say LISP gave special abilities to programmers 50 years ago. More
    recently though, other approaches started giving similar abilities, so
    the abilities aren't so special, and Lisp (CL anyway) became old
    fashioned, though still useful and interesting to some of us. The
    spelling "LISP" gave way to "Lisp" sometime around 1980 maybe.

    To add a note of cheer, there's a famous quote from Edsger W. Dijkstra's
    Turing award lecture of 1972:

    With a few very basic principles at its foundation, it [LISP] has
    shown a remarkable stability. Besides that, LISP has been the
    carrier for a considerable number of in a sense our most
    sophisticated computer applications. LISP has jokingly been
    described as "the most intelligent way to misuse a computer". I
    think that description a great compliment because it transmits the
    full flavour of liberation: it has assisted a number of our most
    gifted fellow humans in thinking previously impossible thoughts.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.misc,comp.lang.c on Wed Aug 26 15:43:38 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    tfb <tfb@work.it.out> writes:
    There would probably be some extremists who would say, well, if only
    everyone saw and understood the blinding light of (Python|Ruby|Lisp)
    then they would achieve true happiness.

    The Blub fallacy. Yes it applies to CL just like to anything else.

    It should be possible to write functions in an existing language which
    map constructs expressing that new (or borrowed) idea into the
    existing language. Those functions have a name: macros.

    Meh, if the old language can express the new idea at all, then the new
    idea isn't that big of a change. Like try implementing Scheme
    continuations as macros in CL.

    Doug Hoyte does it in Let Over Lambda. But even if we have here a case
    where things don't work out so well, one case won't break the efficacy
    of all other cases.

    There's a theoretical paper by Felleisen about what really adds
    expressive power to programming languages. Sadly, I don't understand
    it, but maybe someday.

    https://www2.ccs.neu.edu/racket/pubs/scp91-felleisen.pdf

    Care to share what you don't understand about the paper? I suppose the
    subject is still interesting to the newsgroups addressed here, though it
    leans more towards comp.lang.misc and comp.theory and sci.logic.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From tfb@tfb@work.it.out to comp.lang.lisp on Wed Aug 26 19:06:27 2026
    From Newsgroup: comp.lang.lisp

    [I have removed groups other than comp.lang.lisp, because some troll keeps adding them]

    Paul Rubin <no.email@nospam.invalid> wrote:


    Meh, if the old language can express the new idea at all, then the new
    idea isn't that big of a change. Like try implementing Scheme
    continuations as macros in CL.

    *On Lisp* does this (the code is rather questionable by today's standards
    but could be cleaned up). Based on some casual web searching there's at
    least one other person who has.

    And that's the point: languages which make this kind extension easy (which needs more than just functions between ASTs) remove barriers to the
    creation of new languages. Those new languages might be anything from CL
    (a much smaller Lisp with a bunch of fancy macros), CL with new binding or iteration or other constructs to entirely new languages like Coalton (statically-typed functional language) to whatever.

    I think that not having these barriers is a good thing. I'd really like to
    see a coherent argument *against* that position, which is not 'everyone
    will end up using their own idiolect', but I haven't so far.
    --
    tfeb.org/computer/
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp on Wed Aug 26 19:55:37 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    St|-phane CARPENTIER <sc@fiat-linux.fr> writes:
    The fact is that LISP is almost never used is the real life. I know
    stump, nyxt and guix are LISP programs,

    I'd say LISP gave special abilities to programmers 50 years ago. More recently though, other approaches started giving similar abilities, so
    the abilities aren't so special, and Lisp (CL anyway) became old
    fashioned, though still useful and interesting to some of us. The
    spelling "LISP" gave way to "Lisp" sometime around 1980 maybe.

    To add a note of cheer, there's a famous quote from Edsger W. Dijkstra's Turing award lecture of 1972:

    With a few very basic principles at its foundation, it [LISP] has
    shown a remarkable stability. Besides that, LISP has been the
    carrier for a considerable number of in a sense our most
    sophisticated computer applications. LISP has jokingly been
    described as "the most intelligent way to misuse a computer". I
    think that description a great compliment because it transmits the
    full flavour of liberation: it has assisted a number of our most
    gifted fellow humans in thinking previously impossible thoughts.

    Very nice and all, but let's not forget the sheer joy of writing Lisp on
    a daily basis. Its beauty and joy of using it is really not only due to
    making sophisticated impossible thoughts possible. It's still my pick
    for the very mundane thing that people sometimes say nothing beats <pick-your-language>. Common Lisp with the GNU EMACS and
    paredit-mode---it's simply the most joyous code writing experience.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp,comp.lang.misc,comp.lang.c on Wed Aug 26 18:23:24 2026
    From Newsgroup: comp.lang.lisp

    Anton Antimo <anton@safunu.org> writes:
    Like try implementing Scheme continuations as macros in CL.
    Doug Hoyte does it in Let Over Lambda.

    I don't see how that is possible, other than by using the Turing
    completeness of CL macros to implement Scheme, more or less.
    Continuations automatically give you stackful coroutines and that
    requires runtime support that's not built into CL. I haven't read that
    book though.

    https://www2.ccs.neu.edu/racket/pubs/scp91-felleisen.pdf
    Care to share what you don't understand about the paper?

    It's written in the academic language of PL theory, which I haven't
    studied enough to make sense of what the paper is saying.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From bixbox@noreply@example.invalid to comp.lang.lisp on Thu Aug 27 07:57:36 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    Paul Rubin <no.email@nospam.invalid> wrote:


    Meh, if the old language can express the new idea at all, then the new
    idea isn't that big of a change. Like try implementing Scheme
    continuations as macros in CL.
    And that's the point: languages which make this kind extension easy (which needs more than just functions between ASTs) remove barriers to the
    creation of new languages. Those new languages might be anything from CL
    (a much smaller Lisp with a bunch of fancy macros), CL with new binding or iteration or other constructs to entirely new languages like Coalton (statically-typed functional language) to whatever.

    I think the elegance of lisp macro is that is nothing more that regular
    lisp syntax that transform homoiconic lisp, with just structural transformation,
    other language have a very poor macro system that is completely alien to the language himself.

    In my opinion C++ templates are a basically a simpler macro system but C++ templates have
    nothing to do with the core C++ in term of syntax and features.

    bix
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Thu Aug 27 14:43:07 2026
    From Newsgroup: comp.lang.lisp

    In comp.lang.c Paul Rubin <no.email@nospam.invalid> wrote:
    Anton Antimo <anton@safunu.org> writes:
    Like try implementing Scheme continuations as macros in CL.
    Doug Hoyte does it in Let Over Lambda.

    I don't see how that is possible, other than by using the Turing
    completeness of CL macros to implement Scheme, more or less.
    Continuations automatically give you stackful coroutines and that
    requires runtime support that's not built into CL. I haven't read that
    book though.

    One way to implement continuations is to convert program to
    "continuation passing style" and have garbage collection of
    the stack. Continuation passing style means that you explicitely
    pass next function to call to each function. And normally
    functions do not return, simply tail-call to passed
    "continuation". This transform could be done by a macro,
    a hairy one as it needs to walk over arbitrary Lisp form
    and transform each call to user function inside them. After
    such transformation there will be a lot more of stack frames
    than before. Most of the stack frames will be unreachable.
    Without garbage collection of the stack you will rather
    quickly run out of stack space. If implementation is garbage
    collecting stack frames, then the code will run OK.

    In principle one can get a bit further than that. Namely, if
    all calls are tail calls and there is no need to preseve data
    in the stack frame (in particular no closure references the
    data), then good implementation will immediately reclaim the
    stack frame. So a macro could put all needed data in heap
    allocated data structure, so that nontrivial part of garbage
    collection is done by normal garbage collection and on the
    stack one only need the easy case.

    That basically is equvalent to treating Lisp as a garbage
    collected assembly language, with tail calls performing duty
    of goto. The macro works as a compiler from AST-s to this
    assembly language. One still gets benefits of reusing
    garbage collector. OTOH macros play kind of trivial role
    here, they allow you to pretend that the new language is
    part of Common Lisp by mixing CL code with new code inside
    the same file and without explicit markers indicating which
    language is in use. But clearly, if you do not ever return
    from a function, then UNWIND-PROTECT will not work as intended.
    Calling convention is clearly incompatible with Lisp one,
    so one will need a kind of FFI to perform calls between Lisp
    and new language. And since Lisp does not obey continuation
    passing convention semantics will be hairy if there is a
    nontrivial interaction.

    Concerning macros: continuation passing transformation can be
    programmed in any language and effort to do so will be comparable
    for languages that have good support for handling tree-like
    data structures. Validity of the apprach depends on tail call
    optimization, but that is available in implementations of
    several languages. For languages without macros the most
    natural way is to put code in new language in separate files.
    In a language without REPL one can use some syntactic markers
    to mix code in host language with new one. If there is a REPL
    and say EVAL, than one can implement new REPL for the new
    language. If the host language (like Lisp) has convenient
    notation for defining AST-s, then one can write AST-s for new
    language in host language and than pass them to the compiler.

    Anyway, once macros get hairy they need similar effort as
    alternative approches.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Thu Aug 27 20:39:38 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 27 Aug 2026 14:43:07 -0000 (UTC), Waldek Hebisch wrote:

    One way to implement continuations is to convert program to
    "continuation passing style" and have garbage collection of the
    stack. Continuation passing style means that you explicitely pass
    next function to call to each function. And normally functions do
    not return, simply tail-call to passed "continuation".

    The way I did this in GXScript was to implement stack frames as
    heap-based CallFrame objects, linked together in various ways. The
    interpreter context includes a pointer to the rCLcurrent framerCY, which
    in turn contains a pointer to the current procedure being executed,
    and the position within that procedure.

    Various transfer-of-control actions (return, yield etc) switch out the
    current frame for another by following relevant pointers in it to
    other frames. Conversely, entry into a new procedure means creating a
    new CallFrame around it, storing a pointer to the previously-current
    CallFrame in its rCLreturn_torCY field, and setting the new frame as
    current.

    A Continuation object is a wrapper around a CallFrame which is cloned
    and kept as a template. The rCLenter()rCY method on the Continuation
    creates a new clone of the associated CallFrame template, and sets it
    as the current frame in the interpreter context.

    Nothing too complicated, really ...

    <https://gitlab.com/ldo/gxscript>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Thu Aug 27 19:11:52 2026
    From Newsgroup: comp.lang.lisp

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:

    On Mon, 24 Aug 2026 12:02:33 -0000 (UTC), Waldek Hebisch wrote:

    I consider continuations to be most distingushing feature of Scheme.

    Continuations are cool! I was disappointed to discover theyrCOre not considered a normal part of Lisp.

    I never could understand them.

    I implemented my own little language which is closely modelled on
    PostScript, but drops the antiquated graphics model and adds lexical
    binding and continuations. It is true that the combination of an
    explicit operand stack with continuations can get a bit mind-boggling
    at times ...


    I think postscript can drive you bonkers alone, continuations dunno?

    <https://gitlab.com/ldo/gxscript>
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Fri Aug 28 17:38:21 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    steve g <Sgonedes1977@gmail.com> wrote:


    I don't follow.


    Consider (with-current-readtable (...) <form>): what is the current
    readtable when <form> is read?

    *readtable*.

    I actually like using start end clauses. I use this in my rule engine.

    (rule-file "ex1")

    code

    (rule-file :end)


    Like this then you do not get the extra indentation, and you can store
    more than one set of rules in a file.

    I do not like using reader-macros because. I would like to have

    it usually looks like this.

    (eval-when (:compile-toplevel :load-toplevel :execute)
    (defparameter *emacs-readtable*
    (let ((rt (copy-readtable nil)))
    (set-macro-character #\[ #'emacs-key-reader t rt)
    (set-syntax-from-char #\] #\) rt)
    rt))
    #+excl (setf (excl:named-readtable :emacs) *emacs-readtable*))

    (defmacro in-emacs-readtable ()
    "Initialize emacs readtable"
    `(eval-when (:compile-toplevel :load-toplevel :execute)
    (setq *readtable* *emacs-readtable*)))


    (with-current-readtable (*emacs-readtable*)
    ( #[Control-x (Meta A) ] )
    ) ;; now switch back to normal readtable.


    Yes, we all see the EXCL:named-readtable. This was a very old issue. For
    the sake of efficiency you don't want 96 reader macros. dig.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Fri Aug 28 17:43:50 2026
    From Newsgroup: comp.lang.lisp

    C||il|!n Niocl|is|!n Glost|-ir <thanks-to@Taf.com> writes:

    Steve G <Sgonedes1977@GMail.com> wrote: |---------------------------------------------------------------------|
    |"> Dear Mister Stephen G: |
    |
    I had bought many books. They have been robbed. I never got to read|
    them :( |
    | |
    |same here." | |---------------------------------------------------------------------|

    Dear Mister Steve G:

    I am sorry and I empathize :(


    They even took my mouse and the manual to my lisp machine. The thought
    it was selling drugs online. In the days of BBS there was a door call
    drug dealer or something - dunno I don't usually play with doors. Man oh
    Man!

    They broke my ceiling tiles; looking for marijuana! Like get a smart
    dog. How can you not notice the smell? anywayz...

    thank you for your support. It has only been about 20 years ago; I'm
    still pissed off.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Anton Antimo@anton@safunu.org to comp.lang.lisp,comp.lang.misc,comp.lang.c on Fri Aug 28 17:29:26 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    Anton Antimo <anton@safunu.org> writes:
    Like try implementing Scheme continuations as macros in CL.
    Doug Hoyte does it in Let Over Lambda.

    I don't see how that is possible, other than by using the Turing
    completeness of CL macros to implement Scheme, more or less.
    Continuations automatically give you stackful coroutines and that
    requires runtime support that's not built into CL. I haven't read that
    book though.

    I got that wrong. It turns out TFB posted in

    Message-ID: <116ndfj$st1q$1@dont-email.me>

    two days ago that Paul Graham does in ``On Lisp''.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Sat Aug 29 03:06:19 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> wrote:
    antispam@fricas.org (Waldek Hebisch) writes:
    And normally functions do not return, simply tail-call to passed
    "continuation".

    Continuations are nontrivial precisely because of the non-tail-call
    case, where the continuation is re-used. So you can use them to
    implement coroutines, multitasking, etc. If they can't do that, they're
    not "full" continuations. I don't see how to implement full
    continuations using CL macros.

    Le me try again. Do you see how to implement continuations at say
    assembler level? If not, then I affraid that CL macros will not
    help you. At assembly level each function has some machine code
    and environment. In simple case environment reduces to stack frame,
    it is created when function is invoked and destroyed when it exits.
    Closures complicate this, function may access lexical variable of
    containing functions and we must ensure that this access is possible
    even after retrun from containing function. Continations add similar
    problem, we can only discard a stack frame if it is not reachable
    via continations or closures. One possible way to do this is to have
    garbage collector capable of garbage collecting stack frame. But
    there is another possiblity, namely to keep only return address on
    the stack and keeping all other data in heap. In such case tail
    call optimization will ensure bounded stack use, so no need to
    garbage collect stack frames.

    As I wrote, idea is to treat Lisp as a garbage collected assembly
    language. With tail call optimization calls are translated to
    goto-s, so collection of Lisp functions can implement arbitrary
    control flow. If additinaly all local variables are collected
    into a data structure allocated at function entry and if needed
    passed as an extra argument, then your program at abstract level
    will work as before, but data which previously was stored on the
    stack is on the heap. After contination passing transformation
    you may support continations.

    How macros enter the picture: Lisp macro can perform arbitrary
    transformation, in particular can "compile" code into low
    level form indicated above. In a sense this is Turing completeness,
    but we avoid general argument going via interpretation and
    instead use compilation. And this clearly depends on ability
    to do non-local transformations. Simple AST substitution
    would be too weak.

    AFAICS main trouble with continuations is efficiency. If you
    do not need efficiency, then implementing continuations is just
    some extra work, but otherwise not a problem. Trouble is that
    relatively easy tactic of allocating stack frames on the heap
    puts serious load on garbage collector and on caches. If
    program is doing small number of function calls, then impact
    may be negligible. But people wanting continuations are
    likely to have a lot of function calls in their programs and
    speed is likely to suffer. So basically, you need to do
    some serious optimization work which would be unnecessery
    in language that does not implement continuations.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to comp.lang.lisp on Sat Aug 29 09:51:35 2026
    From Newsgroup: comp.lang.lisp

    On 2026-08-14, Stefan Ram wrote:

    Nuno Silva <nunojsilva@invalid.invalid> wrote or quoted:
    One I've seen used that's adequate is "Generative Autocomplete".

    The first "L" in "LLM" is what distinguishes those LLM from
    LMs which can be described as "glorified autocompleters".
    LLMs have additional features like emergent efficient internal
    representations of abstract concepts and their relations.

    Overall, I'd need to research more before having a formed opinion on how
    to assess this.

    But, from my limited experience and from examples I've seen: don't they
    still exhibit some of these "autocompletion" traits, just perhaps at a
    higher level?

    For one example, today's chatbots can follow meta-constraints
    (like, "Summarize this article in 50 words"). A raw model
    would just continue writing more text similar to the prompt.

    LLMs have recently solved some math problems human mathematicians
    were not able to solve for decades. There is no way you can subsume
    such behavior under "autocomplete".

    If it were subsumed, I'd not see that as a problem, sometimes the
    "right" ideas to try are hard to come by and having another source for
    these, even if it's infinite monkeys punching keyboards or an
    autocomplete, could prove useful, although there could be a SNR problem.

    If it's an "autocomplete at a higher level", that'd probably help a bit
    with the SNR. And if it's trained for that specific purpose, and isn't a centralized "cloud" service, its output may be more useful/relevant too.


    Now, while I did study some (basic/entry-level) stuff from the AI field
    that could be relevant here, I'd have to carefully refresh my knowledge
    of it, as well as read on the newer stuff, before being comfortable
    making more precise assessments.

    I do at least know enough to see that the AI field has a lot of useful
    tools, if used right, and that extend well beyond the current marketing
    hype with GenAI, that's apparently getting entangled into an Enron-esque accounting soap opera.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kragen Javier Sitaker@kragen@canonical.org to comp.lang.lisp,alt.folklore.computers,alt.sys.pdp10 on Sat Aug 29 17:52:49 2026
    From Newsgroup: comp.lang.lisp

    Alan Bawden <alan@csail.mit.edu> writes:
    Paul Rubin <no.email@nospam.invalid> writes:
    All CPython integers are boxed, but small ones (-5 through +250 or
    something like that) are pre-allocated. Sounds awful but I think some
    Lisps also have done that.

    For example, PDP-10 MacLisp. The PDP-10 is a word addressed machine,
    where addresses are 18 bits, and words are 36 bits. PDP-10 integers are
    36 bits long, so pretty much your only choice for representing fixnums
    is as an 18-bit pointer to a 36-bit signed integer, i.e. "boxed".

    I had no idea! Never having used it, I had always assumed that MACLISP
    shared the behavior of things like SBCL, Smalltalk, and recent versions
    of PythonrCerCorCetransparently overflowing from fixnums to bignums.

    One advantage of the transparent-overflow approach is that most of the
    time users donrCOt care what the actual fixnum limit isrCerCorCeitrCOs rCLjustrCY a
    performance optimization, in that your arithmetic starts consing when
    you exceed the limit.

    This does mean, however, that by default, for example on SBCL, all of
    your arithmetic is stuffed full of overflow checks, which has
    performance costs of its own.

    rCo If an intermediate fixnum needs to be allocated, say to pass as an
    argument to another function, it can be allocated in a special area
    of memory that has fixnum type, but that is managed as a stack -- the
    GC doesn't touch it. That temporary number is then popped out of
    existence after the function call returns. This does mean that the
    compiler has to constantly worry that an object that it is about to
    store someplace permanent might be a stack allocated "PDL number".
    The utility that replaces a potential PDL number with a permanent
    number is named "PDLNMK", and every serious MacLisp programmer knows
    exactly what it does because it frequently appears in our compiled
    code.

    This is an interesting idea; I imagine itrCOs a pretty big performance
    win, particularly since MACLISP predates generational garbage collection
    (and, I imagine, never had it bolted on). Consing *per se* is pretty
    fast in a pointer-bumping allocator; what used to kill you was the GC,
    and generational GC largely solved that problem. Still, I'm pretty sure
    that Java, LuaJIT, Chez Scheme, V8, and SpiderMonkey donrCOt box their
    fixnums.

    There's a paper by Guy Steele titled "Fast Arithmetic in MacLisp" that describes all these techniques in detail: <hdl.handle.net/1721.1/6279>.

    Thank you very much! IrCOd never read it. For the peanut gallery, thatrCOs AIM-421.pdf, MD5 158106732f63bf268ffe4c1728950710.

    Kragen
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Brinkhoff@lars.spam@nocrew.org to comp.lang.lisp,alt.sys.pdp10 on Sun Aug 30 06:43:50 2026
    From Newsgroup: comp.lang.lisp

    Kragen Javier Sitaker wrote:
    Alan Bawden wrote:
    There's a paper by Guy Steele titled "Fast Arithmetic in MacLisp"
    that describes all these techniques in detail:
    <hdl.handle.net/1721.1/6279>.

    Thank you very much! IrCOd never read it. For the peanut gallery,
    thatrCOs AIM-421.pdf

    I'll gratefully seize this opportunity to brag about "printing" some of
    these memos fresh from source.

    https://github.com/larsbrinkhoff/ai-memo-reprints/tree/master/mit/aim-421
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Sun Aug 30 02:01:26 2026
    From Newsgroup: comp.lang.lisp

    Nuno Silva <nunojsilva@invalid.invalid> writes:
    But, from my limited experience and from examples I've seen: don't they
    still exhibit some of these "autocompletion" traits, just perhaps at a
    higher level?

    This convinced me that more is going on: https://thegradient.pub/othello/

    See also: https://mathoverflow.net/a/514715/592598
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Alan Bawden@alan@csail.mit.edu to comp.lang.lisp,alt.folklore.computers on Sun Aug 30 17:24:39 2026
    From Newsgroup: comp.lang.lisp

    Kragen Javier Sitaker <kragen@canonical.org> writes:

    Alan Bawden <alan@csail.mit.edu> writes:
    For example, PDP-10 MacLisp. The PDP-10 is a word addressed machine,
    where addresses are 18 bits, and words are 36 bits. PDP-10 integers are
    36 bits long, so pretty much your only choice for representing fixnums
    is as an 18-bit pointer to a 36-bit signed integer, i.e. "boxed".

    I had no idea! Never having used it, I had always assumed that MACLISP shared the behavior of things like SBCL, Smalltalk, and recent versions
    of PythonrCerCorCetransparently overflowing from fixnums to bignums.

    One advantage of the transparent-overflow approach is that most of the
    time users donrCOt care what the actual fixnum limit isrCerCorCeitrCOs rCLjustrCY a
    performance optimization, in that your arithmetic starts consing when
    you exceed the limit.

    Note that MacLisp _does_ have "transparent-overflow" arithmetic, you
    just have to use `PLUS`, `TIMES` and `DIFFERENCE` instead of `+`, `*`
    and `-`. The `+` family is fixnum-only, but the `PLUS` family handles
    all types of numbers.

    There is also a flonum-only family: `+$`, `*$`, `-$`, etc.

    The names `PLUS`, `TIMES`, `DIFFERENCE`, etc. are taken from LISP 1.5,
    so you can think of them as the "true" Lisp arithmetic functions. `+`,
    `+$` and friends are just MacLisp extensions for efficient machine
    arithmetic.
    --
    Alan Bawden
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Kragen Javier Sitaker@kragen@canonical.org to comp.lang.lisp,alt.folklore.computers on Mon Aug 31 03:11:06 2026
    From Newsgroup: comp.lang.lisp

    Alan Bawden <alan@csail.mit.edu> writes:
    Kragen Javier Sitaker <kragen@canonical.org> writes:
    I had no idea! Never having used it, I had always assumed that MACLISP
    shared the behavior of things like SBCL, Smalltalk, and recent versions
    of PythonrCerCorCetransparently overflowing from fixnums to bignums.

    Note that MacLisp _does_ have "transparent-overflow" arithmetic, you
    just have to use `PLUS`, `TIMES` and `DIFFERENCE` instead of `+`, `*`
    and `-`. The `+` family is fixnum-only, but the `PLUS` family handles
    all types of numbers.

    I see! Thank you for explaining.

    Kragen
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp,comp.edu.languages.natural on Fri Sep 4 21:46:01 2026
    From Newsgroup: comp.lang.lisp

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> writes:


    Dear steve g,

    I admit I did not consider shortwave radio for language learning.

    Neither did I; I got into and argument with a blind fellow using a
    braille terminal. "I am a real shithead", I said.

    A
    friend of mine suggested we'd group up and learn French together, and
    we're currently planning to visit Alliance Francaise this week. I hope
    that works out.

    I don't know how good you at HAM, but france24 used to come in. It's
    usually english, but it is something.

    I just found these.

    9790 kHz (French to West Africa, evening UTC)
    11700 kHz (French to East/Central/West Africa, morning UTC)
    11790 kHz (French/African languages to West Africa)
    15300 kHz (RFI relays, daytime broadcasts)

    I wish I had the range. Let me know if you can get vietnam/china or HKJ Japanese news (they have great cooking shows!)


    I mean, I'll be renewing my own knowledge, and she'll be learning from scratch. I'm sure both of us will have lots of fun.

    I am very glad to hear this.


    I've added comp.edu.languages.natural to this discussion.


    Wonderful! Anychance to DX is the right one :)


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Fri Sep 4 22:15:12 2026
    From Newsgroup: comp.lang.lisp

    antispam@fricas.org (Waldek Hebisch) writes:

    Paul Rubin <no.email@nospam.invalid> wrote:
    antispam@fricas.org (Waldek Hebisch) writes:
    And normally functions do not return, simply tail-call to passed
    "continuation".

    Continuations are nontrivial precisely because of the non-tail-call
    case, where the continuation is re-used. So you can use them to
    implement coroutines, multitasking, etc. If they can't do that, they're
    not "full" continuations. I don't see how to implement full
    continuations using CL macros.


    Le me try again. Do you see how to implement continuations at say
    assembler level?

    I remeber, actually not really. I remeber this intel used to have a
    leave and enter statement. This would allow for local space for local
    functions and such. I believe they were called frames or leaves? dunno.
    it was a long time ago. This was before threads.

    If not, then I affraid that CL macros will not
    help you. At assembly level each function has some machine code
    and environment. In simple case environment reduces to stack frame,
    it is created when function is invoked and destroyed when it exits.
    Closures complicate this, function may access lexical variable of
    containing functions and we must ensure that this access is possible
    even after retrun from containing function. Continations add similar problem, we can only discard a stack frame if it is not reachable
    via continations or closures. One possible way to do this is to have
    garbage collector capable of garbage collecting stack frame.

    you just subtract the stack pointer assuming you're not using frames. (It has been a long time).


    But
    there is another possiblity, namely to keep only return address on
    the stack and keeping all other data in heap. In such case tail
    call optimization will ensure bounded stack use, so no need to
    garbage collect stack frames.

    I usually use alloca in C. that takes care of all this mess of
    assembler, CPU #/type , in terms of stack memory.


    As I wrote, idea is to treat Lisp as a garbage collected assembly
    language. With tail call optimization calls are translated to
    goto-s, so collection of Lisp functions can implement arbitrary
    control flow. If additinaly all local variables are collected
    into a data structure allocated at function entry and if needed
    passed as an extra argument, then your program at abstract level
    will work as before, but data which previously was stored on the
    stack is on the heap. After contination passing transformation
    you may support continations.

    How macros enter the picture: Lisp macro can perform arbitrary transformation, in particular can "compile" code into low
    level form indicated above. In a sense this is Turing completeness,
    but we avoid general argument going via interpretation and
    instead use compilation. And this clearly depends on ability
    to do non-local transformations. Simple AST substitution
    would be too weak.

    AFAICS main trouble with continuations is efficiency.

    this is the common complaint.

    If you do not need efficiency, then implementing continuations is just
    some extra work, but otherwise not a problem. Trouble is that
    relatively easy tactic of allocating stack frames on the heap puts
    serious load on garbage collector and on caches. If program is doing
    small number of function calls, then impact may be negligible. But
    people wanting continuations are likely to have a lot of function
    calls in their programs and speed is likely to suffer. So basically,
    you need to do some serious optimization work which would be
    unnecessery in language that does not implement continuations.

    I never could figure out call/cc .
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Tue Sep 15 15:18:12 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:


    They did, didn't they. Sorry: my rather primitive newsreader makes that
    hard to see, but I should have noticed in any case. Sorry for wasting people's time (people who won't see this, but still, sorry).


    I have been cought doing this myself.

    (I do have to wonder though: in the pop-psychology world, what term would
    be used for someone who adds a bunch of unrelated newsgroups in that way?)

    Nobody would read them.

    Some people are/were called spammers, flamers, market droids (automated advertisements).

    No big deal.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Wed Sep 16 14:56:59 2026
    From Newsgroup: comp.lang.lisp

    Paul Rubin <no.email@nospam.invalid> writes:

    antispam@fricas.org (Waldek Hebisch) writes:
    And normally functions do not return, simply tail-call to passed
    "continuation".

    Continuations are nontrivial precisely because of the non-tail-call
    case, where the continuation is re-used. So you can use them to
    implement coroutines, multitasking, etc. If they can't do that, they're
    not "full" continuations. I don't see how to implement full
    continuations using CL macros.

    There is some sentiment[1] in the Scheme world that mandating full continuations in Scheme was a mistake and that it would have been
    preferable to stop with "delimited" or "one-shot" continuations. Those
    are maybe closer to catch/throw than to coroutines. I don't know if
    those can be done with CL macros but it seems more plausible.

    [1] https://okmij.org/ftp/continuations/against-callcc.html

    I believe that these call/cc continuations were created far before
    threads. Being I don't use either; just wondering if they are similiar.

    thanx
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Wed Sep 16 13:42:29 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> writes:
    I believe that these call/cc continuations were created far before
    threads. Being I don't use either; just wondering if they are similiar.

    There is some conceptual overlap between continuations and OS threads,
    but the traditional implementations are totally different.
    Continuations are more general and you can simulate almost every control
    method with them, including loops, subroutines, threads, exceptions,
    etc. Their behaviour can be complicated and paradoxical. The Okmij
    post that I linked argues that Scheme would been better off with a
    simpler primitive.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.lisp on Thu Sep 17 00:12:39 2026
    From Newsgroup: comp.lang.lisp

    steve g <Sgonedes1977@gmail.com> wrote:
    Paul Rubin <no.email@nospam.invalid> writes:

    antispam@fricas.org (Waldek Hebisch) writes:
    And normally functions do not return, simply tail-call to passed
    "continuation".

    Continuations are nontrivial precisely because of the non-tail-call
    case, where the continuation is re-used. So you can use them to
    implement coroutines, multitasking, etc. If they can't do that, they're
    not "full" continuations. I don't see how to implement full
    continuations using CL macros.

    There is some sentiment[1] in the Scheme world that mandating full
    continuations in Scheme was a mistake and that it would have been
    preferable to stop with "delimited" or "one-shot" continuations. Those
    are maybe closer to catch/throw than to coroutines. I don't know if
    those can be done with CL macros but it seems more plausible.

    [1] https://okmij.org/ftp/continuations/against-callcc.html

    I believe that these call/cc continuations were created far before
    threads. Being I don't use either; just wondering if they are similiar.

    OS360 had tasks. And a single program could have multiple tasks,
    which is mutithreading, just adapted to OS360 conventions. I think
    that continuations came later than that.
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Sep 17 19:36:41 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 16 Sep 2026 14:56:59 -0400, steve g <Sgonedes1977@gmail.com>
    wrote:

    Paul Rubin <no.email@nospam.invalid> writes:

    antispam@fricas.org (Waldek Hebisch) writes:
    And normally functions do not return, simply tail-call to passed
    "continuation".

    Continuations are nontrivial precisely because of the non-tail-call
    case, where the continuation is re-used. So you can use them to
    implement coroutines, multitasking, etc. If they can't do that, they're
    not "full" continuations. I don't see how to implement full
    continuations using CL macros.

    There is some sentiment[1] in the Scheme world that mandating full
    continuations in Scheme was a mistake and that it would have been
    preferable to stop with "delimited" or "one-shot" continuations. Those
    are maybe closer to catch/throw than to coroutines. I don't know if
    those can be done with CL macros but it seems more plausible.

    [1] https://okmij.org/ftp/continuations/against-callcc.html

    I believe that these call/cc continuations were created far before
    threads. Being I don't use either; just wondering if they are similiar.

    thanx

    Continuations [as in "a jump target"] pre-date threads [as in
    "scheduler entity"] - though not by much.

    As someone mentioned, OS360 had "tasks" which essentially were
    separate [scheduler] threads, in 1964.

    Continuations as we think of them today really were introduced with
    Scheme in ~1975, however they are just a more modern approach to code "threading", which was known already to assembler programmers in the
    1950s.
    https://en.wikipedia.org/wiki/Threaded_code
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Thu Sep 17 20:03:53 2026
    From Newsgroup: comp.lang.lisp

    On Wed, 16 Sep 2026 13:42:29 -0700, Paul Rubin
    <no.email@nospam.invalid> wrote:

    steve g <Sgonedes1977@gmail.com> writes:
    I believe that these call/cc continuations were created far before
    threads. Being I don't use either; just wondering if they are similiar.

    There is some conceptual overlap between continuations and OS threads,
    but the traditional implementations are totally different.
    Continuations are more general and you can simulate almost every control >method with them, including loops, subroutines, threads, exceptions,
    etc. Their behaviour can be complicated and paradoxical. The Okmij
    post that I linked argues that Scheme would been better off with a
    simpler primitive.

    Scheme's continuations are the way they are because Scheme was meant
    to support research. Scheme's creators wanted the /most/ powerful
    primitive available, and as you [Paul] noted, almost any control
    structure can be accomplished using call/cc.

    However, call/cc is not easy to understand and [ignoring upward
    "escape" uses] not easy to use correctly ... but I have trouble
    believing Scheme could have accomplished what its developers wanted
    using something else.


    I don't happen to like the scoping aspect of call/cc, I would have
    preferred something simpler - like C's setjmp/longjmp, or a more
    general version of Lisp's tagbody/go - ie. a way to save a spot to
    jump to, and a way to jump to it. Scheme's function call invocation
    syntax doesn't bother me [that is compiler magic invisible to the
    programmer].

    YMMV.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.lisp on Thu Sep 17 21:19:11 2026
    From Newsgroup: comp.lang.lisp

    George Neuner <gneuner2@comcast.net> writes:
    Continuations as we think of them today really were introduced with
    Scheme in ~1975, however they are just a more modern approach to code "threading",

    A Scheme-style continuation in full generality has to save a copy of
    the activation stack, and be able to restore it multiple times.

    What Oleg (okmij.org) wanted instead was "one-shot" or "delimited" continuations, maybe closer to ordinary stackful coroutines. They still
    have to save and restore the stack, but only once. I've never tried to understand either type very carefully though.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Sun Sep 20 07:18:43 2026
    From Newsgroup: comp.lang.lisp

    On Thu, 17 Sep 2026 21:19:11 -0700, Paul Rubin
    <no.email@nospam.invalid> wrote:

    George Neuner <gneuner2@comcast.net> writes:
    Continuations as we think of them today really were introduced with
    Scheme in ~1975, however they are just a more modern approach to code
    "threading",

    A Scheme-style continuation in full generality has to save a copy of
    the activation stack, and be able to restore it multiple times.

    That is true ... however, if the program is in CPS, its state at any
    particular time is just a single activation record [for the current
    function] - not an entire stack of them.


    What Oleg (okmij.org) wanted instead was "one-shot" or "delimited" >continuations, maybe closer to ordinary stackful coroutines. They still
    have to save and restore the stack, but only once. I've never tried to >understand either type very carefully though.

    I've never figured out what makes "delimited" continuations different
    from general continuations except that the implementation constrains
    where a "delimited" continuation may be invoked. But that seems to be
    a difference in usage rather than in kind.

    Upward "escape" continuations essentially are one-shots because,
    although there could be many instances due to reentrance or recursion,
    any particular instance of the continuation can be invoked only once.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Stefan Monnier@monnier@iro.umontreal.ca to comp.lang.lisp on Sun Sep 20 16:31:49 2026
    From Newsgroup: comp.lang.lisp

    What Oleg (okmij.org) wanted instead was "one-shot" or "delimited" >>continuations, maybe closer to ordinary stackful coroutines. They still >>have to save and restore the stack, but only once. I've never tried to >>understand either type very carefully though.

    I've never figured out what makes "delimited" continuations different
    from general continuations except that the implementation constrains
    where a "delimited" continuation may be invoked. But that seems to be
    a difference in usage rather than in kind.

    Full continuations are, conceptually, a copy of the whole stack, wrapped
    as a kind of function that never returns.
    Delimited continuations offer, conceptually, a copy of a chunk of the
    stack, wrapped as a kind of function that does return.


    === Stefan
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.lisp on Mon Sep 21 04:40:34 2026
    From Newsgroup: comp.lang.lisp

    On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier wrote:

    Full continuations are, conceptually, a copy of the whole stack,
    wrapped as a kind of function that never returns. Delimited
    continuations offer, conceptually, a copy of a chunk of the stack,
    wrapped as a kind of function that does return.

    Why do you need to copy anything, beyond some very basic context info?

    Call frames just form a tree and are allocated on the heap. So the
    fact that a frame is referenced (directly or indirectly) from a
    continuation is sufficient to keep it from being deleted.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From George Neuner@gneuner2@comcast.net to comp.lang.lisp on Tue Sep 22 05:30:30 2026
    From Newsgroup: comp.lang.lisp

    On Mon, 21 Sep 2026 04:40:34 -0000 (UTC), Lawrence D-|Oliveiro
    <ldo@nz.invalid> wrote:

    On Sun, 20 Sep 2026 16:31:49 -0400, Stefan Monnier wrote:

    Full continuations are, conceptually, a copy of the whole stack,
    wrapped as a kind of function that never returns. Delimited
    continuations offer, conceptually, a copy of a chunk of the stack,
    wrapped as a kind of function that does return.

    Why do you need to copy anything, beyond some very basic context info?

    Call frames just form a tree and are allocated on the heap. So the
    fact that a frame is referenced (directly or indirectly) from a
    continuation is sufficient to keep it from being deleted.

    Not every implementation allocates frames on the heap.

    Since most functions don't create closures or continuations, it often
    is simpler to put their call frames on the [linear] CPU stack and let
    the normal call/return sequence deal with them. This has the advantage
    of speed because the CPU stack [or at least part of it] always is in
    cache.

    However, creating closures then involves copying whatever is needed
    from the stack to a heap allocation, and rewriting code to look in the allocation instead of in the stack. This is called "closure
    conversion" in the literature.

    Continuations require similar treatment, but may need to copy the
    entire CPU stack.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From steve g@Sgonedes1977@gmail.com to comp.lang.lisp on Sun Oct 18 17:31:02 2026
    From Newsgroup: comp.lang.lisp

    tfb <tfb@work.it.out> writes:

    Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:

    The person you're talking to has deliberately added cross-posts to
    comp.lang.misc and comp.lang.c. If you must reply to this troll,
    please limit your replies to comp.lang.lisp.


    They did, didn't they. Sorry: my rather primitive newsreader makes that
    hard to see, but I should have noticed in any case. Sorry for wasting people's time (people who won't see this, but still, sorry).

    (I do have to wonder though: in the pop-psychology world, what term would
    be used for someone who adds a bunch of unrelated newsgroups in that way?)


    asshole
    --- Synchronet 3.22a-Linux NewsLink 1.2