Argument order for shape-taking (nesting) functions about libfive HOT 4 CLOSED

That's an interesting idea!

The main reason why I chose the current API structure is for functions that take optional arguments. For example, rotate-z takes an optional center to rotate about, which needs to be at the back of the argument list.

Since this is Scheme, I think that that the right solution is some kind of rewriting macro. Consider the following hypothetical code:

(sequence (mysphere x y z 0.2)
          (scale-y 1.5)
          (rotate-y 0.1)
          (move #[0.1 0.2 0.3]))

which both has arguments near the transformations, and puts things in the actual order of execution!

How does that sound?

from libfive.

That seems great! (I'm still not quite grasping exactly how the flow of information works in Scheme if something like that is possible, apparently...)

Also, if that turns out to be too much work, and optional arguments are the only issue, you could always just have multiple differently-named functions instead, like (rotate-z 0.1 myshape) vs (rotate-z-about 0.1 #[0.1 0 0] myshape)

from libfive.

Okay, sequence is in, and works just like I showed above.

Rewriting syntax on the fly is amazing 😁

from libfive.

Fantastic! That works beautifully. Thank you :)

from libfive.