|
From: | martin rudalics |
Subject: | Re: Musings: Supposed places of safety, guaranteed by parse-partial-sexp are not safe. |
Date: | Sun, 04 Dec 2011 11:41:20 +0100 |
User-agent: | Thunderbird 2.0.0.21 (Windows/20090302) |
> The better way to fix it is probably to change the (nth 5 ppss) value so > it holds something like "buffer position actually described by PPSS in > case the requested buffer position is in the middle of a lexeme" and > so it can be used for both backslashes and multi-char comment markers. If you change (nth 5 ppss) you would still have to say that (nth 4 ppss) is unreliable in this special case. I think Daniel is right here: Check whether the character following TO completes a comment begin (or comment end) lexeme and in that case return consistently the in-comment value. martin
[Prev in Thread] | Current Thread | [Next in Thread] |