Talk:BBN LISP

From Computer History Wiki
Jump to: navigation, search

Dialects versus Implementations

I'm a little lost differentiating between 'dialects' and 'implementations'. At one end of the spectrum, if a language has a clear specification, and two implementations (compilers) implement that specification exactly, then clearly they aren't 'dialects', just 'implementations'. At the other end, with things like BASIC and LISP, different implementations might implement dialects with significant differences.

In some places, like Maxc Byte Lisp, I put it in Category: Language Implementations; INTERLISP got put in both that and Category: LISP Dialects, since it has aspects of both. (I see you moved BBN LISP from one to the other - maybe putting it in both would have been more appropriate?) But it's so difficult to decide between those two, in some places. So I don't know how to handle that situation.

Maybe the thing to do is give up on Category: Language Implementations, and just have 'Dialect' categories? But then there are Category: C Compilers, etc. For languages which don't really have dialects with large differences, maybe that kind of category name is appropriate?

I think the first step is to get definite names for bottom-level categories (because to change the names of those categories, one has to edit all the articles which are in them). Having done that, the category structure above that is easier to adjust. Jnc (talk) 22:09, 20 June 2023 (CEST)

Yes, I was also considering this after I changed BBN LISP, and then I started getting second thoughts. In that particular case, there are three different implementations. But are they a cohesive dialect? I'm not sure; probably to some extent. Similarly, INTERLISP could refer to what was retronymed Interlisp-10, or to the family/dialect as a whole. Somehow Lisp in particular has a very chequered past with regards to implementations, dialects, families, compilers, interpreters, etc, so it's probably one of the hardest to neatly categorize.
ByteLisp is an instruction set that was a target for the INTERLISP compiler. Larsbrinkhoff (talk) 07:08, 21 June 2023 (CEST)
Yes, LISP is one of the worst; up there with BASIC.
ByteLisp is pretty clearly an implementation of the INTERLISP dialect.
I'm not at all sure what do do about this whole implementation/dialect mess. I think I'm going to let it simmer in my mind for a few days. Jnc (talk) 10:26, 21 June 2023 (CEST)