News for hackers. Stuff that matters.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @07:24PM (#33578667)
> expressive function names

Yes, but those are effectively library conventions, not fixed properties of the language. Maybe more importantly, names aren’t a structural construct, like a for loop or a class definition. And, arguably, you can have similar syntax in other languages, like e.g. `!` in Rust or the type sigils ($, @) in Perl, except that here you can be sure of their semantics.

Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by bmitc on Saturday November 12, 2022 @08:53PM (#33579158)
The naming is enabled by the way S-expressions work and aren't merely convention. Handling such syntax in non-parenthetic languages is difficult because of the overlap with the other meaning of those infix operators in the language. For example, in F#, if I have a function named `string->number`, then the parser doesn't know if I mean `(string) - (>number)`, `(string-) > (number)`, `(string) -> (number)`, or the function `string->number`.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by layer8 on Saturday November 12, 2022 @09:16PM (#33579282)
I totally understand. What I meant was that the meaning of such names, or the names chosen for a given meaning, is a convention of the library (or set of libraries) that defines the names, and not a semantics the language guarantees, like keywords and punctuation do in other languages. (In Lisp I don't know what `string->number` does any more than I know what `stringToNumber` does.) So S-expressions give you more freedom in the syntax of your function names, but they don't provide more kinds of constructs in the language.