Quote:
Originally Posted by Alan Anderson
That contradicts much of what I've heard about both the specific FRC tools we are told to expect (e.g. DYNAMICALLY ALLOCATED!) and the general style of LabView programming I learned a couple of years ago (e.g. "open" a resource and pass the resulting pointer along to everything else that uses it, remembering to "close" it when finished).
I look forward with a mix of anticipation and dread to actually having this stuff in front of me to work with. My optimistic expectation is that I'll quickly realize what simple concept is keeping me from completely understanding what I'm reading, and that I'll finally "get it". (My nagging fear is that I'm a programming dinosaur, stuck in a procedural tar pit and doomed to extinction as the dataflow mammals take over.)
|
A lot of things ARE dynamically allocated, most noticeably, arrays. HOWEVER, the biggest difference is that all the dynamic allocation takes place behind the scenes in LabVIEW. The end-user of LabVIEW, i.e. the programmer, i.e. you, never has to worry about using malloc, calloc or anything like that. The only type of thing that I can think that you should have to "close" would be a TCP connection in LabVIEW. You don't have to "close" any other references or anything like that, I least I never have had to in the years I've been programming.