From: Jamie Walker <jamie@sagaxis.co.uk>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Sat, 18 Dec 1999 15:56:00 -0000 [thread overview]
Message-ID: <5vhARpAQ5BX4EwUB@howgarth.demon.co.uk> (raw)
In-Reply-To: <385c11fa@oit.umass.edu>
In article < 385c11fa@oit.umass.edu >, Shawn <NRLax27@aol.com> writes
> I am writing a medium sized program, and ran into a problem where gcc
>would not compile any function that did not have all of its variables
>declared as the first lines of the function. As a test, I wrote this small
>program:
In standard C, you cannot declare variables part-way through any
function.
Move them to the top of the function and they will compile fine.
C++ does support what you want, so you could rename your .c files to .C
and gcc will treat them as C++, then they should work fine.
HTH,
--
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: <5vhARpAQ5BX4EwUB@howgarth.demon.co.uk> (raw)
Message-ID: <19991231222400.JN7Bd7E7tG4fEtowYr3cD-i9Pi9fTf5OQU4B2TMEmmc@z> (raw)
In-Reply-To: <385c11fa@oit.umass.edu>
In article < 385c11fa@oit.umass.edu >, Shawn <NRLax27@aol.com> writes
> I am writing a medium sized program, and ran into a problem where gcc
>would not compile any function that did not have all of its variables
>declared as the first lines of the function. As a test, I wrote this small
>program:
In standard C, you cannot declare variables part-way through any
function.
Move them to the top of the function and they will compile fine.
C++ does support what you want, so you could rename your .c files to .C
and gcc will treat them as C++, then they should work fine.
HTH,
--
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)
next prev parent reply other threads:[~1999-12-18 15:56 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 [this message]
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
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=5vhARpAQ5BX4EwUB@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).