From: Davis Herring <herring@lanl.gov>
To: Le Wang <l26wang@gmail.com>
Cc: Bric <bric@flight.us>, emacs-devel@gnu.org
Subject: Re: awesome feature (yet to be added?)
Date: Mon, 05 May 2014 20:45:10 -0600 [thread overview]
Message-ID: <53684CB6.1050601@lanl.gov> (raw)
In-Reply-To: <CAM=K+iqYUrhYYAjjFpNeQBCyadd9V6nH7ELoEVNoO5yCrak=bA@mail.gmail.com>
> Judging by the uptake. We are the only two to think this is useful. :)
I thought about implementing `invert-comment' a few years ago, but I
wasn't sure what to do about code like this:
/* old_implementation_prepare (); */
/* old_implementation_go (); */
new_implementation_prepare ();
/* The new implementation needs a buffer allocated. */
char *p = malloc (new_implementation_size ());
new_implementation_go (p);
What to do about the actual comment embedded in the "new" code?
x = foo () + /* bar () + */ baz ();
quux (x, x + 1); /* quux now accounts for bar internally */
What does it mean to toggle commented-ness here?
Your idea of markers likely works out better than "toggle the comments"
because of cases like these.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2014-05-06 2:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 18:47 awesome feature (yet to be added?) Bric
2014-05-04 1:23 ` Bric
2014-05-04 11:12 ` Stephen Berman
2014-05-04 18:33 ` Andreas Röhler
2014-05-06 2:32 ` Le Wang
2014-05-06 2:45 ` Davis Herring [this message]
2014-05-06 8:19 ` Stephen J. Turnbull
2014-05-06 22:27 ` Robert Thorpe
2014-05-30 21:35 ` Thorsten Jolitz
2014-05-31 1:30 ` Stefan Monnier
2014-05-31 10:46 ` Thorsten Jolitz
2014-06-09 11:01 ` Thorsten Jolitz
2014-06-09 15:30 ` Stefan Monnier
2014-05-31 6:26 ` Andreas Röhler
2014-05-31 10:52 ` Thorsten Jolitz
2014-05-31 17:20 ` Andreas Röhler
2014-05-31 20:04 ` Thorsten Jolitz
2014-06-01 7:00 ` Andreas Röhler
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=53684CB6.1050601@lanl.gov \
--to=herring@lanl.gov \
--cc=bric@flight.us \
--cc=emacs-devel@gnu.org \
--cc=l26wang@gmail.com \
/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.