public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "McCunney, Dennis" <DMcCunney@roper.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Date: Mon, 16 Aug 1999 14:55:00 -0000	[thread overview]
Message-ID: <65CAA822B707D211AD430008C7F40FED74843B@EXCHANGERSW2> (raw)

> -----Original Message-----
> From: Chris Faylor [ mailto:cygwin@sourceware.cygnus.com ]
> Sent: Monday, August 16, 1999 4:40 PM
> To: McCunney, Dennis
> Cc: 'cygwin@sourceware.cygnus.com'
> Subject: Re: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
> > 
> >>We don't have correct emulation of IPC semapahores since they are not
> >>implemented at all.  I assume that if you're relying on persistent
> >>semaphores, then some add-on package is being used.
> >
> >How about an additional section in the API FAQ with a list of stuff
> >that _isn't_ implemented, together with a note for each on whether it
> >isn't implemented because you haven't needed to, and if anyone does,
> >please send a patch, or it isn't implemented because you don't think it
> >_can_ be done in the Win32 environment, and if anyone figures out a
> >way, please send a patch?
> 
> This is a good idea.  If you send me a patch for the API FAQ 
> and I'll be glad to add this.

Thanks.  I figured it would cut down a few questions of the "Does Cygwin
implement this?" variety.  I'd be tempted to make it the first thing
a new Cygwin programmer sees. 
 
> If you aren't too sure what to add, you can get started with 
> the semaphores which were mentioned in this thread.  Also, if you peruse
the 
> mailing list archives you should be able to find additional items.

I have a local copy of the FAQ, so I'll start with it.  The mail archives 
will take more doing.  Is there a chance of getting them in a downloadable
form to review locally?  I don't have direct internet access from this work
account (Internet to the desktop is in the planning stages, but Y2K test and
remediation is the current hot button), and doing it via 56K dial-up from
home is a PITA for various reasons.

I would also recommend packaging both the User Guide and the API FAQ with
the FULL.EXE release next time, instead of requiring the users to view
it on line.  I think it would help a lot in cutting down confusion.

I can probably make a start on the list of unimplemented stuff, but you'll 
have to tell me why it wasn't implemented.
 
> Looking forward to your contribution...

I'll do what I can, but I don't recommend holding your breath while you 
wait.  :-)

> -chris
______
Dennis

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: "McCunney, Dennis" <DMcCunney@roper.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: RE: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
Date: Tue, 31 Aug 1999 23:49:00 -0000	[thread overview]
Message-ID: <65CAA822B707D211AD430008C7F40FED74843B@EXCHANGERSW2> (raw)
Message-ID: <19990831234900.KSzSYlRHllTHWL6ZipLajvXamI3PpnRXapgcHzonwuI@z> (raw)

> -----Original Message-----
> From: Chris Faylor [ mailto:cygwin@sourceware.cygnus.com ]
> Sent: Monday, August 16, 1999 4:40 PM
> To: McCunney, Dennis
> Cc: 'cygwin@sourceware.cygnus.com'
> Subject: Re: [HACKERS] backend freezeing on win32 fixed (I hope ;-) )
> > 
> >>We don't have correct emulation of IPC semapahores since they are not
> >>implemented at all.  I assume that if you're relying on persistent
> >>semaphores, then some add-on package is being used.
> >
> >How about an additional section in the API FAQ with a list of stuff
> >that _isn't_ implemented, together with a note for each on whether it
> >isn't implemented because you haven't needed to, and if anyone does,
> >please send a patch, or it isn't implemented because you don't think it
> >_can_ be done in the Win32 environment, and if anyone figures out a
> >way, please send a patch?
> 
> This is a good idea.  If you send me a patch for the API FAQ 
> and I'll be glad to add this.

Thanks.  I figured it would cut down a few questions of the "Does Cygwin
implement this?" variety.  I'd be tempted to make it the first thing
a new Cygwin programmer sees. 
 
> If you aren't too sure what to add, you can get started with 
> the semaphores which were mentioned in this thread.  Also, if you peruse
the 
> mailing list archives you should be able to find additional items.

I have a local copy of the FAQ, so I'll start with it.  The mail archives 
will take more doing.  Is there a chance of getting them in a downloadable
form to review locally?  I don't have direct internet access from this work
account (Internet to the desktop is in the planning stages, but Y2K test and
remediation is the current hot button), and doing it via 56K dial-up from
home is a PITA for various reasons.

I would also recommend packaging both the User Guide and the API FAQ with
the FULL.EXE release next time, instead of requiring the users to view
it on line.  I think it would help a lot in cutting down confusion.

I can probably make a start on the list of unimplemented stuff, but you'll 
have to tell me why it wasn't implemented.
 
> Looking forward to your contribution...

I'll do what I can, but I don't recommend holding your breath while you 
wait.  :-)

> -chris
______
Dennis

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~1999-08-16 14:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-16 14:55 McCunney, Dennis [this message]
1999-08-31 23:49 ` McCunney, Dennis
  -- strict thread matches above, loose matches on Subject: below --
1999-08-17  4:53 Horak Daniel
1999-08-31 23:49 ` Horak Daniel
1999-08-16 11:08 McCunney, Dennis
1999-08-16 13:38 ` Chris Faylor
1999-08-31 23:49   ` Chris Faylor
1999-08-31 23:49 ` McCunney, Dennis
1999-08-16  2:36 Horak Daniel
1999-08-16  7:08 ` [HACKERS] " Tom Lane
1999-08-16 10:08   ` Chris Faylor
1999-08-31 23:49     ` Chris Faylor
1999-08-31 23:49   ` Tom Lane

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=65CAA822B707D211AD430008C7F40FED74843B@EXCHANGERSW2 \
    --to=dmccunney@roper.com \
    --cc=cygwin@sourceware.cygnus.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).