From: Jason Rumney <jasonr@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Antipov <dmantipov@yandex.ru>,
joakim@verona.se, emacs-devel@gnu.org
Subject: Re: Refactoring in Emacs
Date: Wed, 01 Aug 2012 22:05:23 +0800 [thread overview]
Message-ID: <87hasm6730.fsf@gnu.org> (raw)
In-Reply-To: <83pq7berfa.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 31 Jul 2012 21:06:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Tue, 31 Jul 2012 21:42:44 +0400
>> From: Dmitry Antipov <dmantipov@yandex.ru>
>>
>> IIUC real refactoring of C should imply preprocessing and full
>> syntactic analysis
>
> Why is that? Can you give a couple of examples?
>
> Even if a full-fledged refactoring engine does need that, we could
> have a somewhat limited one that doesn't, could we? AFAICS, the
> refactoring you did until now were all quite simple.
Preprocessing might even be a disadvantage, as it would mean skipping
blocks of code that are currently #ifdef'ed out because of the
configuration constants of the platform on which the refactoring is
being done.
next prev parent reply other threads:[~2012-08-01 14:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 12:38 Note on 109327 Dmitry Antipov
2012-07-31 13:13 ` Dan Nicolaescu
2012-07-31 13:25 ` Dmitry Antipov
2012-07-31 13:33 ` Tom Tromey
2012-07-31 13:50 ` Dmitry Antipov
2012-07-31 21:47 ` Thien-Thi Nguyen
2012-08-01 4:34 ` Dmitry Antipov
2012-07-31 13:54 ` Juanma Barranquero
2012-07-31 17:04 ` Eli Zaretskii
2012-07-31 17:17 ` Juanma Barranquero
2012-07-31 17:35 ` joakim
2012-07-31 17:56 ` Dmitry Antipov
2012-07-31 17:42 ` Dmitry Antipov
2012-07-31 18:06 ` Refactoring in Emacs (was: Note on 109327) Eli Zaretskii
2012-08-01 4:14 ` Refactoring in Emacs Dmitry Antipov
2012-08-01 11:41 ` Refactoring in Emacs : CEDET Eric M. Ludlam
2012-08-01 14:50 ` Eli Zaretskii
2012-08-01 23:42 ` Eric Ludlam
2012-08-01 22:41 ` Refactoring in Emacs Richard Stallman
2012-08-01 14:05 ` Jason Rumney [this message]
2012-07-31 15:16 ` Note on 109327 Jan Djärv
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=87hasm6730.fsf@gnu.org \
--to=jasonr@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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.