[M3devel] introducing VAR in more places?

[Tony Hosking]

You can, except you need to explicitly give the block scope:

VAR ...
BEGIN
   ...
END;

I find this much better than C++ where the scope of the new variable  
is imprecisely defined.

On Feb 11, 2008, at 4:29 AM, Jay wrote:

> Does anyone else find it bothersome that you can't introduce VARs  
> anywhere? Kind of like in C++?
> Ok, or if you grant that frame size doesn't matter THAT much, and  
> the compiler might do stack packing anyway, you can move all your  
> locals up top like typical C, but still, how about for the module  
> initializer?
> Still it seems good to me to do manual stack packing since it is  
> often so easy..
> WITH helps, but only for "relative constants".
>
> It would be nice if the code below could have still loops until t0 ! 
> = t1, but the repeat condition is outside the scope in which t1 is  
> available. This feels quite lame..
>
>  - Jay
>
>
>
> > Date: Mon, 11 Feb 2008 10:24:00 +0000
> > To: m3commit at elegosoft.com
> > From: jkrell at elego.de
> > Subject: [M3commit] CVS Update: cm3
> >
> > CVSROOT: /usr/cvs
> > Changes by: jkrell at birch. 08/02/11 10:24:00
> >
> > Modified files:
> > cm3/m3-libs/m3core/src/time/WIN32/: Time.m3
> >
> > Log message:
> > no need for globals here..
> >
>
>
> Helping your favorite cause is as easy as instant messaging. You  
> IM, we give. Learn more.