Leaderboard

In LV 2009, this is how I would recommend that the Singleton pattern be implemented: AQSingleton.zip No wrapping library. No replication of VIs caused by having public wrappers and private implementations. No excessive copy overhead. And, yes, thread safety for parallel public calls. This demo class implements three public functions: Set Path, Append Path (which does a read-modify-write) and Get Path. Note that there is one minor issue with this implementation *if* (and only if) you have multiple top-level VIs all using the same central storage and the one that accesses the global first quits before the others are ready. The workaround solutions for that are ... problematic. It is in the set of "holes in the LV language" that we've been slowly patching o'er these many years.