its two major limitations: name based linking and a binary file
format.
%
-\nomenclature{DAQ}{Data acquisition. Although the term only refers to
- input, it is sometimes implicitly extended to include signal output
- as well (for controlling experiments as well as measuring results).}
+\nomenclature[text ]{DAQ}{Data acquisition. Although the term only
+ refers to input, it is sometimes implicitly extended to include
+ signal output as well (for controlling experiments as well as
+ measuring results).}
Programming in a graphical language is quite similar to programming in
a textual language. In both, you reduce complexity by encapsulating
package the functional subroutines. In LabVIEW, you package the
subroutines in \emph{virtual instruments} (VIs).
-\nomenclature{VI}{Virtual instrument. LabVIEW's analog to functions
- for encapsulating subroutines.}
+\nomenclature[text ]{VI}{Virtual instrument. LabVIEW's analog to
+ functions for encapsulating subroutines.}
The problem comes when you want to update one of your subroutines.
LabVIEW VIs are linked dynamically by VI name\citep{ni-vi-management},
drastically. There are third-party merge tools\citep{ni-merge} for
LabVIEW, but the tools are not officially supported.
%
-\nomenclature{VCS}{Version control system. A system for tracking
- project development by recording versions of the project in a
- repository.}
+\nomenclature[text ]{VCS}{Version control system. A system for
+ tracking project development by recording versions of the project in
+ a repository.}
While National Instruments seems to put a reasonable amount of effort
into maintaining backwards compatibility, long term archival of binary