Unterhaltung
Nachrichten
-
Bootstrapping wisp¹ with #wisp now works²! → ¹: http://draketo.de/light/english/wisp-lisp-indentation-preprocessor ²: https://bitbucket.org/ArneBab/wisp/commits/0509e9e3418789ef307ae49b7dd862380c5c5bf8 — the magical feeling of seeing a language (dialect) grow up to live by itself: python3 wisp.py wisp-guile.w > 1 && guile 1 wisp-guile.w > 2 && guile 2 wisp-guile.w > 3 && diff 2 3 #scheme #lisp #wisp
Tuesday, 10-Sep-13 17:01:32 UTC von web-
Embrace parentheses, they are your friend. Anyway, do you plan on providing REPL support? Some lispers swear by it ;)
-
You may be a "homoiconiphobe" #humor
-
@zoowar For technical details on #wisp, the best source is actually the comparison in SRFI-110 srfi.schemers.org/srfi-110/srfi-110.html#wisp
-
I'm no expert on homoiconicity, but that there are formatting requirements in the language seems to blow it. I cant write 'display display "string"', which translates incorrectly to '(display display "string")' The output is correct if the input has a newline/space between the "display" terms.
-
@zoowar afaik homoiconity just requires that the language is written in the format you use for its data.
-
I did that with my example.
-
@zoowar and that is given, because there is an exact transformation of wisp to scheme: data and code are treated the same.
-
(display (display "string"))
-
@zoowar what would you want your example to be in scheme/lisp?
-
You might have to pretend that "display" returns a string value, since I don't use scheme these days and forgot it has side effects :(
-
@zoowar that would be either 'display : display "string"' or 'display \n display "string"' — the opening paren is just spelled as '\n ' ☺
-