My Adieu to LabVIEW : Your Comments

[Ben]

---

Fragger Fox wrote:

---

Raghunathan wrote:

>>Just requested an evaluation cd of VEE from the Agilent Website! 

So its the exit gate for LV. And enter VEE ??

---

No....Just giving VEE a try! 😄

I can't leave LV so easily....I am so addicted to it.....and so am I addicted to these forums!! 🙂

---

My closest exposure to HP VEE gave me the impression that HP VEE was single threaded. Can anyone who knows HP VEE confirm or strike down that observation?

Ben

[tbob]

---

Ben wrote:

My closest exposure to HP VEE gave me the impression that HP VEE was single threaded. Can anyone who knows HP VEE confirm or strike down that observation?

Ben

---

I worked with VEE a while back.  I seem to remember that there was an execution flow terminal.  Instead of data flow, there was an execution flow dictated by wires.  I think you could branch the execution into two separate threads, and then join them back at some point.  So I think VEE has multi thread capabilities.  The execution flow terminal is pretty much same as using Error In and Error Out to dictate execution flow in LV.

[Ray.R]

The little bit of exposure to Vee did seem like you could wire objects in parallel.  I do not know if the actually executed in a parallel manner as LV does.

[lavalava]

---

parthabe wrote:

---

lavalava wrote:

http://forums.ni.com/ni/board?board.id=180

---

So, you work in both LV & CVI?

---

No, I'm still pretty new to CVI.  I don't think I will be messing around with it anytime sooner despite already having licenses for it because we purchased developer suites.  We chose LV for its unique G language, otherwise we would've picked something else.  If I ever need to mess around with C/C++ version with Labview then I'll use visual studio with measurement studio libraries and go from there.  But there is really little motivation for that because G version of LV already answered most of our needs and we get it done so much faster.  If there is such motivation that would driven me toward using C/C++ then it would be relating to MDI and true concurrency/multithreading.  Other than that, you can do just about anything else with LV as in any other languages.  Right now most of my applications are SDI with multiple popups communicating through TCP sockets.  I hate popups but we just live with it for the time being.

Message Edited by lavalava on 04-07-2010 03:32 PM

[lavalava]

---

smercurio_fc wrote:

---

lavalava wrote:
What ever you do to enhance your career success for the long run, stay away from MS proprietaries like C#, VB, etc.... , instead stick to traditional stuffs like C/C++.    Did you know if you don't like looking at wires, you can always opt for a version of CLV, that's doing the same thing as wire but you do with text base in C language?  If you purchase the developer suite, they all come with wire based LV, CLV, and even classes for Visual Studio where you can do even more than what CLV has to offer.

---

So by that argument we should also be staying away from proprietaries like ... LabVIEW? 

---

DOH!  You got me there!

But then again, labview G language is still one of the kind.  Other imitation from late comers don't count.   So let's add in C/C++/G++, how about that for a change?

[querty999]

I you want to increase your versatility as a programmer then learning to program in C is a good choice. Here is a link suggesting that C is the most widely used programming language. If you have the luxury of knowing for sure that your entire career will be in a LabVIEW environment then G language may be all you need. But if you ever have to go looking for a job you'll be better off with a broader skill set.

I've programmed for 25 years, mostly in C but also in Fortran. Practically all control and database vendors have a C programming library. NI is no acception. For that reason I prefer CVI over G language. Once you become fluent in C you can produce good CVI applications in a reasonably short period of time. Difficult applications require a lot of effort regardless of the programming language involved.

[Guruthilak]

---

Ben wrote:

My closest exposure to HP VEE gave me the impression that HP VEE was single threaded. Can anyone who knows HP VEE confirm or strike down that observation?

Ben

---

VEE is multithreded.

During a code walkthrough i noticed that two functions are connected by means of "broken lines". And then i asked stupid questions... "Hey how you managed to make the line look like broken?" and i got a weird look from the other person and later he informed that its not the "broken lines" but some asynchronus data transfer or something like that (i dont remeber what he said but i can still remeber his look)

Guru