LV2012 compatible version

[komorbela]

Hi All,

I have been trying to figure out how to use the Actor framework recently, and have seen that there was much change in the framework between the versions. I am really amazed by this framework, and definitely want to use it. By the way I am afraid that the version possibly coming out with LV 2012 will be not compatibe with the 3.* version. If it's the case, could we get the latest version in advance?

I wanted to follow the LV 2012 beta, but it seems to be too late for that

[AristosQueue (NI) · Accepted solution]

The 3.x versions install into user.lib.

The new (4.x) version installs into vi.lib.

This means that any program you write against the existing version can continue to work in 2012 even though there will be another version of the Actor Framework.

Yes, we are breaking compatibility (again) between the 3.x and the 4.x version of the framework.  I will not be making the revised version available prior to the 2012 release in August except to those who picked it up through the Beta. The revised AF is going to be a draw for upgrades for LV 2012, and I'm not going to undermine that. It's not even really my call to make any more, anyway... it's not an independent library any more... part of the price to be paid for becoming part of the official supported library.

So, even though the two libraries are not compatible with each other, the old library is compatible with LV 2012, and when you get LV 2012, if you want to convert over to the new library, it can be done (annoying as heck, as I just did it today for one application, but it can be done).

[komorbela]

Thanks for the fast reply!

I get your point and understand it. It's a little unfortunate that I have to wait until August, as I am about to start a project right now, and cannot wait until August. I hope converting to the new library will not be too much pain.

Anyways, thanx again for the fast and clear reply!

[David_Staab]

Considering that AQ just said it was annoying for him to do the conversion, I think I'm going to distribute v3.0.7 alongside any of my AF-based components as a dependency and avoid the upgrade unless it's critically necessary.