From: Andrew Cagney <ac131313@cygnus.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA 2nd] hpread.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr,..
Date: Fri, 26 Apr 2002 06:32:00 -0000 [thread overview]
Message-ID: <3CC956F6.5000100@cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20020426105725.0233c338@ics.u-strasbg.fr>
> in hpread.c
> there is a line with
> #include "syms.h"
> but there is no syms.h
> in the gdb sources...
>
> If I do a 'grep -n syms.h *.c in gdb directory,
> I get only this:
> $ grep -n syms.h *.c
> hpread.c:29:#include "syms.h"
> somread.c:25:#include <syms.h>
>
> Is the hpread.c file obsolete?
> Or shouldn't it be also
> #include <syms.h>
> like in somread.c?
I need to tread carefuly here, skating on thin ice :-) There is the
strict ISO C defined behavour of "" vs <> and then there are accepted
conventions (note plural).
Within GDB, the accepted convention is to use <> as as "syms.h" is a
system header.
In theory, it should be possible for you to compile hpread.c on any
system, because of includes like the above, it isn't (hence the
MAINTAINERS file marks it as broken). Consequently, yes, ok.
Andrew
next prev parent reply other threads:[~2002-04-26 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 6:18 [RFA/RFC] printf (stderr,... ->fprintf_unfiltered (gdb_stderr,... in hpread.c Pierre Muller
2002-04-24 7:25 ` Daniel Jacobowitz
2002-04-24 12:02 ` Michael Snyder
2002-04-24 12:29 ` Daniel Jacobowitz
2002-04-25 8:38 ` Andrew Cagney
2002-04-25 9:35 ` Pierre Muller
2002-04-25 10:16 ` Andrew Cagney
2002-04-25 11:52 ` Daniel Jacobowitz
2002-04-24 12:08 ` [RFA/RFC] printf (stderr,... ->fprintf_unfiltered(gdb_stderr,... " Michael Snyder
2002-04-24 12:40 ` Daniel Jacobowitz
2002-04-26 2:10 ` [RFA 2nd] hpread.c printf (stderr,... ->fprintf_unfiltered (gdb_stderr, Pierre Muller
2002-04-26 6:32 ` Andrew Cagney [this message]
2002-04-29 4:09 ` Pierre Muller
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=3CC956F6.5000100@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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