I am feeling a little controversial today so forgive the blunt title of this post I have never used global variables because I was under the misconception that they are somehow "bad". That is all I have heard from the time I started learning LabVIEW. Look at code in the upconvert and downconvert threads. Some of the ugliest code uses globals and some of the most beautiful code does not. This implies that bad programmers use global variables and therefore globals are bad programming practice. This is not true. Globals are just easy to use so beginners use them. "Uninitialized what? I can't find those on the pallette?" I think I always subconsciously questioned that globals are bad. They are not bad it is how they are used that can be bad. This is true of anything in life. The first and most obvious problem with global variables is race conditions. But it is not strictly the global that causes the race condition. It is the undefined dataflow. But the same is true of a functional global if used incorrectly. In the example below there is nothing to enforce dataflow. You need to enforce the dataflow with an error wire for example. Globals do not have an error wire but not to fear - the sequence man is here! You only need the sequence if the global is directly on your block diagram. Those two single frame sequence structures could be replaced with a NumericWrite.vi and a NumericRead.vi containing nothing but the global, a control or indicator respectively, and the error terminals. Set them to inline and you are good as gold. Or you could have one subvi containing nothing but a two frame case structure selected by an enum containing the items "Get" and "Set". It now looks like a duck and quacks like a duck. Don't worry about overhead from the case structure either. If the enum is a constant it will be folded out. Another problem with globals is that they are, well, global. This is no different from a functional global so it is not really an issue anyway. For both globals and functional globals this is easily addressed by placing them in a library and setting the access scope. Besides that libraries give you namespaces and "Namespaces are one honking great idea -- let's do more of those!" * The real reason to use a global instead of a functional global is that they are about twice as fast. Up until this morning I would have recommended to use a functional global over a global. But I changed my mind. Can anyone change it back? * The Zen Of Python

I go on vacation for a week and I come back to this? Dogs and cats living together... In this thread I swore off Globals once and for all. Flat out bench-marks on just the global may trick you into thinking they are faster but they simply do not allow working in-place. Ease of support is another big factor. Re: call overhead It is a standard to include "extra" terminals on an icon connector but I have benchmarked the "extra terminals" and the call over-head scales with the number of extra copies. Data copies and the most frustrating part ofa global is, you can not do a ctrl-e to fix it. Ben

Return to Home Page
Toggle navigation

Solutions

Industries

Academic and Research
Aerospace, Defense, and Government
Electronics
Energy
Industrial Machinery
Life Sciences
Semiconductor
Transportation

Product Life Cycles

Design and Prototype
Validation
Production

Focus Areas

5G and 6G Technology
ADAS and Autonomous Driving Testing
Electric Vehicle Test
Lifecycle Analytics
Radar and Electronic Warfare
Space Launch and Exploration
Validation Lab Innovations

See our approach to solutions

Get a Helping Hand

From troubleshooting technical issues and product recommendations, to quotes and orders, we’re here to help.

Products

Software

View All Software

LabVIEW
TestStand
FlexLogger
SystemLink
DIAdem
VeriStand
OptimalPlus GO

Software Suites

LabVIEW+ Suite
HIL and Real-Time Software Suite
Circuit Design Suite

SERVICES

View All Services

Repair Services
Calibration
Training Courses

HARDWARE

View All Hardware

Data Acquisition and Control

Learn About DAQ
CompactDAQ Bundles
Multifunction I/O
Voltage
Digital I/O
Temperature
Sound and Vibration
Current
Strain, Pressure, and Force
CompactDAQ Chassis

Electronic Test and Instrumentation
PXI Instrument Bundles
GPIB, Serial, and Ethernet
Switches
Oscilloscopes
Digital Multimeters
Source Measurement Units and LCR Meters

Wireless Design and Test

Software Defined Radios
RF Signal Generators
Vector Signal Transceivers

Application-Specific Systems

Semiconductor Test System
Power Electronics Test Systems

Accessories

Power Accessories
Connectors
Cables
Sensors

FEATURES

Entry-Level DAQ

RESOURCES

Advisors
Distributors

See all products

PC-Based Systems

Benchtop Measurement and Test

CompactRIO

Distributed Measurement and Control

PXI

High-Performance Test

Software

Systems Engineering Software

Perspectives

Perspectives showcases how NI sees what’s next in the world of test and technology.

View all articles

Charting the Course for Test Development with LabVIEW

LabVIEW remains key in test, promising speed, efficiency, and new features with NI’s investment in core tech, community, and integration.

Read our featured article

Support

Resources

View All Support Resources

Software Downloads
Register and Activate
Product Documentation
Release Notes
Online Training
KnowledgeBase
Code Examples

Request Support

You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.

Open a service request

Popular Software Downloads

See all Software Product Downloads

LabVIEW

Multisim

Academic Volume License

Popular Driver Downloads

See all Driver Software Downloads

NI-DAQmx
Provides support for NI data acquisition and signal conditioning devices. 
NI-VISA
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments. 
NI-488.2
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.

Community

About

My Account

Account

Cart

Solutions
- Back
- Industries
- Academic and Research
- Aerospace, Defense, and Government
- Electronics
- Energy
- Industrial Machinery
- Life Sciences
- Semiconductor
- Transportation
- Product Life Cycles
- Design and Prototype
- Validation
- Production
- Focus Areas
- 5G and 6G Technology
- ADAS and Autonomous Driving Testing
- Electric Vehicle Test
- Lifecycle Analytics
- Radar and Electronic Warfare
- Space Launch and Exploration
- Validation Lab Innovations
- See our approach to solutions
Products
- Back
- Software
- View All Software
- LabVIEW
- TestStand
- FlexLogger
- SystemLink
- DIAdem
- VeriStand
- OptimalPlus GO
- Software Suites
- LabVIEW+ Suite
- HIL and Real-Time Software Suite
- Circuit Design Suite
- SERVICES
- View All Services
- Repair Services
- Calibration
- Training Courses
- HARDWARE
- View All Hardware
- Data Acquisition and Control
- Learn About DAQ
- CompactDAQ Bundles
- Multifunction I/O
- Voltage
- Digital I/O
- Temperature
- Sound and Vibration
- Current
- Strain, Pressure, and Force
- CompactDAQ Chassis
- Electronic Test and Instrumentation
- PXI Instrument Bundles
- GPIB, Serial, and Ethernet
- Switches
- Oscilloscopes
- Digital Multimeters
- Source Measurement Units and LCR Meters
- Wireless Design and Test
- Software Defined Radios
- RF Signal Generators
- Vector Signal Transceivers
- Accessories
- Power Accessories
- Connectors
- Cables
- Sensors
- FEATURES
- Entry-Level DAQ
- RESOURCES
- Advisors
- Distributors
- See all products
Perspectives
Support
- Back
- Resources
- View All Support Resources
- Software Downloads
- Register and Activate
- Product Documentation
- Release Notes
- Online Training
- KnowledgeBase
- Code Examples
- Popular Software Downloads
- See all Software Product Downloads
- LabVIEW
- Multisim
- Academic Volume License
- Popular Driver Downloads
- See all Driver Software Downloads
- NI-DAQmx
- NI-VISA
- NI-488.2
- Request Support
- You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required. Open a service request
Community
About
Contact Us
Account