Hmm. Indentation - i.e. newline as a default escape, then using spacing after newline as a sort of counter-escape - is a possibility I hadn't considered. It seems a little awkward in context of a bytecode, but I won't dismiss it out of hand. I'd need to change my open-quote character, of course. I'll give this some thought. Thanks.
On Tue, Sep 24, 2013 at 4:19 PM, Loup Vaillant-David <[email protected]>wrote: > One way of escaping is indentation, like Markdown. > > This is arbitrary code > This is arbitrary code *in* arbitrary code. > and so on. > > No more escape sequences in the quotation. You just have the > inconvenience of prefixing each line with a tab or something. > > Loup. > > > On Mon, Sep 23, 2013 at 10:24:20PM -0700, David Barbour wrote: > > Text is also one of the problems I've been banging my head against since > > Friday. Thing is, I really hate escapes. They have this nasty geometric > > progression when dealing with deeply quoted code: > > > > {} -> {{\}} -> {{{\\\}\}} -> {{{{\\\\\\\}\\\}\}} -> > > {{{{{\\\\\\\\\\\\\\\}\\\\\\\}\\\}\}} > > > > I feel escapes are too easy to handle incorrectly, and too difficult to > > inspect for correctness. I'm currently contemplating a potential > solution: > > require all literal text to use balanced `{` and `}` characters, and use > > post-processing in ABC to introduce any imbalance. This could be > performed > > in a streaming manner. Inductively, all quoted code would be balanced. > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc >
_______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
