Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] microMIPS support
Date: Fri, 27 Apr 2012 15:14:00 -0000	[thread overview]
Message-ID: <alpine.DEB.1.10.1204270320150.19835@tp.orcam.me.uk> (raw)
In-Reply-To: <20120427020603.GA24531@host2.jankratochvil.net>

On Fri, 27 Apr 2012, Jan Kratochvil wrote:

> >  But are you absolutely sure that it was a supported construct with C89 or 
> > are you only assuming having no counter-evidence?
> 
> (a) C89 == C90: http://en.wikipedia.org/wiki/C89_%28C_version%29#C89
> (b) The suggested 'const' construct is compliant with 'gcc -std=c89 -pedantic'.
>     This does not prove it is really C89 compliant but:

 In the absence of an actual copy of the standard itself checking with a 
third-party known-C89/C90-only compiler would be better.

> (c) GDB codebase is already not C90 compliant, at least not
>     with 'gcc -std=c89 -pedantic', as discussed in the thread
>     Re: [no-commit-intention] Naive unnamed fields for main_type
>     http://sourceware.org/ml/gdb-patches/2012-02/msg00146.html

 These are merely bugs IMO, that should simply be fixed instead (and some 
are outside GDB, readline for one is not a part of GDB, just bundled for 
convenience, and optional, though I'd agree that using GDB's CLI without 
readline is a bit painful).  We shouldn't deliberately create new bugs on 
the basis we already have some. ;)

 As I say I'd be first happy to hear we can finally switch to C99.

> I checked according to C90 const array means const elements of the array.
> And 'const type *var;' does not make 'var' const - my conclusion is qualifier
> 'const' is therefore independent for 'var' and the target type.

"const type *var" is a pointer to a variable of "const type" type.
"type *const var" is a const pointer to a variable of "type" type.

> >  At the time I learnt C (some 18 years ago) that certainly wasn't a 
> > construct I had seen in any language reference
> 
> I do not see any problem using const for an array, what specifically do you
> see wrong here?

 Not a const array, but a const pointer.

> >  AFAIK we still require our code to conform to C89 (fortunately not K&R 
> > anymore) or we could use lots of good stuff,
> 
> I agree.  I find const arrays compliant with C89.

 But this is about an array of const pointers, I wouldn't see any problem 
with an array of const arithmetic-type elements.

 So far it's your word against mine, I'd like to hear from someone else 
too.  I'll accept whatever their decision will be.

  Maciej


  reply	other threads:[~2012-04-27 14:49 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 21:18 Maciej W. Rozycki
2012-04-25  6:20 ` Eli Zaretskii
2012-04-26 13:54   ` Maciej W. Rozycki
2012-04-26 14:14     ` Eli Zaretskii
2012-04-26 18:03       ` Maciej W. Rozycki
2012-04-26 20:39         ` Eli Zaretskii
2012-04-27 18:16           ` Maciej W. Rozycki
2012-04-27 18:24             ` Eli Zaretskii
     [not found]               ` <alpine.DEB.1.10.1204302334520.19835@tp.orcam.me.uk>
2012-05-02 16:39                 ` Eli Zaretskii
2012-05-17 15:07                   ` Maciej W. Rozycki
2012-05-17 16:10                     ` Eli Zaretskii
2012-05-18 23:13                       ` Maciej W. Rozycki
2012-05-19  8:20                         ` Eli Zaretskii
2012-04-25 13:13 ` Yao Qi
2012-04-25 15:57   ` Maciej W. Rozycki
2012-04-25 15:54 ` Joel Brobecker
2012-04-25 17:18   ` Maciej W. Rozycki
2012-04-25 18:12     ` Joel Brobecker
2012-04-25 18:27       ` Maciej W. Rozycki
2012-04-26 18:38 ` Jan Kratochvil
2012-04-26 19:04   ` Maciej W. Rozycki
2012-04-26 19:29     ` Jan Kratochvil
2012-04-26 21:59       ` Maciej W. Rozycki
2012-04-27  7:11         ` Jan Kratochvil
2012-04-27 15:14           ` Maciej W. Rozycki [this message]
2012-04-27 15:29             ` Pedro Alves
2012-04-27 15:46               ` Maciej W. Rozycki
2012-04-27 15:54             ` Tom Tromey
2012-05-18 23:53     ` Maciej W. Rozycki
2012-05-18 21:32 ` [PATCH] microMIPS support (Linux signal trampolines) Maciej W. Rozycki
2012-05-18 22:25   ` Mark Kettenis
2012-05-21 14:33     ` Maciej W. Rozycki
2012-06-11 10:32       ` [PING][PATCH] " Maciej W. Rozycki
2014-09-28 11:12       ` [PATCH] " Maciej W. Rozycki
2014-10-06  0:46         ` [PING][PATCH] " Maciej W. Rozycki
2014-10-13 12:24           ` [PING^2][PATCH] " Maciej W. Rozycki
2014-10-20 17:01             ` [PING^3][PATCH] " Maciej W. Rozycki
2014-11-03 16:04               ` [PING^4][PATCH] " Maciej W. Rozycki
2014-11-16  8:58         ` [PATCH] " Joel Brobecker
2014-12-03 21:00           ` Maciej W. Rozycki
2012-05-18 23:47 ` [PATCH] microMIPS support Maciej W. Rozycki
2012-05-19  8:52   ` Eli Zaretskii
2012-05-22  0:07     ` Maciej W. Rozycki

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=alpine.DEB.1.10.1204270320150.19835@tp.orcam.me.uk \
    --to=macro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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