Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	gdb@sourceware.org, mark@codesourcery.com, paul@codesourcery.com
Subject: Re: Windows support in GDB
Date: Mon, 02 May 2005 15:45:00 -0000	[thread overview]
Message-ID: <20050502154548.GA26295@nevyn.them.org> (raw)
In-Reply-To: <427649B3.5030807@gnu.org>

On Mon, May 02, 2005 at 11:39:31AM -0400, Andrew Cagney wrote:
> >
> >>non-POSIX nature of Windows, which sets its quit far apart from the
> >>traditional Unix-like systems that have been converging towards POSIX
> >>for quite some time now.  This means that we really need to have some
> >>commitment from the Windows user community for maintaining this stuff.
> >>Otherwise this will become another MetroWerks disaster.
> >
> >
> >I don't know what you're referring to.  Are you thinking of the HP
> >merge?
> 
> Mark is correct (and kudos for remembering it, its one of those things 
> I'd rather forget).  Look for files named *mpw*, and macros named MPW, 
> in old sources (oh and also the bitter complaints that ensued as I went 
> through the slow careful process of removing it).

OK, now I'm really curious!  Could you explain the connection to
MetroWerks?  I've used MPW; it stood for Macintosh Programmer's Workshop
at the time, and according to Apple's web pages it still does.

MPW does make a lot more sense in this context, though.  Thanks for the
pointer.  It was certainly a ... unique environment.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-05-02 15:45 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 15:32 Mark Kettenis
2005-04-29 15:32 ` Daniel Jacobowitz
2005-04-29 16:08   ` Christopher Faylor
2005-04-29 16:31     ` Mark Mitchell
2005-04-29 16:36       ` Christopher Faylor
2005-04-29 16:47         ` Mark Mitchell
2005-04-29 16:56           ` Christopher Faylor
2005-04-29 17:05             ` Mark Mitchell
2005-04-29 17:16               ` Christopher Faylor
2005-05-01 20:13             ` Eli Zaretskii
2005-05-01 19:50           ` Eli Zaretskii
2005-04-29 16:52       ` Dave Korn
2005-04-29 16:57         ` Mark Mitchell
2005-04-29 17:00           ` Dave Korn
2005-04-30 16:18           ` Mark Kettenis
2005-04-30 20:37             ` Christopher Faylor
2005-05-01 20:05       ` Eli Zaretskii
2005-05-01 20:06         ` Mark Mitchell
2005-05-01 20:24           ` Eli Zaretskii
2005-04-29 16:32     ` Kris Warkentin
2005-04-29 16:40       ` Christopher Faylor
2005-04-29 17:00         ` Kris Warkentin
2005-05-01 19:55           ` Eli Zaretskii
2005-05-01 21:41             ` Christopher Faylor
2005-05-02 19:03               ` Eli Zaretskii
2005-05-02 19:56                 ` Christopher Faylor
2005-04-29 16:48     ` Daniel Jacobowitz
2005-04-29 17:33       ` Christopher Faylor
2005-04-29 17:58         ` Daniel Jacobowitz
2005-04-29 19:08           ` Christopher Faylor
2005-04-29 19:36             ` Daniel Jacobowitz
2005-04-29 22:01               ` Christopher Faylor
2005-05-02 15:41   ` Andrew Cagney
2005-05-02 15:45     ` Daniel Jacobowitz [this message]
2005-04-29 16:04 ` Kris Warkentin
2005-04-29 16:23 ` Mark Mitchell
2005-04-29 16:46   ` Christopher Faylor
2005-04-29 16:50     ` Mark Mitchell

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=20050502154548.GA26295@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=mark@codesourcery.com \
    --cc=paul@codesourcery.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