Labview interpreter mode vs. Compiled mode?

[John_]

Dear All,

When we hit the RUN button to execute Labview G-language program, does the G-language program runs in   interpreted-mode  OR  compiled-mode?

I meant, does LabVIEW compiles the G-language source to FULL assembly code   before  executing? (although it does not save it as .exe file without the purchasing the generate-exe-file software option)

I meant, is it true that the fully compiled .exe code (with the extra purchased generate-exe-file software option) will NOT run faster?

[johnsold]

Version 1 of LV ran in interpretted mode. Since then all have been compiled. So, to your last two questions: Yes and Yes.

Lynn

[Ben]

I agree 99.95% with Lynn except...

"will NOT run faster?"

In LV versions prior to LV 8, debugging was disabled in executables. This can be shut off in the development environment as well, in which case they will both run at the same speed. With debugging enabled, there is a very small performance hit.

Questions of this type are usally posted because people are trying to get better performance out of their application. Why were you asking?

Trying to help,

Ben

[LV_Pro]

As Altenbach indicated, this thread and forum are about "G" the underlying language for LabVIEW. As his links indicate, g-code is not the same, it is a "language" defining positioning of CNC or Numerical controlled machine tools.

[LV_Pro]

He may be in a hurry because the postings he refered to were back in June, and on another very old (2005) thread. In that one some discussion was made of g-code interpreters, etc., but as I have tried to explain to others, the chances that someone who posted in 2005 will see a new post in a timely manner (or at all) are slim, unless they are one of the Knights of NI and see all. 😉