Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Suggested ways to remove the need for xm-go32.h
Date: Mon, 20 Sep 2004 03:33:00 -0000	[thread overview]
Message-ID: <01c49ec2$Blat.v2.2.2$834381e0@zahav.net.il> (raw)
In-Reply-To: <200409191144.i8JBiSA7045711@elgar.sibelius.xs4all.nl> (message from Mark Kettenis on Sun, 19 Sep 2004 13:44:28 +0200 (CEST))

> Date: Sun, 19 Sep 2004 13:44:28 +0200 (CEST)
> From: Mark Kettenis <kettenis@gnu.org>
> CC: gdb-patches@sources.redhat.com
> 
> Thus far, we've required a ISO C compliant *compiler*, but not
> strictly ISO C compliant *libraries*.  The reasoning behind this is
> that it's easy to replace the compiler (with gcc), but not so easy to
> replace the system libraries.

I think it's a really rare case that a system has an ISO compiler, but
a non-ISO library (last time I saw such a system was back in 1994: it
was a SunOS 4.3 box where I installed GCC).  Nowadays an ISO compiler
goes with an ISO library, and "rb" and friends were mandated by C89,
not the latest C9x.

> I think it'd be better to have wrapper functions that try to open the
> file using the "b" modifier, and if that fails, retry without.  It's a
> bit more work, but it should be more robust.

If people prefer this, I don't mind.

> Why not have a list of files to try?  That would mean we'd always try
> "gdb.ini" if ".gdbinit" fails, even on Unix.

I have no problems with that, I just thought that Unix users will not
want "gdb.ini".

>    4.  DIRNAME_SEPARATOR: The DOS-specific definition can be put either
>        in defs.h or local to the only file that uses it (source.c).
> 
> We should probably include "filenames.h" and base the definition on
> HAVE_DOS_BASED_FILE_SYSTEM.

I don't think this will be good, since Cygwin uses
HAVE_DOS_BASED_FILE_SYSTEM, and its DIRNAME_SEPARATOR is ':'.  More
generally, HAVE_DOS_BASED_FILE_SYSTEM is somewhat orthogonal to the
DIRNAME_SEPARATOR issue.


  reply	other threads:[~2004-09-20  3:33 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 13:21 Eli Zaretskii
2004-09-19 11:44 ` Mark Kettenis
2004-09-20  3:33   ` Eli Zaretskii [this message]
2004-09-22 20:21     ` Michael Chastain
2004-09-23  4:51       ` Eli Zaretskii
2004-09-23  6:02         ` Michael Chastain
2004-09-23  8:14   ` Corinna Vinschen
2004-09-23  5:03 ` Christopher Faylor
2004-09-23  6:30   ` Michael Chastain
2004-09-23  8:02     ` Corinna Vinschen
2004-09-24 10:51       ` Eli Zaretskii
2004-09-24 14:35         ` Andrew Cagney
2004-09-23 13:56     ` Christopher Faylor
2004-09-23 17:20       ` Michael Chastain
2004-09-23 17:24         ` Christopher Faylor
2004-09-23 15:18     ` Joel Brobecker
2004-09-23 17:57       ` Daniel Jacobowitz
2004-09-24 15:05         ` Andrew Cagney
2004-09-25 16:43           ` Eli Zaretskii
2004-09-26 18:38             ` Mark Kettenis
2004-09-27  2:29           ` Daniel Jacobowitz
2004-09-23 20:58   ` Mark Kettenis
2004-09-23 21:14     ` Christopher Faylor
2004-09-24 10:48       ` Eli Zaretskii
2004-09-24 12:23         ` Corinna Vinschen
2004-09-24 13:39           ` Andreas Schwab
2004-09-24 19:51             ` Christopher Faylor
2004-09-24 21:16               ` Christopher Faylor
2004-09-24 21:32               ` Andreas Schwab
2004-09-24 13:40           ` Eli Zaretskii
2004-09-24 16:49           ` Ian Lance Taylor

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='01c49ec2$Blat.v2.2.2$834381e0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@gnu.org \
    /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