From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Musings: Supposed places of safety, guaranteed by parse-partial-sexp are not safe.
Date: Sun, 04 Dec 2011 18:06:16 +0100 [thread overview]
Message-ID: <4EDBA888.2060202@gmx.at> (raw)
In-Reply-To: <jwvd3c45prx.fsf-monnier+emacs@gnu.org>
>> If you change (nth 5 ppss) you would still have to say that (nth 4 ppss)
>> is unreliable in this special case.
>
> Not if (nth 5 ppss) says that the buffer position is the one *after* the
> "/*" sequence. Of course for "*/" we'd conversely want to use the state
> *before* "*/".
What I meant was that the caller would have to care about (nth 5 ppss)
too, wherever she now looked only at (nth 3 ppss) and (nth 4 ppss). If
we say that a comment is everything in between and including both
delimiters she won't have to care about (nth 5 ppss) in the first place.
Admittedly, it's not entirely trivial to implement. But the fact that
between "/" and "*" we are not in a comment whilst between "*" and "/"
we are doesn't strike me as very intuitive.
martin
next prev parent reply other threads:[~2011-12-04 17:06 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EDBA888.2060202@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.