4 ms·
Apparently the actual surface syntax is not yet decided and the S-expression abstract syntax is currently used as a stand-in.
by lifthrasiir 3y ago
Apparently the actual surface syntax is not yet decided and the S-expression abstract syntax is currently used as a stand-in.
- muth02446 3y agoThat is correct. The concrete syntax will be python-like. Somer examples are here: https://github.com/robertmuth/Cwerg/tree/master/FrontEnd/ConcteteSyntax https://github.com/robertmuth/Cwerg/tree/master/FrontEnd/Con...
- alwaysbeconsing 3y agoPrecedent for Python-like but C-level language in Nim; will be interested to see how yours develops too. Good luck!
- kouteiheika 3y agoIIRC, wasn't this originally also the case for Lisp?
- eigenhombre 3y agoI wonder how hard it would be to keep the S-expression syntax when the new one is implemented. As a C and Lisp programmer I'm intrigued by the possibilities - C-family syntax being IMO more readable, but Lisp providing unparalleled (in my experience) metaprogramming possibilities.
- lelanthran 3y agoI'm also a Lisp and C programmer (want to get better at Forth too). I think Lisp and C (not C++) share an important characteristic that few other languages share: being low-level. C is low-level due to minimal abstractions from the hardware. Lisp is low-level due to minimal abstractions from the AST. People wanting to program very close to hardware feel comfortable with C. People wanting to program very close to the compiler feel comfortable with Lisp.
- muth02446 3y agoI am planning to make the s-expr form the on disk format.
- user2342 3y agoAh, now I see. Thx.
- qwerty456127 3y agoI see. And this led me to a question: what can make a language expressed in S-expressions not a lisp?
- wrs 3y agoAny language can be expressed in S-expressions. A translation of the syntax tree to sexprs is often used in parser debugging. And Lisp doesn’t have to be expressed in S-expressions (see Dylan, or M-expressions, a syntax for Lisp that predates S-expressions). Lisp traditionally has these features, but they’re separate features: * There is a rich syntax for literal data structures * Code is directly exposed as data structures so it can be manipulated with code (macros) * Code is written as literal data structures so it has no separate syntax
- qwerty456127 3y agoThanks. Can you please elaborate some bits on what is meant under "rich syntax for literal data structures"? I'm not a lisp pro, just started studying it.
- lispm 3y agoThat's nothing special of Lisp. Literal data structures means that one can write down data objects like list, arrays, vectors, numbers (floats, integers, rational, complex, ...), symbols, strings, characters, records/structures, ... Common Lisp for example: (berlin hamburg munich cologne) ; a list of symbols #(berlin hamburg munich cologne) ; a vector of symbols (1.3 1.3d6 13 #c(1 3) 1/3) ; a list of numbers "Hello World!" ; a string #\H ; the character H #S(CITY :NAME BERLIN ; a structure (aka record) of type CITY :COUNTRY GERMANY) #*1010101111 ; a bitvector #2A((BERLIN GERMANY) ; a 2d array (PARIS FRANCE)) Other programming languages have their own syntax for literal data (even data structures like unicode characters, hash tables, unicode strings, decimal numbers, ...) Common Lisp OTOH has an extensible reader, one can add new syntax extensions for data structures, using so-called reader macros. READ is the function to read s-expressions from text streams. It returns data objects.