public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: paul-ml@is.lg.ua
Cc: cbjones@nortelnetworks.com, cygwin@sourceware.cygnus.com
Subject: Re: Cygwin 1.1.0 gdb troubles
Date: Wed, 19 Apr 2000 07:22:00 -0000	[thread overview]
Message-ID: <200004191421.KAA22811@envy.delorie.com> (raw)
In-Reply-To: <7703.000419@is.lg.ua>

> Almost any POSIX feature maps one-to-one to win32 one and difference
> is only in some idiosyncratic details.

This is an understatement.  For every feature that maps one-to-one, it
seems like there are a dozen idiosyncratic details that make it
difficult to meet the POSIX requirements.  A large portion of Cygwin
is devoted to these details.

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

  reply	other threads:[~2000-04-19  7:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-19  6:02 Christopher Jones
2000-04-19  7:15 ` Re[2]: " Paul Sokolovsky
2000-04-19  7:22   ` DJ Delorie [this message]
2000-04-19 12:19     ` Paul Sokolovsky
2000-04-19 12:31       ` DJ Delorie
2000-04-19 16:27       ` Chris Faylor
2000-04-19 10:05   ` Chris Faylor
2000-04-20 23:37     ` Re[2]: " Paul Sokolovsky
2000-04-21  8:08       ` Chris Faylor
2000-04-19  9:47 ` Chris Faylor
  -- strict thread matches above, loose matches on Subject: below --
2000-04-19 10:45 Christopher Jones
2000-04-19 10:49 ` Chris Faylor
2000-04-18 15:04 Heribert Dahms
2000-04-18 14:32 Heribert Dahms
2000-04-18 14:39 ` Chris Faylor
2000-04-18 14:11 Heribert Dahms
2000-04-18 14:26 ` Chris Faylor
2000-04-17 21:32 Boyd Adamson
2000-04-17 21:47 ` Chris Faylor
2000-04-17 22:30   ` Chris Faylor
2000-04-17 23:41     ` Boyd Adamson
2000-04-18 12:29       ` Chris Faylor
2000-04-18  6:12   ` Tim Prince
2000-04-18 13:17     ` Chris Faylor

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=200004191421.KAA22811@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cbjones@nortelnetworks.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=paul-ml@is.lg.ua \
    /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).