Introducing LabVIEW 2009

[Intaris]

I've been looking around for an affordable 2X AMD Istanbul 6-core (12-core in total) machine for testing and code optimisation.  Now we have 64-bit support (Last version already?) I can go mad on memory too...

Anyone know where to get one which isn't prohibitively expensive?  I see the 6-Core is only planned to hit the "mainstream" market in 2011..... 😞

I know it's off-topic but LV is getting so good at the multicore thing, it's actually an effort to keep up with the hardware.  I think that's a good thing, right?

Shane.

Message Edited by Intaris on 08-01-2009 01:52 AM

[tst]

---

Intaris wrote:

LVOOP with References.  Oh man, I can't wait.

---

You should note that this does NOT currently integrate into the IDE and LVOOP.

That means that you can pass an object by-ref (just like you could using a queue), but you can't create class methods in the IDE which would operate by-ref. That means that you either have to deref the object yourself before each operation (or series of operations) or that you will have to write wrappers for each method which you want to be by-ref.

At least until someone writes something which will automate it.

[tst]

---

Pnt wrote:

This time we will not install the Code capture tool....

---

You're assuming the CCT will not support this feature. Having used it in the beta, I can say the CCT still has some advantages in usability over it, and if it will support it, well...

[Intaris]

I realise that the class needs a data reference in its member data (So the class is technically still by value), but the coolness sisn't really affected too much bay that.  It allows for some cool new approaches.

Shane.

[tst]

---

Intaris wrote:

I realise that the class needs a data reference in its member data

---

Actually, the basic concept for usage is the other way around (since you want a reference to a cluster, which means a class) - you need to move the instance you want around using references and the IDE doesn't currently help you make it easier for classes. Essentially, you could have done the same thing until now using a single-element queue. I'm not sure you would also have gotten the performance you want, but the functionality would be there.

The reference feature has the same disadvantages as the queue method (e.g. the ability to easily create deadlocks) but also some advantages (e.g. to create a deadlock you would have to bring the reference wire over the IPE structure border, which makes it more noticable that you're doing this).

[muks]

---

Drag image onto your diagram and they run!

---

Whattttt? I mean how? I mean Kewl.........

[Intaris]

"the basic concept for usage is the other way around"

I've never really paid much intention to basic concepts.  😮 I would try to make the "reference" part of the class transparent to the programmer by encasing it in a class (Essentially creating a class clone if you will).  That way By-ref and By-val versions of the same class would be interchangeable in code.

Shane.

[Coq_Rouge]

---

Darin.K wrote:

Recursion!  Yes!  I have wanted this for more than 15 years.  BTW what is wrong with calling it LV9.0?  My first thought when I hear software with the year in the name is a certain OS company, and the associations aren't always good.

---

Well perhaps some smart people in the marketing department want to remember us about the fact that we are using an old labview version;). Many people still use labview 7.1 or older version today. So a splash screen telling you the fact that you are still using Labview 2000 in 2009( as an example), will at some point bother you so much. That you at some point order a new Labview 2009 copy. Or maybe not  

[tst]

---

Intaris wrote:

I would try to make the "reference" part of the class transparent to the programmer by ... Essentially creating a class clone

---

Exactly, meaning you have to do duplicate work manually (the wrapper-for-each-method problem). Not the most elegant solution and certainly not convenient for the class developer. That's what I meant by "not currently integrated into LVOOP".

[Intaris]

---

Coq Rouge wrote:

---

Well perhaps some smart people in the marketing department want to remember us about the fact that we are using an old labview version;). Many people still use labview 7.1 or older version today. So a splash screen telling you the fact that you are still using Labview 2000 in 2009( as an example), will at some point bother you so much. That you at some point order a new Labview 2009 copy. Or maybe not  

---

I still have a PC with MS Office 2000 installed.  IMHO the best version they brought out.

Shane.

Message Edited by Intaris on 08-02-2009 10:14 AM