Doug Moen

Reader beware, I went crazy and did an exhaustive survey of range/slice syntaxes. Set notation is not specifically an American thing. I'm not American anyway. Set theory is the foundation...

By "when the vector is saved", I assume you mean when the model is exported (as STL, AMF or whatever). No, I don't think it is useful to discard part...

The current OpenSCAD range syntax is [start:step:end]. You propose to replace this with range(start,end,step), changing the order of the arguments. You claim that this is more readable for the step...

One more comment. With my proposed range syntax, [2,4..10] is the sequence of all even integers from 2 to 10. It's very similar to set builder notation from high school...

I'll explain why I wrote that. OpenSCAD2 has first class function values. A function call has the syntax `f(x,y,a=z)`. What are the semantics of function call? I intend for there...

Yes, I've considered this type of design as well. The syntax I came up with was `v$abc` for a variable, `f$abc` for a function, and `m$abc` for a module. These...

The "OpenSCAD2" proposal has a few problems, and one of them is the inability to work with OpenSCAD libraries that define the same name in different namespaces. The `v$`, `f$`,...

OpenSCAD2 has a single namespace, but it needs to be compatible with libraries written in the older dialect, which has 3 namespaces. Suppose you write some OpenSCAD2 code: ``` M...

@Ma-XX-oN said: "for referencing the two different namespaces, you could use M.foo and M.f$foo. Variables wouldn't need the decoration as it is implied." That doesn't work reliably. Suppose that M...

@Ma-XX-oN said: How about this: unless a the symbol exists in more than one namespace, disambiguating would not be necessary, and an error would be displayed when trying to reference...