|
From: | Stefan Seefeld |
Subject: | Re: AC_DIVERSION_INIT and autoconf 2.52 |
Date: | Wed, 23 Jan 2002 11:06:40 -0500 |
Akim Demaille wrote:
Thomas> "internals" should be used in its correct sense: describing Thomas> things that a user cannot see Sorry, I'm doing free software, and therefore there are no internals according to your definition. I prefer a useful definition. Consider it `private' if you prefer.
May be I'm missing the context here, but what has free software to do with this discussion ?
We are talking about a public interface (an 'API') as opposed to implementation. One reason to encapsulate things is to be able to change it without creating incompatibilities, i.e. without affecting the API. The failure here is that there doesn't seem to be at least a namingconvention that marks non-public macros/variables such as AC_DIVISION_INIT (AC_PRIVATE_DIVISION_INIT may be ?), which would have avoided its (mis-)use.
Now people are using it, and you just tell them to rewrite their build system in order to be able to use the new version.
That's bad practice. Regards, Stefan
[Prev in Thread] | Current Thread | [Next in Thread] |