Hi.
This definetly has it's uses. The code reuse, and being able to change the scripts without recompiling are good reasons to use it in LabVIEW.
But on http://iel.ucdavis.edu/projects/chlabview/ it says:
"Although using graphical icons is simple and easy, it is quite inefficient for development of applications with special requirements and operations which have not been implemented in advance in a VI. "
The pdf paper gives an example about the discrete cosine function. I doubt very much that the interpreted c/c++ code will be faster then the compiled (!) LabVIEW code. Compiled c/c++ code is usually maximally 10-20% faster then LabVIEW code, often much less. I don't think an interpreted language can be that efficient.
So I don't think execution speed is a valid argument to use a construction like this. It's worth a benchmark though...
I couldn't find the following things in the documentation. Can the Ch script be called directly without saving it to file? How does the user (or the program) get feedback about errors in the Ch script?
Regards,
Wiebe.
