From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>
Cc: Stefan Monnier <monnier@IRO.UMontreal.CA>, emacs-devel@gnu.org
Subject: Re: Musings: Supposed places of safety, guaranteed by parse-partial-sexp are not safe.
Date: Tue, 06 Dec 2011 11:15:22 +0100 [thread overview]
Message-ID: <4EDDEB3A.8020509@gmx.at> (raw)
In-Reply-To: <20111205112549.GA3522@acm.acm>
> The parse-partial scanner works strictly left to right. If (nth 5 ppss)
> records the left hand bit of "/*", we are not yet in a comment. We're
> probably about to do a division. Similarly, after * of "*/", we're still
> in the comment, probably just passed a comment prefix.
If we can look ahead by one character, there is no probability but
certainty. And the latter is what you want in (nth 4 ppss). The
remaining case is with an "/" at the end of a buffer and that case
wouldn't trouble me.
> I disagree. I think keeping the stricly L to R invariant of the parse is
> critically important (but don't ask me why :-).
Why would looking ahead violate a L to R rule?
martin
next prev parent reply other threads:[~2011-12-06 10:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 23:23 Musings: Supposed places of safety, guaranteed by parse-partial-sexp are not safe Alan Mackenzie
2011-12-03 23:40 ` Daniel Colascione
2011-12-04 3:39 ` Stefan Monnier
2011-12-04 10:41 ` martin rudalics
2011-12-04 15:21 ` Stefan Monnier
2011-12-04 17:06 ` martin rudalics
2011-12-04 20:47 ` Andreas Röhler
2011-12-05 3:33 ` Stefan Monnier
2011-12-05 7:41 ` martin rudalics
2011-12-05 14:01 ` Stefan Monnier
2011-12-05 11:35 ` Alan Mackenzie
2011-12-05 11:25 ` Alan Mackenzie
2011-12-06 10:15 ` martin rudalics [this message]
2011-12-06 10:33 ` Alan Mackenzie
2011-12-06 13:39 ` martin rudalics
2011-12-06 13:50 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EDDEB3A.8020509@gmx.at \
--to=rudalics@gmx.at \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).