| Another little evidence of the lie of statelessness: If there is no state needed to desribe a model, and it's wrong to want it and there is no valid reason to want to define and then overwrite a value, because you should have just set the value the right way in the first place... ...then why does it matter what order I write the assignments in the file? Why is it an error to describe a relationship between values that haven't been assigned yet, if there is supposedly no such thing as "yet" in a stateless timeless world? The assignments are there later in the file. The described relationship is valid. This leads to yet other contortions and sometimes flat limitations when there is a relationship between 2 values, but either one may possibly come first and be used to decide something automatically about the other. Sometimes you can handle that by just having provisional desired values for both, that can both be assigned without conflict up front, and you evaluate the relationship between them later to get other actual values, but sometimes that's not actually so simple. But regardless of workarounds, my point is more to show a very simple thing that exposes the fallacy of the proffessed ideal. If you (not you, an openscad dev) would tell me that I don't need state from you, then why do you need state from me? |