Five years ago that should have been LabVIEW 4 or 5. But then, as
we've seen here, some people keep versions around forever. I have
always worked with the professional packages, so I've always had
access to compilers for LabVIEW.
Where I work now, we use Perforce for revision control. It works
great. I've also used Visual Source Safe and I'll stick to Perforce,
thanks. You can even set the client to automatically sign out the code
if you change to edit mode on the diagram.
AS others have said - LabVIEW excels at equipment connectivity. An
example from my past: a C programmer had spent 2.5 days building a
terminal type of program to talk to our equipment. He gave me the DLL
that he was using for communications and watched as I built the same
program in LabVIEW and completed in 15 minutes. His comment was that
he was probably going to be relegated to supporting the old code while
I made the new code and for the most part he was right.
Rob
