Re: rename and clean unexec.c

[Dan Nicolaescu <dann@gnu.org>]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Dan Nicolaescu <dann@gnu.org>
>> Date: Wed, 28 Jul 2010 18:55:45 -0400
>> Cc: Óscar Fuentes <ofv@wanadoo.es>, emacs-devel@gnu.org
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> >> From: Óscar Fuentes <ofv@wanadoo.es>
>> >> Date: Wed, 28 Jul 2010 22:13:16 +0200
>> >> 
>> >> Speaking as someone who is getting familiar with the code base, it is
>> >> useful to see a hint on the name about its platform-specific nature.
>> >
>> > unexec.c is not DOS-specific.  It is for any platform that uses COFF.
>> > It just so happens that MSDOS is the only one that still does.
>> 
>> Then let's call it unexcoff.c then so that it follows some kind of
>> rule like all the other unexec files.  It's not very logical to refuse
>> to change the least used one.
>
> Why is it so important to rename this file?  I'm not against renaming

For long term maintainability.
Good, suggestive file names are good for maintainability.

When we have a rule and a single file does not follow it, it not good.
We finally have the right support for renaming so there's not reason
to keep a very old name that's not accurate anymore and it's the wrong
place to look for the "unexec" function for close to (100% -1person)
of the developers.