Re: UUID logic required in APR?

2002-04-16 Thread Greg Stein
On Sat, Apr 13, 2002 at 05:43:09PM -0700, Justin Erenkrantz wrote: On Sat, Apr 13, 2002 at 12:36:09PM -0500, William A. Rowe, Jr. wrote: At 03:11 AM 4/13/2002, you wrote: From: Justin Erenkrantz [mailto:[EMAIL PROTECTED] Sent: 13 April 2002 08:52 Do we really have to have the

[patch apr_file_io.h] apr_file_mktemp declaration

2002-04-16 Thread Stas Bekman
match the declaration in the .c and the doc, which is template. Index: srclib/apr/include/apr_file_io.h === RCS file: /home/cvspublic/apr/include/apr_file_io.h,v retrieving revision 1.120 diff -u -r1.120 apr_file_io.h ---

Re: NSLinkEditErrorHandlers....

2002-04-16 Thread Pier Fumagalli
Kevin Pilch-Bisson [EMAIL PROTECTED] wrote: On Sat, Apr 13, 2002 at 09:07:46AM -0700, Justin Erenkrantz wrote: On Sat, Apr 13, 2002 at 05:03:11PM +0100, Pier Fumagalli wrote: On Darwin, if there's a link error (in APR-dso, if something goes wrong), the program will exit without giving a

Re: UUID logic required in APR?

2002-04-16 Thread William A. Rowe, Jr.
At 10:27 AM 4/16/2002, Karl Fogel wrote: Greg Stein [EMAIL PROTECTED] writes: The Windows UUIDs are a helluva better than ours in terms of uniqueness. We compensate, but Windows does a much better job. Or if we find that really unclean, then abstract one key portion of the uuid code and keep it

Re: cvs commit: apr/include apr_errno.h

2002-04-16 Thread William A. Rowe, Jr.
At 09:32 AM 4/16/2002, you wrote: brane 02/04/16 07:32:03 Modified:include apr_errno.h Log: On Windows, ERROR_PATH_NOT_FOUND is an ENOENT, not an ENOTDIR -- same as OS/2. I'm somewhat dubious of this change. Can you please point to the use case (a specific scenario) that this

Re: cvs commit: apr/include apr_errno.h

2002-04-16 Thread Branko ibej
William A. Rowe, Jr. wrote: At 09:32 AM 4/16/2002, you wrote: brane 02/04/16 07:32:03 Modified:include apr_errno.h Log: On Windows, ERROR_PATH_NOT_FOUND is an ENOENT, not an ENOTDIR -- same as OS/2. I'm somewhat dubious of this change. Can you please point to the use case (a