Peter McCulloch

Vexpr doesn't seem to be able to switch values for symbols the way expr can. In the expr examples, there's this:

expr $s2[$i1] where $s2 is the name of the table to reference for lookup. This is really nice. Vexpr will let you put a table name when you create it, but it won't accept values in the format #0-name, so you can't have a lookup that's specific to an abstraction. Also, vexpr doesn't know what to do with symbols in the inlets even with scalarmode on.

Any chance this could get fixed in a point update?

Vexpr doesn't seem to be able to switch values for symbols the way expr can.  In the expr examples, there's this:

expr $s2[$i1] where $s2 is the name of the table to reference for lookup.  This is really nice.  Vexpr will let you put a table name when you create it, but it won't accept values in the format #0-name, so you can't have a lookup that's specific to an abstraction.  Also, vexpr doesn't know what to do with symbols in the inlets even with scalarmode on.

bug-vexpr-expr-symbol-compatibility-with-0

Agree... 11 years later. This is a bit frustrating.

A conceivable workaround is to translate the #0 value into something alphanumeric which vexpr tolerates as a table name, then you just need to script connections to make up the difference.

image.png

Agree... 11 years later.  This is a bit frustrating.

Bug: Vexpr / expr symbol compatibility with #0