reference vs local variable

[Vasilich2004]

Steve Chandler

here is the real reason that people still cling to text based programming.

===============

Sorry but I couldn't see any point on first page of your link if you wouldn't confirm that there 50% of hobbiest and 50% of proffessionals who write software and, moreover, with connection to hardware.

[Vasilich2004]

altenbach

It is the development environment asking you "Did I get that right?", basically a grammar checker on steroids. It is a good troubleshooting tool!

=============

if you are so good in development environment could you, please, say me way how can I change function palette to programming VIs instead of express?

[altenbach]

Here's my typical setting. I also make all visible. (pin palette, customize button, change visible ... select all)

[SteveChandler]

@Vasilich2004 wrote:

The program has reentrant execution VI than I will have a lot of copies during debug. Try to track them ... Another "nice" moment is breakpoint inside of reentrant execution VI. When the program stops on the breakpoint inside of  reentrant execution VI there is not any information. If you will decide to stop the program at all and edit then you need to find VI ... in your > 1000 VIs 😉

The trick is to modularize your code. I don't think Mark has a module with 1000 VIs. It is much easier to write and validate large applications in well defined and easily digestable chunks. You then basically plug them together through well defined APIs into an application. Of course this is not specific to LabVIEW but is standard engineering practice.

@Vasilich2004 wrote:

Another problem which I meet constantly that LabVIEW constantly eats memory. I suppose LabVIEW always allocates and deallocates memory instead of re-usage. And it would be nice if someone can suggest way to how I could avoid problem when I come at the morning and see message that LabVIEw doesn't have enough memory.

The Desktop Execution Trace Toolkit is an excellent way to track down your memory leaks. There are many things you can do to write poor applications so nobody can make any suggestions without seeing your code. LabVIEW actually does a very good job of managing memory for you. If you tell it you want all available memory either explicitly or through a bug it will happily comply.

@Vasilich2004 wrote:

Sorry but I couldn't see any point on first page of your link if you wouldn't confirm that there 50% of hobbiest and 50% of proffessionals who write software and, moreover, with connection to hardware.

I don't think it is split down the middle like that. I think that the percentage of people who write LabVIEW code professionally is much higher than the percentage of people who write LabVIEW code as a hobby. That's why Altenbach's idea was such a good one. Hobbyists get jobs and make recommendations to management on purchase decisions.

I get the impression that you do not like LabVIEW. Nobody here is going to force you to use it. If you are more comfortable with C then by all means use it. This is a forum for people who use LabVIEW to discuss the language.

[MKES]

Hi, very interesting discussions presented here.

I'm no expert, in fact, I consider myself a beginner even though I have several years of using LabVIEW 7.1 ... and English is not my native language either.

When I first met LabVIEW it was love at first sight! I discovered a world of possibilities to achieve through its visual programming (I have always been difficult to work with text-based programs).

My job involves working with LabVIEW not all the time but yet many of the daily problems are solved by a "small" program in LabVIEW ... and much of what I know about LabVIEW, I've learned in the discussion forums.).

Considering myself a beginner or talk about making small programs is not to say that's the only thing I do, I have developed some applications involving medium-sized implementation of proprietary protocols, communications over the Internet, among other things, but I know I can still do much more with LabVIEW which perhaps I will achieve with other programming languages, precisely because of its visual programming model.

No one is forced to use LabVIEW instead other programming environments, but those who participate here (or regularly visit the support forums, like me) are interested in two things: 1) better learn the language based on the experiences of others (like me) and 2) help others to learn (when I can, I do, perhaps a small scale) with no other interest than to help spread the love of a "language" that is great (for me in particular)

Sorry guys, I could not avoid giving my opinion. Normally only had read your discussions, sometimes also participated

[richjoh]

Vasilich2004, your a beginner labview programmer. Your post are of no information. Reference vs local is trivia knowledge. What IDE doesn't see all variables. What the purpose of your thread? I've used Visual Studio, it OK, has its place.