LabVIEW
line macro equivalent in labview
Ooooh! Ben!
With LabVIEW being a "data flow" language, if the original program has used the error cluster concept there should be a traceback to the source of the error through the call chain. It would still require, as in Ben's earlier example, putting the error logging code in a number of places. If you have a vi that is used in a number of locations then that would definitely be one location. Then if an error occurs with in it, or upstream of it, you would have the specific instance of the vi identifiable with the call chain, it being relatively unlikely that you would have matching call chains for different instances (unless it is used multiple times in the same vi, then you would need a way to ID the specific call instance). LabVIEW doesn't (to the best of my knowledge) have an equivalent debug tool to the one you mention, basically because "line numbers" have no meaning in its development environment, and if there is any "grid references" (and there probably are to the editor) they probably are lost at compile time, so wouldn't be there in the exe.
If the original program didn't use error chaining, well short of refactoring it to use it (which I understand is probably not do-able) I'm not sure how you would compartmentalize the code to isolate the errors.
Question:
Does the "Line macro" provide error reporting after a program has been compiled into an exe? If so I suspect what is being done "automatically" is that the equivalent to the error logger vi's is being inserted into the code by the compiler.
@LV_Pro wrote:
Ooooh! Ben!
With LabVIEW being a "data flow" language, if the original program has used the error cluster concept there should be a traceback to the source of the error through the call chain. It would still require, as in Ben's earlier example, putting the error logging code in a number of places. If you have a vi that is used in a number of locations then that would definitely be one location. Then if an error occurs with in it, or upstream of it, you would have the specific instance of the vi identifiable with the call chain, it being relatively unlikely that you would have matching call chains for different instances (unless it is used multiple times in the same vi, then you would need a way to ID the specific call instance). LabVIEW doesn't (to the best of my knowledge) have an equivalent debug tool to the one you mention, basically because "line numbers" have no meaning in its development environment, and if there is any "grid references" (and there probably are to the editor) they probably are lost at compile time, so wouldn't be there in the exe.
If the original program didn't use error chaining, well short of refactoring it to use it (which I understand is probably not do-able) I'm not sure how you would compartmentalize the code to isolate the errors.
Question:
Does the "Line macro" provide error reporting after a program has been compiled into an exe? If so I suspect what is being done "automatically" is that the equivalent to the error logger vi's is being inserted into the code by the compiler.
I'm sorry Putnam*.
Please forgive me.
Ben
*Appologies extended to Aristos Queue and all of his group as well for even suggesting mis-using LVOOP in that way. 
