On Fri, May 30, 2003 at 01:54:21PM -0400, MATHIHALLI,MADHUSUDAN
(HP-Cupertino,ex1) wrote:
...
> Now, what should be the behaviour under the following scenarios :
>
> - everything is fine : program runs fine. No problems.
> - Unresolved symbols and stderr is open : program will report the
> unre
> From: Jeff Trawick [mailto:[EMAIL PROTECTED]
> 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 th
On Fri, May 30, 2003 at 09:23:11PM +0200, Sascha Schumann wrote:
> Hi there,
>
> the sed on IRIX does not cooperate with the complex sed
> expressions used to cut out and transform the proper layout
> section. Thus configure has been failing since 2.0.40 or
> so on IRIX.
>
>
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
> From: MATHIHALLI,MADHUSUDAN (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 04, 2003 8:56 PM
> >-Original Message-
> >From: Jeff Trawick [mailto:[EMAIL PROTECTED]
> [SNIP]
>
> >> So, what you're proposing is that APR provide mechanisms for
> >people to write
> >> p
>-Original Message-
>From: Jeff Trawick [mailto:[EMAIL PROTECTED]
[SNIP]
>> So, what you're proposing is that APR provide mechanisms for
>people to write
>> platform-specific code?
>
>APR already does that.
Exactly. There is already platform-specific code in APR (and I think it's
impossi
[EMAIL PROTECTED] wrote:
So, what you're proposing is that APR provide mechanisms for people to write
platform-specific code?
APR already does that.
> That's in direct conflict with our mission to provice
"predictable if not identical" behaviour across platforms.
In conflict with or orthogonal to?
At 02:23 PM 6/4/2003, [EMAIL PROTECTED] wrote:
Quoting Jeff Trawick <[EMAIL PROTECTED]>:
> Another factor is that not every portability issue affecting
> applications that use APR is going to be adopted by APR as a
problem
> that it can or should solve. Some issues will always pop up for
certain
Quoting Jeff Trawick <[EMAIL PROTECTED]>:
> Branko �ibej wrote:
>
> > Imagine the mess if all APR users started to use APR_PLATFORM_IS_HPUX to
> > decide the .so vs. .sl thing... this is exactly what APR is meant to avoid.
>
> Another factor is that not every portability issue affecting
> appl
see http://www.apache.org/~trawick/PR20295/pipes_are_not_atomic.patch
and http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20295
apr_file_write() and its callers are not properly dealing with the
atomic nature of some pipe write operations on Unix-ish systems. I
suggest that it is reasonable to
William A. Rowe, Jr. wrote:
#define APR_DSO_DEFAULT_EXT ".so"
#define APR_DSO_DEFAULT_EXT ".sl"
#define APR_DSO_DEFAULT_EXT ".dll"
#define APR_DSO_DEFAULT_EXT ".dylib"
is the sort of thing we should be supporting. No need for in-depth-knowledge
here.
I don't see anybody claiming that the right sol
At 05:20 PM 6/3/2003, Branko Čibej wrote:
>Jeff Trawick wrote:
>
>> Joe Orton wrote:
>>
>>> On Thu, May 29, 2003 at 07:38:29AM -0400, Jeff Trawick wrote:
>>>
[EMAIL PROTECTED] wrote:
> trawick 2003/05/28 11:24:13
>
> Modified:test testdso.c
> Log:
> get tes
12 matches
Mail list logo