From: "Williams, Gerald S \(Jerry\)" <gsw@agere.com>
To: "Thread TITTTL'd!" <cygwin-talk@cygwin.com>
Subject: RE: Re: Handling special characters (\/:*?"<>|) gracefully
Date: Wed, 24 May 2006 16:05:00 -0000 [thread overview]
Message-ID: <4C89134832705D4D85A6CD2EBF38AE0F3E0992@PAUMAILU03.ags.agere.com> (raw)
Dave Korn wrote:
>> I actually use a version of such a library to create some of
>> the otherwise-uncreatable files in a /dev directory (which is
>> not on a managed mount). That way, I can do:
>
> Is this code public?
Some of it is, sort of.
I finally got permission from my company to release it into
the public domain. I even went so far as to create a project
on sourceforge.
One problem is that in order to understand something of the
internal operation of Windows, I was working on this while
looking at the ReactOS code, so initially I pulled several
of their definitions into a header file. I had set up the
project (and received permission to release the code) as a
public domain project, not under the GPL, so it needed to
be cleaned a bit. Looking at the file now, it appears that
I did finally remove the blatantly copied declarations. I
may want to run the file past the ReactOS developers just
to make sure, though.
Now, the whole point to the project was to make something
available that Cygwin could use, since my company would not
sign the release that allowing me to contribute directly.
(This is another reason why the code couldn't be GPL'ed.)
Since Cygwin went in another direction, I pretty much let
it drop.
At that time, I had completed the following routines:
CaseWiseCreateDirectory
CaseWiseCreateDirectoryA
CaseWiseCreateDirectoryW
CaseWiseCreateDirectoryEx
CaseWiseCreateDirectoryExA
CaseWiseCreateDirectoryExW
CaseWiseCreateFile
CaseWiseCreateFileA
CaseWiseCreateFileW
CaseWiseSetCurrentDirectory
CaseWiseSetCurrentDirectoryA
CaseWiseSetCurrentDirectoryW
And was working on:
CaseWiseMoveFile
If you're interested, I can clean up the project and make
sure the existing files are properly published.
gsw
next reply other threads:[~2006-05-24 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 16:05 Williams, Gerald S (Jerry) [this message]
2006-05-24 16:34 ` Dave Korn
2006-05-24 16:38 ` Christopher Faylor
2006-05-24 16:52 ` Dave Korn
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 14:04 Williams, Gerald S (Jerry)
2006-05-25 13:45 Williams, Gerald S (Jerry)
2006-05-25 13:55 ` Dave Korn
2006-05-25 14:35 ` Christopher Faylor
2006-05-26 5:21 ` Joe Smith
2006-05-26 5:40 ` Christopher Faylor
[not found] <4C89134832705D4D85A6CD2EBF38AE0F3E0956@PAUMAILU03.ags.agere.com>
2006-05-24 9:31 ` Dave Korn
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=4C89134832705D4D85A6CD2EBF38AE0F3E0992@PAUMAILU03.ags.agere.com \
--to=gsw@agere.com \
--cc=cygwin-talk@cygwin.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).