public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <erikd@zip.com.au>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <385C1A3C.41E235D1@zip.com.au> (raw)
Message-ID: <19991231222400.Rd5MPl37lSDzFeYzeWnW20HJhPixW8ZvUPH-7jHGpxg@z> (raw)
In-Reply-To: <385c11fa@oit.umass.edu>

Shawn wrote:
> 
>     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. 

This is one of the differences between C and C++. C++ allows variables
to be declared anywhere a statement could be declared while C insists
all variables be declared at the start of a block.

So, you have two options:

1) Compile your program with g++ (the GNU C++ compiler) instead of gcc.

2) Change your code to legal C.

Erik
-- 
+-------------------------------------------------+
     Erik de Castro Lopo     erikd@zip.com.au
+-------------------------------------------------+
"Anyone who says you can have a lot of widely dispersed people hack
 away on a complicated piece of code and avoid total anarchy has never
 managed a software project." - Andy Tanenbaum in 1992 on comp.os.minix

  parent reply	other threads:[~1999-12-31 22:24 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
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 [this message]
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=385C1A3C.41E235D1@zip.com.au \
    --to=erikd@zip.com.au \
    --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).