all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>, joakim@verona.se
Cc: emacs-devel@gnu.org
Subject: Re: Refactoring in Emacs (was: Note on 109327)
Date: Tue, 31 Jul 2012 21:06:33 +0300	[thread overview]
Message-ID: <83pq7berfa.fsf@gnu.org> (raw)
In-Reply-To: <50181914.4030503@yandex.ru>

> Date: Tue, 31 Jul 2012 21:42:44 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
> 
> > Btw, can't we have in Emacs a feature that would allow such
> > refactoring?  The replacements don't seem too complex to me.  Adding
> > this to Emacs will both allow getting rid of an external tool, and be
> > a valuable addition to Emacs abilities.  WDYT?
> 
> 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.

> so, I'm thinking about GCC plugin.

Why do we need a GCC plugin?  What kind of information is needed from
the compiler?

> Nevertheless, I suppose that it should be possible to build
> simple refactoring engine on top of cc-mode, and such an engine
> may provide basic features like intelligent renaming of identifiers
> or tweaking function arguments.

That would be very good, I think.

> From: joakim@verona.se
> Date: Tue, 31 Jul 2012 19:35:35 +0200
> Cc: Juanma Barranquero <lekktu@gmail.com>, dmantipov@yandex.ru,
> 	emacs-devel@gnu.org
> 
> http://cedet.sourceforge.net/srecode.shtml
> 
> The idea is that the two CEDET tools, Semantic and SRecode can cooperate
> to provide such features, I think.

Emacs has some of both; is what we have not enough?



  reply	other threads:[~2012-07-31 18:06 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       ` Eli Zaretskii [this message]
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
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=83pq7berfa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmantipov@yandex.ru \
    --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.