From: Sam Habiel <sam.habiel@gmail.com>
To: Ken Brown <kbrown@cornell.edu>
Cc: cygwin@cygwin.com, Eric Blake <eblake@redhat.com>
Subject: Re: Help with C clearenv and setenv
Date: Mon, 04 Jun 2018 20:22:00 -0000 [thread overview]
Message-ID: <CABHT960ssuKG9HQgwi=8R9qxFhmQTsieWbTKS1oZ9kTa-r=S4Q@mail.gmail.com> (raw)
In-Reply-To: <e029a690-11fa-ddb7-3702-9e513325b1bb@cornell.edu>
Thank you!
On Mon, Jun 4, 2018 at 3:39 PM, Ken Brown <kbrown@cornell.edu> wrote:
> On 5/31/2018 9:43 AM, Eric Blake wrote:
>>
>> On 05/30/2018 09:48 AM, Sam Habiel wrote:
>>>
>>> I have code for a database I am porting to Cygwin.
>>>
>>> Part of that code is a clearenv() then a couple of setenvs. There is
>>> an ifdef for Cygwin, as it doesn't implement clearenv.
>>
>>
>> It wouldn't be hard to implement clearenv() for a future release of
>> Cygwin, at least for a version that leaves environ pointing to a 1-element
>> array containing NULL. A bit more effort and we could probably also support
>> glibc's notion of environ==NULL being shorthand for an empty environment;
>
>
> I've attempted to do this:
>
> https://cygwin.com/ml/cygwin-patches/2018-q2/msg00024.html
>
> Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-04 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 16:55 Sam Habiel
2018-05-31 3:56 ` Keith Christian
2018-05-31 8:58 ` Sam Habiel
2018-05-31 21:53 ` Keith Christian
2018-05-31 9:38 ` Marco Atzeri
2018-05-31 13:22 ` Eliot Moss
2018-05-31 17:57 ` Eric Blake
2018-06-04 19:39 ` Ken Brown
2018-06-04 20:22 ` Sam Habiel [this message]
2018-06-06 13:02 ` Sam Habiel
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='CABHT960ssuKG9HQgwi=8R9qxFhmQTsieWbTKS1oZ9kTa-r=S4Q@mail.gmail.com' \
--to=sam.habiel@gmail.com \
--cc=cygwin@cygwin.com \
--cc=eblake@redhat.com \
--cc=kbrown@cornell.edu \
/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).