9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] A Plan 9 C request....
Date: Wed,  1 Mar 2006 18:17:57 +0000	[thread overview]
Message-ID: <b9edcf2c8fe89ce6f869f1245e0237f9@vitanuova.com> (raw)
In-Reply-To: <61438dea6b0a264f8225382d0c6e2d51@9netics.com>

> when it was added to C++, i "felt" that the scope
> of 'i' wasn't natural; it goes beyond 'for's closure.
> i like a behavior like this:
>
> 	{ int i; for (i = 0, ...) ...; }

when i first started to use Limbo, which has a similar looking
idiom, i thought the same.

	for(i := 0; i < 10; i++) {
	}

but actually, having the variable
available outside the scope is so often useful,
e.g.
	for(i := 0; i < end; i++)
		if(sometest())
			break;
	if(i == end)
		fall_through_condition();

that i now think the non-scoping behaviour is the right thing.

i'm not sure that it's worth adding to plan 9 C though.



  parent reply	other threads:[~2006-03-01 18:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 17:56 Dan Cross
2006-03-01 18:09 ` Skip Tavakkolian
2006-03-01 18:15   ` Brantley Coile
2006-03-01 18:17   ` rog [this message]
2006-03-01 18:20   ` Russ Cox
2006-03-01 18:23     ` Brantley Coile
2006-03-01 18:32       ` Russ Cox
2006-03-01 18:32       ` jmk
2006-03-01 19:59       ` Ronald G Minnich
2006-03-02  4:52         ` Devon H. O'Dell
2006-03-01 18:31     ` Skip Tavakkolian
2006-03-02  4:27       ` David Leimbach
2006-03-02  4:37         ` Andrew R. Reiter
2006-03-02 11:44           ` Brantley Coile
2006-03-01 18:22   ` Richard Bilson
2006-03-02 12:07 Fco. J. Ballesteros
2006-03-02 12:14 ` Richard Miller
2006-03-02 12:25   ` Anthony Sorace
2006-03-02 12:26   ` Brantley Coile
2006-03-03 15:07     ` erik quanstrom
2006-03-04 10:00       ` Richard Miller

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=b9edcf2c8fe89ce6f869f1245e0237f9@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).