Re: tinkering with inner functions

> Further more I realized that using printf(...) in the
> inner function gives the same compile error ("Toc did not examine an
> inserted check: (x | printf)"). What restrictions do apply for inner
> functions, or what are they meant for? Are they useful in any way?  
> Or are
> they a broken feature?

I believe inner functions are currently broken ... apologies.

> Further more I realized that the  <at> region qualifier is deprecated,  
> does it
> still worker as documented? Is documentation for  <at> effect available?

A pointer in Cyclone can be qualified by a set of region names (the  
effect), rather than just a single name. Where previously we used an  
"outlives" relation on region names to do subtyping, we now use a  
subset relation on effects. There's more information about this in  
the manual, but it was not explicit about the relationship between  
 <at> effect and  <at> region. I've now added a couple of sentences about this.  
The short version is that you can always use  <at> effect in place of  
 <at> region.

For the full story:

http://cyclone.thelanguage.org:80/wiki/Type-Checking%20Regions
(the part about "Subtyping and Effect Qualifiers")

and

http://cyclone.thelanguage.org/wiki/Pointers%20with%20Restricted% 
20Aliasing#SubtypingforEffectQualifierandReaps

-Nik