LabView Vs HP VEE and Visual C++

[robert231@my-deja.com]

I am looking for some information on the differences between LabView,
HP VEE, and Visual C++. I am especially interested in Object
Oriented Programming and how that technique compares to what is
written in HP VEE and LabView.


Sent via Deja.com http://www.deja.com/
Before you buy.

[Mani Kay]

As I know, LabVIEW is not object-oriented. There is no consideration
regarding class and object instance. If you have skill writing C++ program,
highly recommened using VC++/MFC.

Mani Kay


robert231@my-deja.com wrote in message <7stmse$gd3$1@nnrp1.deja.com>...
>I am looking for some information on the differences between LabView,
>HP VEE, and Visual C++. I am especially interested in Object
>Oriented Programming and how that technique compares to what is
>written in HP VEE and LabView.
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.

[Labview user name]

I would suggest that you try Labview. You can develop your application in
about 20% of the time it takes to do it in C. By the way it cross assembles
into C at run-time anyway. The application builder will compile your app
into a nice executable ready for distribution.

Mani Kay puked up in message <#rsNPHuC$GA.339@cpmsnbbsa05>...
>As I know, LabVIEW is not object-oriented.

I am laughing so hard I can hardly stand it!

>There is no consideration
>regarding class and object instance. If you have skill writing C++
program,
>highly recommened using VC++/MFC.
>
>Mani Kay
>
>robert231@my-deja.com wrote in message <7stmse$gd3$1@nnrp1.deja.com>...
>>I am looking for some information on the differences between LabView,
>>HP VEE, and Visual C++. I am especial
ly interested in Object
>>Oriented Programming and how that technique compares to what is
>>written in HP VEE and LabView.
>>
>>
>>Sent via Deja.com http://www.deja.com/
>>Before you buy.
>

[Greg_McKaskle2]

> I am looking for some information on the differences between LabView,
> HP VEE, and Visual C++. I am especially interested in Object
> Oriented Programming and how that technique compares to what is
> written in HP VEE and LabView.
>

Keep in mind who I work for and that my impressions aren't totally
unbiased -- they are my opinion.

LV is a compiled dataflow language that is quite powerful in what can be
written in it because of the huge number of libraries available for it
and the modularity. The language itself still has quite a simple
syntax, and it is good for rapid prototyping. The language shares a few
features with object oriented languages, but it is not an object
oriented language.

HP-VEE is an interpreted language that is part dataflow with lots of
control flow melded in. It also have libraries that target it towards
engineering apps, but it hasn't been around as long, and its libraries
and language are not nearly as powerful. It also has a few features
that are like those in object oriented languages, but it isn't object
oriented either.

C++ is very flexible, very complicated, and quite object oriented,
although it is by no means the holy grail of OOP (object oriented
programming). Like C, it is meant to be structured, but flexible enough
to write things like operating systems, complete with embedded assembly,
and the like.

I know two of these quite well, and I'm familiar with VEE and quite a
few similar tools. As for OOP, object oriented design is something that
you can do on any project, and then implement it in anything you want.
There are papers at the last couple NIWeeks by Stepan Riha about GOOP or
graphical OOP with LV. It explains how to construct objects out of VI
sets so that your application is better isolated from changes to the
different objects. I highly recommend looking at his NIWeek99 paper.

If you want to more easily learn OOP, you may want to look at JAVA. If
you have lots of time and must have the most powerful tool ever written,
then be sure to stock up on the C++ books and bury yourself in a hole
for awhile so that it has time to soak in. If you have a job to do, I'd
say you should look at Stepan's paper and try to apply some of those
techniques to your next project and use whatever tool you are proficient in.

Greg McKaskle

[robert231@my-deja.com]

In article <37F4A933.8A7067AB@austin.rr.com>,
GMCKASKLE@austin.rr.com wrote:
> > I am looking for some information on the differences between
LabView,
> > HP VEE, and Visual C++. I am especially interested in Object
> > Oriented Programming and how that technique compares to what is
> > written in HP VEE and LabView.
> >
>
> Keep in mind who I work for and that my impressions aren't totally
> unbiased -- they are my opinion.
>
> LV is a compiled dataflow language that is quite powerful in what can
be
> written in it because of the huge number of libraries available for it
> and the modularity. The language itself still has quite a simple
> syntax, and it is good for rapid prototyping. The language shares a
few
> features with object oriented languages, but it is not an object
> oriented language.
>
> HP-VEE is an interpreted language that is part dataflow with lots of
> control flow melded in. It also have libraries that target it towards
> engineering apps, but it hasn't been around as long, and its libraries
> and language are not nearly as powerful. It also has a few features
> that are like those in object oriented languages, but it isn't object
> oriented either.
>
> C++ is very flexible, very complicated, and quite object oriented,
> although it is by no means the holy grail of OOP (object oriented
> programming). Like C, it is meant to be structured, but flexible
enough
> to write things like operating systems, complete with embedded
assembly,
> and the like.
>
> I know two of these quite well, and I'm familiar with VEE and quite a
> few similar tools. As for OOP, object oriented design is something
that
> you can do on any project, and then implement it in anything you want.
> There are papers at the last couple NIWeeks by Stepan Riha about GOOP
or
> graphical OOP with LV. It explains how to construct objects out of VI
> sets so that your application is better isolated from changes to the
> different objects. I highly recommend looking at his NIWeek99 paper.
>
> If you want to more easily learn OOP, you may want to look at JAVA.
If
> you have lots of time and must have the most powerful tool ever
written,
> then be sure to stock up on the C++ books and bury yourself in a hole
> for awhile so that it has time to soak in. If you have a job to do,
I'd
> say you should look at Stepan's paper and try to apply some of those
> techniques to your next project and use whatever tool you are
proficient in.
>
> Greg McKaskle
>
Thanks for the info, Greg. I went looking for Stepan Riha's paper
on OOP in LabVIEW from NIWEEK 99, but I could not find any of
the papers on National Instruments website. Will they be posted
later or am I not looking in the right place?


Sent via Deja.com http://www.deja.com/
Before you buy.