[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Motivation for renaming to and its effect?

From: Ralf Corsepius
Subject: Re: Motivation for renaming to and its effect?
Date: Mon, 08 Mar 2010 18:10:59 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100301 Fedora/3.0.3-1.fc12 Thunderbird/3.0.3

On 03/08/2010 05:55 PM, Peter Breitenlohner wrote:
On Mon, 8 Mar 2010, Steffen Dettmer wrote:

I'm trying to understand the motivation for renaming
to If I remember correctly it was related to the
fact that ./config.status or whoever else processes .in files.

IMHO, the only real reason to rename to is, that
some future Autoconf version may cease to accept the 'bugward' compatible
old name.
Only partially.

Suffix rules/mime-types are the keywords you are looking for. Whether the files are named *.ac or *.in doesn't make much of a difference to autoconf, but to other tools, e.g. automake, GUIs, browsers, editors etc.

Everything else is philosophy/ideology.
Well, I presume your C-sources are named *.jpg?


PS.: Yes, I strongly think it's time for autoconf to bury It's an anachronism worth to ditch, ASAP.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]