From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: tromey@redhat.com
Cc: jan.kratochvil@redhat.com, brobecker@adacore.com,
gdb-patches@sourceware.org
Subject: Re: [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes]
Date: Sun, 12 Feb 2012 10:20:00 -0000 [thread overview]
Message-ID: <201202121019.q1CAJoQw025308@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <87y5saa3zs.fsf@fleche.redhat.com> (message from Tom Tromey on Fri, 10 Feb 2012 12:21:43 -0700)
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 10 Feb 2012 12:21:43 -0700
>
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> `long long' is apparently not supported by ISO C90 compilers, so it
> Jan> is a bug if GDB claims C90 compatibility. Or what do you mean?
>
> I mean that this is clearly a C90 violation.
>
> Another question is whether some compilers accept parts of C99 but not
> all of it.
Quite a few compilers do. For example, 'long long' was a popular
extension adopted by many vendors even before C99 was ratified.
On OpenBSD we still have some platforms stuck with GCC 2.95. It
already includes quite a bit of C99 functionality, but some bits are
missing. The most important one is that it doesn't allow declarations
after statements. But I (and many C programmers with me) consider
that to be bad style and a C99 misfeature anyway.
next prev parent reply other threads:[~2012-02-12 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 9:28 [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Jan Kratochvil
2012-02-09 9:32 ` [no-commit-intention] Naive unnamed fields for main_type [Re: [patch] Fix gdb-gdb.py for flds_bnds copy-pastes] Jan Kratochvil
2012-02-09 15:16 ` Joel Brobecker
2012-02-09 15:37 ` Jan Kratochvil
2012-02-09 18:56 ` Eli Zaretskii
2012-02-10 18:05 ` Tom Tromey
2012-02-10 19:01 ` Jan Kratochvil
2012-02-10 19:22 ` Tom Tromey
2012-02-10 19:29 ` Jan Kratochvil
2012-02-12 10:20 ` Mark Kettenis [this message]
2012-02-12 19:23 ` Jan Kratochvil
2012-02-09 19:07 ` Alfred M. Szmidt
2012-02-09 19:23 ` Stan Shebs
2012-02-10 18:07 ` Tom Tromey
2012-02-09 15:12 ` [patch] Fix gdb-gdb.py for flds_bnds copy-pastes Joel Brobecker
2012-02-09 15:15 ` [commit] " Jan Kratochvil
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=201202121019.q1CAJoQw025308@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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