You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Published in 1992, all the examples with setf result in errors because an undefined variable is being "set." The language is now so appalling and ornate that the only thing that works is (defparameter x 10). The committees have taken over and made the language a bastion of hideous rules that enshrine the committee members' esoteric knowledge.
The text was updated successfully, but these errors were encountered:
sbcl
From: homedirectory ***@***.***>
Reply-To: norvig/paip-lisp ***@***.***>
Date: Saturday, August 5, 2023 at 1:28 PM
To: norvig/paip-lisp ***@***.***>
Cc: Lewis Levin ***@***.***>, Author ***@***.***>
Subject: Re: [norvig/paip-lisp] so old.... (Issue #187)
Which implementation are you using? I'm using GNU CLISP and, having worked through the first 8 chapters, almost everything has been smooth so far.
—
Reply to this email directly, view it on GitHub<#187 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIYWLMXFOM5YTIBX4URJJ3XTZ7D7ANCNFSM6AAAAAAZHGZGD4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
Published in 1992, all the examples with setf result in errors because an undefined variable is being "set." The language is now so appalling and ornate that the only thing that works is (defparameter x 10). The committees have taken over and made the language a bastion of hideous rules that enshrine the committee members' esoteric knowledge.
The text was updated successfully, but these errors were encountered: