LabVIEW
Tell us about your large LabVIEW applications!
Brittner,
I don't feel hurt personally, it's simply a matter of expressing opinions. Your opinion is valid (for yourself) as is everyone else's (for themselves). As such there's no overlap, and also no reason to feel hurt.
I didn't intend for my last post to be interpreted as me being
annoyed. I'm not. It was meant as a simple statement of
fact.
I don't have the "show buffer allocation" tool, because I'm working with LV 6.1. There are some rules to wiring large data sets which can greatly avoid memory overhead. When working with large arrays and basically just reading values, even from sub-sets of the original array (without modifying the array) make sure to wire the array through the structure or sub-vi you're doing the work in. This will actually AVOID copies. It seems counter-intuitive because you're passing the array to a sub-routine (which kind of suggests more copying, not less) but the LV compiler is "smart" enough to realise you're not chenging the array and passes it "Byref" instead of "Byval". At least that's my understanding, but I don't have a formal programmer training, so I may be wrong.
LV is a different programming language (and indeed paradigm) so it DOES take time to learn the subtelties. I can also understand that 10 copies of a 10MB array doesn't seem like a subtelty when it happens unexpectedly, but there's always a way to avoid it. This is another reason why everyone says local and global variables are bad. Each one generates a copy......
I don't take exception with your programming skill, quite the contrary. If I think back at what I did with LV when I started I shudder and a shiver runs down my spine. What I did take exception with (on a factual level, not a personal one) was your damnation of LV due to something which CAN be avoided when you know how.
I don't think your post is "polluting" anything. It's important to have different views, but it's also important to be willing to learn something instead of quickly blaming something as being faulty. A quick question as to why LV creates so many copies instead of claiming it simply "automatically" creates copied would have generated a totally different response, and would have most likely lead to several people taking time to explain things to you. In this way, everyone wins.
On a side note, I don't accept apologies where they're simply not neccessary. Don't worry. I don't fly off the handle quite that easily.
Shane.
PS for some understanding of code optimization in LV, check out the past coding challenges. They're a gold mine of speed optimizations.....
I don't feel hurt personally, it's simply a matter of expressing opinions. Your opinion is valid (for yourself) as is everyone else's (for themselves). As such there's no overlap, and also no reason to feel hurt.
I didn't intend for my last post to be interpreted as me being
annoyed. I'm not. It was meant as a simple statement of
fact.I don't have the "show buffer allocation" tool, because I'm working with LV 6.1. There are some rules to wiring large data sets which can greatly avoid memory overhead. When working with large arrays and basically just reading values, even from sub-sets of the original array (without modifying the array) make sure to wire the array through the structure or sub-vi you're doing the work in. This will actually AVOID copies. It seems counter-intuitive because you're passing the array to a sub-routine (which kind of suggests more copying, not less) but the LV compiler is "smart" enough to realise you're not chenging the array and passes it "Byref" instead of "Byval". At least that's my understanding, but I don't have a formal programmer training, so I may be wrong.
LV is a different programming language (and indeed paradigm) so it DOES take time to learn the subtelties. I can also understand that 10 copies of a 10MB array doesn't seem like a subtelty when it happens unexpectedly, but there's always a way to avoid it. This is another reason why everyone says local and global variables are bad. Each one generates a copy......
I don't take exception with your programming skill, quite the contrary. If I think back at what I did with LV when I started I shudder and a shiver runs down my spine. What I did take exception with (on a factual level, not a personal one) was your damnation of LV due to something which CAN be avoided when you know how.
I don't think your post is "polluting" anything. It's important to have different views, but it's also important to be willing to learn something instead of quickly blaming something as being faulty. A quick question as to why LV creates so many copies instead of claiming it simply "automatically" creates copied would have generated a totally different response, and would have most likely lead to several people taking time to explain things to you. In this way, everyone wins.
On a side note, I don't accept apologies where they're simply not neccessary. Don't worry. I don't fly off the handle quite that easily.
Shane.
PS for some understanding of code optimization in LV, check out the past coding challenges. They're a gold mine of speed optimizations.....
Message Edited by shoneill on 09-09-2005 03:12 PM
Message Edited by shoneill on 09-09-2005 03:14 PM
