News for hackers. Stuff that matters.
Re:Lisp Machine Manual (1984) by AnimalMuppet on Thursday September 07, 2017 @10:18PM (#15197433)
Hold on there, cowboy. You're still assuming the worst about me, with no evidence, and that gets annoying by the second or third time.

> You do not understand the difference between what the program code does and what the programming language implementation does

False.

> I am going to assume you need a stdlib.h refresher

False, and even if I did, that wasn't much of one.

> How do you think free works?

I've seen an implementation.

> How would you write a linked list implementation in C?

I've had the pleasure (?) of doing so.

On to the meat of your reply: I was not aware of any non-garbage-collected Lisps. Still, isn't it fair to say that such Lisps are by far the exception?

I was under the impression that immutable was the normal way to write Lisp. ("Normal" here not meaning "the one right way" or "the way the language tries to make you write" - Lisp doesn't do that - but more "the way the majority of people write it".)

And even if you're going to not write it that way, if you really want to avoid allocations, don't you have to also be careful what library functions you call, since many of them cons?

Re:Lisp Machine Manual (1984) by sedachv on Friday September 08, 2017 @04:15AM (#15198668)
> Hold on there, cowboy. You're still assuming the worst about me, with no evidence, and that gets annoying by the second or third time.

The evidence is that you insist on posting a bunch of "I was under the impression" bullshit instead of spending a few minutes using a search engine. That is what is really annoying. Why do you think that your basic thesis that programs written under the assumption that there is garbage collection will not work well when there is no garbage collection is a novel or insightful contribution to the discussion about the original post?