-
For $work I just started working on the meaty part of a re-implementation of an airline flight schedule combiner in Go. This thing has to handle messages in ancient and ill-specified protocols, so…fun. For Open Dylan I’m on my second round of trying to add multi-line strings to the compiler, after refactoring the lexer a bit to enable some testing. I normally don’t hack the compiler so this is a bit different for me. Planning to use Python-like triple-double-quote syntax.
-
-
Good point about editor support. It seems like there should be some general support for it out there due to Python though.
Other alternatives I thought about are #s and #r since Dylan has #t, #f, and #“symbol” syntax already. That is, #s"…“ and #s'…‘ for strings with interpreted escape characters like \n and #r”…“ and #r’…‘ for "raw” strings with no interpretation. The latter is particularly useful for regular expressions.
The bottom line, I think, is that if you want to put a big blob of text in a constant there’s a good chance it has both a double-quote and a single-quote in it somewhere, and that’s why “ ” “ is nice.
There’s some discussion here… https://lists.opendylan.org/pipermail/hackers/2013-February/006709.html
-
-
This would make a nice addition to the Dylan documentation as a quick overview for people new to the language. Thanks for writing it!
Oddly, none of the reviewers pointed out that I missed
subclasstypes! I guess I’ll have to find enough interesting material about that to make a blog post …