Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
From: "Sander Striker" <striker@apache.org>
To: <trawick@attglobal.net>, <dev@apr.apache.org>
Subject: RE: cvs commit: apr/test testdso.c
Date: Wed, 4 Jun 2003 23:30:10 +0200
Message-ID: <JLEGKKNELMHCJPNMOKHOIEKDKBAA.striker@apache.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3EDE5117.6080805@attglobal.net>

> From: Jeff Trawick [mailto:trawick@attglobal.net]
> Sent: Wednesday, June 04, 2003 10:06 PM

> Sander Striker wrote:
> 
>> It's about giving the user (an app developer) a tool you may not wish to
>> hand him.  This either forces him to write platform independend code, or,
>> makes him need to go to the ugly process of writing platform tests himself.
> 
> I see an implication that if APR doesn't give the user a tool s/he will 
> be forced/encouraged/challenged to write platform independent code, and 
> that otherwise it would be a mess.
> 
> Is my understanding of your point accurate?  IOW, do you believe that 
> for APR to provide a cleaner representation of such platform-specific 
> details will cause APR applications to be messier?

Yes, that is a fair understanding.  I like your 'encouraged' better than
my 'forced', because it matches my thoughts.

If people really need to know what platform they are compiling on, while
using APR, I think we haven't accomplished our goals with APR.  Feature
checks are one thing, platform checks are another.  IMHO, ofcourse.

Sander