Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by antonvs on Sunday March 17, 2024 @11:23PM
(#39740263)
> there was ferment in the Lisp community.
This is the same as saying "the Lisp community existed."
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by lisper on Sunday March 17, 2024 @11:42PM
(#39740333)
No, it is saying that the community was coming up with a lot of remarkably good ideas.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by jksmith on Monday March 18, 2024 @12:07AM
(#39740439)
An elegant weapon for a more civilized age without the C language legacy.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by fargle on Monday March 18, 2024 @12:45AM
(#39740595)
that's like saying the 18th century was more "civilized" because we settled squabbles with dueling pistols. people are still people and we are just about as civilized today as we ever were. which isn't saying much.
the analogy holds for programming languages as well as it does for anything else involving people.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by jksmith on Monday March 18, 2024 @03:07AM
(#39741110)
Just a fanciful quote with some license. But one might argue the defn of civilization as applied to general programming with so much of it being commodity programming these days. Additionally, I believe an argument could be made that the long-term tyranny of the C bubble has actually retarded the advancement of the art.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by MonkeyClub on Monday March 18, 2024 @05:36PM
(#39750348)
I think GP missed the reference, https://xkcd.com/297
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by fargle on Tuesday March 19, 2024 @09:55PM
(#39762230)
indeed. thank you.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by antonvs on Thursday March 21, 2024 @10:59PM
(#39787047)
The point is that the Lisp community was always in some sort of ferment. The number of Lisps that were developed alone is testament to that.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by digdugdirk on Monday March 18, 2024 @12:46AM
(#39740602)
That sounds really interesting, in a way I cannot begin to comprehend.
Can someone please translate into more common vernacular?
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by volemo on Monday March 18, 2024 @02:13AM
(#39740874)
> Can someone please translate into more common vernacular?
If I were to read that, it’d be common lisp. :D
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by JimmyRuska on Monday March 18, 2024 @01:47AM
(#39740796)
Sounds like an implementation for how to managing scopes using stack frames with some state machine like elements to it
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by rurban on Monday March 18, 2024 @05:45AM
(#39741948)
setjmp/longjmp if the states were not on the stack. (of course nobody would be so crazy to actually use longjmp, just properly save the stack state: env and control)
if jumping back into inner states (i.e. out of control stacks), the stack frame needs to be preserved also. as in call/cc later.
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by ustad on Monday March 18, 2024 @02:39AM
(#39740985)
Could not find the actual paper but the figures look cool:
https://www.semanticscholar.org/paper/A-model-and-stack-impl...
Re:IBM Research: Experience with an Uncommon Lisp (1986) [pdf]
by mainland on Monday March 18, 2024 @10:54AM
(#39745412)
Here is a copy of what looks to be the original report: <https://wellcomecollection.org/works/seuuc6a5>
Here is a link to the version published with the ACM: <https://dl.acm.org/doi/10.1145/362375.362379>
A key component of this model of computation was the con- cept of the saved state, a data object which captured both the set of current variable bindings (the environment) and the current call chain and point of execution (the control). We have used saved states (state descriptors) extensively, both as a form of continuation and as a component of closures.