View Single Post
  #22   Spotlight this post!  
Unread 09-09-2008, 19:05
EricVanWyk EricVanWyk is offline
Registered User
no team
 
Join Date: Jan 2007
Rookie Year: 2000
Location: Boston
Posts: 1,597
EricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond reputeEricVanWyk has a reputation beyond repute
Send a message via AIM to EricVanWyk
Re: Why to use LV/C++/C?

Quote:
Originally Posted by Michael Hill View Post
For example, you have absolutely no pointers, no worry of memory allocation or anything.
I am not a software engineer. I am not a LabVIEW expert (barely proficient is stretching it). However, I have (at some point) used more than 10 programming languages, and I have spent enough time with LabVIEW to become frustrated and (later) elated.

I will defer to Greg as to whether or not Michael's assertion is true 100% of the time, forever and ever. I simply don't know.

What I do know is that typical LabVIEW code reminds me of LISP/Scheme in how it handles basic data types. The Liopleurodons among us may benefit of approaching it from that angle - that was the mental leap that made everything "click" for me. Now I think of LabVIEW as Graphical PythonLISP.

To over generalize:
Quote:
Python -adjective
1) readable and approachable
2) utilitarian / lacking blind devotion to a particular ideology.
3) pretty
I will admit that "pre-click", LabVIEW was frustrating. I kept trying to force imperative programming methods which just weren't appropriate. Now I am rather excited to use it for `09 (especially since I haven't mentored a programming team in FIRST in 2 years).