[Todo] when udf name is used as a variable

Post Reply
Posts: 111
Joined: September 26th, 2018, 9:36 pm

[Todo] when udf name is used as a variable

Post by bjkwon » July 23rd, 2019, 12:40 pm

If a variable is used with the same as udf name (just the existence of the (name).aux file in the path), the udf name has the precedence; i.e., you use the variable but AUXLAB actually treats it as a udf ==> NO GOOD!!!

This occurs
1) when the variable is used in the main workspace
2) when the variable is used in another udf

This also occurs with the variable name as a class/struct field name, for example,

x.buffer = randperm(10)

will crash if there's a file buffer.aux in the PATH.

Particular caution should be exercised when hidden udf's are written for auxp, such as f2_channel_stereo_mono.aux or default__callback.aux, because users don't see what's going on in those udfs.

This problem has been noticed for a while, but it's getting more annoying. Let's do something...7/23/2019

Post Reply