From: Dmitry Antipov <dmantipov@yandex.ru>
To: emacs-devel@gnu.org
Cc: Andy Moreton <andrewjmoreton@gmail.com>
Subject: Re: refactoring DEFUN
Date: Mon, 25 Mar 2013 17:48:41 +0400 [thread overview]
Message-ID: <515055B9.4070103@yandex.ru> (raw)
In-Reply-To: <vz1li9bk59w.fsf@gmail.com>
On 03/25/2013 04:55 PM, Andy Moreton wrote:
> It would help to show the elisp program you used to generate the patch,
> as that would make it easier to check that the results of the transform
> are correct.
This is just about mastering the monster regexp:
(defun defun-replace ()
(set-buffer (find-file-noselect (car (last command-line-args))))
(while (re-search-forward
"DEFUN \(\\(\".+\"\\),[ \n\t]+F\\(\[A-Za-z0-9_\]+\\),[ \n\t]+S\\(\[A-Za-z0-9_\]+\\),[ \n\t]+\\([^,]+, [^,]+, [^,]+,\\)" nil t)
(replace-match "DEFUN \(\\1, \\3, \\4"))
(save-buffer))
And then do it in batch mode:
for f in src/*.[cm]; do emacs -Q -batch -l ../misc/defun-replace.el -f defun-replace $f; done
The regexp above can't handle complex interactive specs like in Frename_buffer.
However defun-replace doesn't change such a functions at all, so the whole
procedure yields to a few compilation errors which may be fixed manually.
Finally, too long lines may be found with something like:
grep -nH DEFUN *.[cm] | awk 'length > 70'
and fixed manually too.
The whole change passes full bootstrap and basic editing tests.
> Did you find any cases where the names did not match up ?
I believe that I've fixed the last mismatch in r112124 :-).
Dmitry
next prev parent reply other threads:[~2013-03-25 13:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 11:56 [RFC] refactoring DEFUN Dmitry Antipov
2013-03-25 12:19 ` Eli Zaretskii
2013-03-25 12:38 ` Eli Zaretskii
2013-03-25 12:56 ` Andy Moreton
2013-03-25 12:55 ` Andy Moreton
2013-03-25 13:48 ` Dmitry Antipov [this message]
2013-03-25 13:18 ` [RFC] " Daniel Colascione
2013-03-25 14:02 ` Dmitry Antipov
2013-03-25 13:54 ` Alan Mackenzie
2013-03-25 14:34 ` 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=515055B9.4070103@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@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.
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.