Would you be reluctant to use shift registers in CLD exam?

[DFGray]

I successfully used drjdpowell's method in my CLD, so can second that suggestion.  It is a design feature I almost always use, since it provides both speed and flexibility.  For real designs, I use a typedef for the cluster type to enable easy maintenance of subVIs, especially LabVIEW object command pattern subVIs.  In a CLD exam, you will not have that many subVIs, so the typedef will just slow you down (but would probably help your score).

[drjdpowell]

---

@Ben wrote:

1) Clusters like that should be made into type definitions ( see here ) to allow for easy code changes.

2) ...avoid super-clusters... 

---

Hi Ben,

I would say that the outer cluster in my example, if named, would be called "Things this particular loop is holding in shift registers."  As such, it isn't something that should be used anywhere else in the program, nor should it be sent into subVI's, and thus it gains nothing by being type-defed. It's really a wire organization rather than a data structure, and NOT type-defing it prevents it being used outside its loop.  Now, INSIDE IT may be actual type-defed clusters (or even better, LVOOP objects) that are used throughout the program and passed into subVI's.  So, I might change my example to:

So I agree with your (1) and (2) for clusters used as structured data, but consider this shift-register case to be an exception.

-- James