02-26-2014
12:58 PM
- last edited on
08-08-2024
11:06 AM
by
Content Cleaner
There was a short discussion after yesterday's presentation (great job Dan, btw!) regarding LabVIEW's compiling process and use of intermediate languages (specifically Dataflow Intermediate Representation (DFIR) and Low-Level Virtual Machine (LLVM)). As promised, here's a look under the hood of LabVIEW compliation process: https://www.ni.com/en/support/documentation/supplemental/10/ni-labview-compiler--under-the-hood.html
Take particular note that the DFIR graph decouples the editor from the compiler representation.
02-26-2014 01:09 PM
My summary of that white paper: Trust the compiler, unless you have a reason not to.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
02-26-2014 01:35 PM
Hooovahh wrote:
Trust the compiler, unless you have a reason not to.
Ha! True, true. But imagine that, since DFIR does decoupling, there's an opportunity for other development environments that exist, and those that we haven't imagined yet, to write "LabVIEW" code.