public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Brian Gladman" <brg@gladman.plus.com>
To: <gsl-discuss@sourceware.org>
Subject: GSL 1.15 Test Release
Date: Thu, 14 Apr 2011 15:38:00 -0000	[thread overview]
Message-ID: <2F6C8DD90FBE49DEB5AE8CB08D7B1A2E@MobileSlave> (raw)

I have just had a quick look at this on Microsoft Visual Studio 2010 and I 
notice failures when compiling in C as a result of the use of C99's 'out of 
order' declarations (which VC++ doesn't support for C code).

I can deal with these but, before doing so, I wanted to check that this C99 
feature is now acceptable in GSL code and that the use of this feaature is 
not an oversight.

    with my regards,

         Brian Gladman

             reply	other threads:[~2011-04-14 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 15:38 Brian Gladman [this message]
2011-04-14 16:43 ` Brian Gough
2011-04-14 18:58   ` Brian Gladman
2011-04-16 23:01 ` 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=2F6C8DD90FBE49DEB5AE8CB08D7B1A2E@MobileSlave \
    --to=brg@gladman.plus.com \
    --cc=gsl-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).