From: "Brendan Murray" <bpmurray@nospam.mediaone.net>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Sat, 18 Dec 1999 17:44:00 -0000 [thread overview]
Message-ID: <kLW64.3884$su3.135653@wbnws01.ne.mediaone.net> (raw)
In-Reply-To: <dhV64.1216$QU1.6733@newsfeed.slurp.net>
> {
> int fubar;
> for (fubar=0; fubar<bar; fubar++)
> printf("completely fooed\n");
> }
> }
>
> should compile. I believe that fubar is at least lexically visible to the
> end of the function, unlike some languages where the scope would be
strictly
> the block.
>
Nope - once you hit the enclosing "}", fubar's toast. In C, variables have
scope only at the level in which they have been declared; in this case
that's within the block, not to the end of the function.
B=
WARNING: multiple messages have this Message-ID
From: "Brendan Murray" <bpmurray@nospam.mediaone.net>
To: help-gcc@gnu.org
Subject: Re: Declaring variables mid-function
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <kLW64.3884$su3.135653@wbnws01.ne.mediaone.net> (raw)
Message-ID: <19991231222400.1ViacwUwne2H1qrVu2pV-KZFHfGDewtq6Swcj5KryHc@z> (raw)
In-Reply-To: <dhV64.1216$QU1.6733@newsfeed.slurp.net>
> {
> int fubar;
> for (fubar=0; fubar<bar; fubar++)
> printf("completely fooed\n");
> }
> }
>
> should compile. I believe that fubar is at least lexically visible to the
> end of the function, unlike some languages where the scope would be
strictly
> the block.
>
Nope - once you hit the enclosing "}", fubar's toast. In C, variables have
scope only at the level in which they have been declared; in this case
that's within the block, not to the end of the function.
B=
next prev parent reply other threads:[~1999-12-18 17:44 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 [this message]
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='kLW64.3884$su3.135653@wbnws01.ne.mediaone.net' \
--to=bpmurray@nospam.mediaone.net \
--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).