G: Difference between revisions
No edit summary |
Testaccount (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with. | G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with.. | ||
== See Also == | == See Also == | ||
Revision as of 08:20, 7 November 2018
G is the "native" language of LabVIEW. Some arguments might be made as to whether LabVIEW code should instead be called G source code. Let it therefore be said that strictly speaking LabVIEW is the development environment, while G is the code produced under the LabVIEW system. Let it also be added that the graphical language G cannot be re-interpreted into a text based language. You cannot pop the hood on LabVIEW generated code and see the underlying text code, because there is none! Thus G remains the underlying source code that LabVIEW developers work with..