Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: "Alexandre Oliva" <oliva AT lsd DOT ic DOT unicamp DOT br>,
        <cygwin-apps AT sources DOT redhat DOT com>, <autoconf AT gnu DOT org>
Subject: Re: updated win32 macro
References: <035401c0ac91$3ba21fd0$0200a8c0 AT lifelesswks>
	<022001c0accf$29b724d0$0200a8c0 AT lifelesswks>
	<orelvz60mr DOT fsf AT guarana DOT lsd DOT ic DOT unicamp DOT br>
	<007f01c0ad2e$f3dc5d20$0200a8c0 AT lifelesswks>
	<00a301c0ad32$57ad0220$0200a8c0 AT lifelesswks>
	<mv4elvz5pma DOT fsf AT nostromo DOT lrde DOT epita DOT fr>
	<00c801c0ad36$01ec3370$0200a8c0 AT lifelesswks>
	<mv466hb5ohw DOT fsf AT nostromo DOT lrde DOT epita DOT fr>
	<011a01c0ad41$c0fbc9a0$0200a8c0 AT lifelesswks>
From: Akim Demaille <akim AT epita DOT fr>
Date: 15 Mar 2001 13:28:02 +0100
In-Reply-To: <011a01c0ad41$c0fbc9a0$0200a8c0@lifelesswks>
Message-ID: <mv4snkf43ot.fsf@nostromo.lrde.epita.fr>
Lines: 29
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


| Yes. Well the namespace pollution is already solved - that was my
| ignorance. I think the best bet is the high/low level interface.
| 
| the questions are then:
| 
| one low level interface for each language? (I think yes)

Yep, the current one.

| one high level interface for each language (I think no)

Correct.  Anyway Autoconf is dead broken when it comes to try to
isolate features of these or those libraries/headers used by this or
that compiler: there is a single namespace for HAVE_FOO_H etc.

| What does the high level interface do ? (I suggest it sets the variables
| named above, setting them to " " as a minimum if WIN32 is found, and
| nothing if it is not. 

What's the point?  Just define a user var to the proper flags if
needed, and set the current compiler to use it.

| What does the low level interface do? For each language it finds a win32
| set of switchs and puts them in the appropriate variable. It could have
| a [if true, if false] layout if needed, but I don't really see the need.

If there is no need, just don't.  Low level macro just compute some
$WIN32FLAGS for the current language.