User login

Reply to comment

Indentation?

Hmm, works for me, both indentation and lower-case symbols. Can you provide a test case and your setup?


I worry that textual refactorings might have lots of corner cases.

Yes, that's why I am not very fond of them. However, I also want to respect what the user typed. Paredit goes to some lengths to preserve as much of what the user typed as possible, and I think it's a good strategy in the presence of partial input. In fact, that's what makes it so pleasant to use, I believe.


I'm sure it's possible to do a regular-expression-like language that can recognize s-expr syntax. I'm just not aware of how to do it right off the bat.

Ugh, that does not sound right. The Eclipse approach seems better to me: incremental parsing, preserving comments and other whitespace (hence my mentioning of syntax tree earlier), inserting error nodes when something cannot be parsed to synchronize the parser. The matcher then works on the "DOM", with the matching ignoring whitespace and the transformations doing something intelligent with it.

Reply

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.