From: Dennis Yurichev <Dennis.Yurichev@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: C++ excessive bracketts removal
Date: Thu, 11 Oct 2007 15:00:30 -0700 [thread overview]
Message-ID: <1192140030.089916.10660@o80g2000hse.googlegroups.com> (raw)
In-Reply-To: <1192138157.259548.25800@d55g2000hsg.googlegroups.com>
On Oct 12, 12:29 am, Wojtek <wnk...@gmail.com> wrote:
> On Oct 11, 4:11 pm, Dennis Yurichev <Dennis.Yuric...@gmail.com> wrote:
>
> > Hello.
> > Is there any Emacs script which can remove excessive bracketts in all
> > expressions in some C++ source code?
> > Is there any other tools for C++ source code "cleaning"?
>
> Can you say more about what you mean by excessive? Is it that you want
> ((a && b)) to be turned into (a && b)?
Yes! With the respect to operator precedence.
prev parent reply other threads:[~2007-10-11 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 21:11 C++ excessive bracketts removal Dennis Yurichev
2007-10-11 21:29 ` Wojtek
2007-10-11 22:00 ` Dennis Yurichev [this message]
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=1192140030.089916.10660@o80g2000hse.googlegroups.com \
--to=dennis.yurichev@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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).