public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jamie Walker <jamie@sagaxis.co.uk>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Sun, 19 Dec 1999 12:15:00 -0000	[thread overview]
Message-ID: <pMs0JeAnkSX4EwEA@howgarth.demon.co.uk> (raw)
In-Reply-To: <jayaarzrhd.fsf@gatsby.u-net.com>

In article < jayaarzrhd.fsf@gatsby.u-net.com >, David Wragg
<dpw@doc.ic.ac.uk> writes
>Jamie Walker <jamie@sagaxis.co.uk> writes:
>> In standard C, you cannot declare variables part-way through any
>> function.
>
>Yes you can. ISO C99 was passed a couple of months ago, and allows
>mid-block declarations.
Thanks for that, David.
>
>Of course, there are no compilers available yet that comprehensively
>implement C99, and probably won't be for a couple of years (though
:o)
-- 
Jamie Walker                                  http://www.sagaxis.co.uk/
"lp1 reported invalid error status (on fire, eh?)", Linux error message
       PGP Key ID: 0x1B6BBB15 (available on public key servers)

WARNING: multiple messages have this Message-ID
From: Jamie Walker <jamie@sagaxis.co.uk>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <pMs0JeAnkSX4EwEA@howgarth.demon.co.uk> (raw)
Message-ID: <19991231222400.MIOJu-4M4gprHt4EvhQ56kkb0jN2XpLelXaEUVEiBUo@z> (raw)
In-Reply-To: <jayaarzrhd.fsf@gatsby.u-net.com>

In article < jayaarzrhd.fsf@gatsby.u-net.com >, David Wragg
<dpw@doc.ic.ac.uk> writes
>Jamie Walker <jamie@sagaxis.co.uk> writes:
>> In standard C, you cannot declare variables part-way through any
>> function.
>
>Yes you can. ISO C99 was passed a couple of months ago, and allows
>mid-block declarations.
Thanks for that, David.
>
>Of course, there are no compilers available yet that comprehensively
>implement C99, and probably won't be for a couple of years (though
:o)
-- 
Jamie Walker                                  http://www.sagaxis.co.uk/
"lp1 reported invalid error status (on fire, eh?)", Linux error message
       PGP Key ID: 0x1B6BBB15 (available on public key servers)

  reply	other threads:[~1999-12-19 12:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-18 15:01 Shawn
1999-12-18 15:52 ` llewelly
1999-12-31 22:24   ` llewelly
1999-12-18 15:56 ` Jamie Walker
1999-12-18 16:11   ` bowman
1999-12-18 17:44     ` Brendan Murray
1999-12-31 22:24       ` Brendan Murray
1999-12-21  9:19     ` Arthur Gold
1999-12-31 22:24       ` Arthur Gold
1999-12-31 22:24     ` bowman
1999-12-19  4:01   ` David Wragg
1999-12-19 12:15     ` Jamie Walker [this message]
1999-12-31 22:24       ` Jamie Walker
1999-12-31 22:24     ` David Wragg
1999-12-31 22:24   ` Jamie Walker
1999-12-18 16:02 ` Erik de Castro Lopo
1999-12-31 22:24   ` Erik de Castro Lopo
1999-12-31 22:24 ` Shawn

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=pMs0JeAnkSX4EwEA@howgarth.demon.co.uk \
    --to=jamie@sagaxis.co.uk \
    --cc=help-gcc@gnu.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).