I wrote: > But I was thinking of adding a per_frame: variant, that would > just have the same semantics, but looks different from an > assignment.
Done. > At least with the per_frame: syntax, it may also make sense to > enforce an initial - per_frame - per_vertex sequence, with each > patch being allowed at most one per_frame: and per_vertex: Did that too. > Ah yes, I was wondering about that :-) Compile-time evaluation > of constant subexpressions - anywhere - would definitely make > sense. Constant folding is now done for: +, - (unary and binary), *, /, %, above, below, equal, max, min, if, ? :, and sqr. I cowardly stayed away from anything that would need libm :) > >> foo = bar ? sin(time) : 1-cos(time) > > > > I'm for this option. Done. > I'm also considering getting rid of the operator > precedence directives and just express precedence within the > grammar, following the example of K&R 2nd Ed. This needs a > few more rules but tightens the semantics. Also done. The language is beginning to look usable ;-) Still have a few more small items left, though. - Werner _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
