From: Douglas B Rupp <rupp@gnat.com>
To: DJ Delorie <dj@redhat.com>
Cc: ian@airs.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Libiberty for VMS - mkstemps.c don't mix case
Date: Thu, 23 Jul 2009 02:50:00 -0000 [thread overview]
Message-ID: <4A67BBBC.7080104@gnat.com> (raw)
In-Reply-To: <4A67BAA2.4020502@gnat.com>
Douglas B Rupp wrote:
> DJ Delorie wrote:
>>> Well... just because windows users haven't complained doesn't mean
>>> the problem doesn't theoretically exist. I would argue VMS machines
>>> are genrally larger with more simultaneous developers than windows
>>> and so the problem is more likely to occur.
>>
>> I would argue that we already check for file conflicts, and don't need
>> to worry about it.
>>
>> fd = open (pattern, O_BINARY|O_RDWR|O_CREAT|O_EXCL, 0600);
>> if (fd >= 0)
>> /* The file does not exist. */
>> return fd;
>> if (errno != EEXIST
>>
>> If VMS is truly case insensitive, wouldn't it detect such conflicts
>> via the above O_EXCL code?
>>
>
> VMS has file versioning, I think it would detect it only if the version
> was specified or the directory as created with single versioning.
>
There's an obvious flaw in that argument. I'll withdraw the patch for
now pending more testing.
prev parent reply other threads:[~2009-07-23 1:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 0:54 Douglas B Rupp
2009-07-23 1:05 ` DJ Delorie
2009-07-23 1:11 ` Douglas B Rupp
2009-07-23 1:24 ` DJ Delorie
2009-07-23 1:41 ` Douglas B Rupp
2009-07-23 2:24 ` DJ Delorie
2009-07-23 3:38 ` Douglas B Rupp
2010-06-27 19:24 ` Douglas B Rupp
2010-06-28 0:55 ` Douglas B Rupp
2010-06-28 20:27 ` DJ Delorie
2010-06-28 21:19 ` Douglas B Rupp
2010-06-28 22:21 ` DJ Delorie
2009-07-23 2:50 ` Douglas B Rupp [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A67BBBC.7080104@gnat.com \
--to=rupp@gnat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ian@airs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).