Alex-Kent

> You say that $fp would control the number of significant figures. > Would it affect the point at which the output switches to exponential notation? Depends on how the...

> i had to write my own number formatting code to see a number of 10-12 digits because i had no way to see what was being rounded off Indeed...

> Although changing that would theoretically be a compatibility break, I would go ahead with it anyway. The #​1 priority should [must] be **don't break existing code**. Apologies for shouting...

> what about programs that are already using $fp for something else? I think the documentation needs to be updated to explicitly state that all `$`* variables are reserved for...

> It isn't clear whether you are trying to avoid using union(), which is what your text says That's my main intent, syntactic sugar to make it clear that the...

> What's wrong with group()? TBH I wasn't aware that that operator existed (it's not on the CheatSheet and is only mentioned in passing [in the docs](https://en.wikibooks.org/wiki/OpenSCAD_User_Manual/The_OpenSCAD_Language) [under **Chapter 6**...

> Why is that mixed behavior needed? That seems very confusing to explain. A simple `{ ... }` would not allow that either. I'm not clear on what you're getting...

> group() is an undocumented operation currently roughly (exactly?) equivalent to union(). It's mentioned in passing in the docs. Looking at the code I _think_ it simply introduces a new...

> allowing leaks from scopes This can be emulated using the current functional syntax: ``` a=1; // b doesn't escape if blocks if (a==1) { b=2; } else { b=3;...

> the most interesting cases for leaks and reassignment - if() and for(). These too can be emulated. `if` can simply be replaced with a conditional. `for` is a bit...