i'm writing some pan code and i realise after some debugging that (part of) the code might depend on a value of a schema default, eg
object t;
bind "/a" = long = 1;
"/b" = value("/a");which fails with a referenced path (/a) doesn't exist evaluation error
short term question: any tips how to deal with this?
long term question: (this probably doesn't make much sense ;) can we adapt the compiler to look for a schema default when the path doesn't exist (yet)? if the path is set after the value call, it doesn't matter (the result is not the value from the actual profile); if it is not set after the value call, value would return correct result, but no more error.
(actual implementation might be non-trivial, as you have to do recursive schema default searching; and even more so, set the value).
i'm writing some pan code and i realise after some debugging that (part of) the code might depend on a value of a schema default, eg
which fails with a
referenced path (/a) doesn't existevaluation errorshort term question: any tips how to deal with this?
long term question: (this probably doesn't make much sense ;) can we adapt the compiler to look for a schema default when the path doesn't exist (yet)? if the path is set after the value call, it doesn't matter (the result is not the value from the actual profile); if it is not set after the value call, value would return correct result, but no more error.
(actual implementation might be non-trivial, as you have to do recursive schema default searching; and even more so, set the value).