From: Brian Gough <bjg@network-theory.co.uk>
To: gsl-discuss@sources.redhat.com
Subject: Re: Problem building vector/reim_source.c
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15237.2123.33371.640822@debian> (raw)
In-Reply-To: <20010823014055.A68401@oolong.il.thewrittenword.com>
gsl-discuss@lists.thewrittenword.com writes:
> On Mon, Aug 20, 2001 at 12:25:41PM +0100, Brian Gough wrote:
> > gsl-discuss@lists.thewrittenword.com writes:
> > > I've opened a problem report with Sun and gave them a small test case
> > > to reproduce the bug. I'll forward your info below if they need
> > > convincing.
> >
> > Sounds good. You probably saw it on comp.std.c but just for reference
> > this was the simplest test case I could find:
>
> According to the Sun engineer:
> I don't think that's valid C code.
>
> I don't think you can initialize a variable in C with the value of a
> function call like that.
>
> This is using your C code below. Can you point me at the section in
> C89 that says the code below should work?
I've been looking at it some more and it may be a moot point now.
The Sun C compiler accepts the code in gsl_vector if the const is
moved outside the struct, e.g. typedef const struct... instead of
typedef struct { const ... }, which is suitable for this case.
I've checked this into CVS if you want to try it.
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 gsl-discuss
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough [this message]
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` gsl-discuss
2001-12-19 13:20 ` Brian Gough
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=15237.2123.33371.640822@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).