On 2013-03-12, at 10:17, Sven Van Caekenberghe <sven@stfx.eu> wrote:
Camillo,
On 12 Mar 2013, at 09:39, Camillo Bruni <camillobruni@gmail.com> wrote:
from that point of view, it is just a warning. Unless you do some fancy new FileSystem stuff it will continue to work with 2.0 and for a while with 3.0.
Is it not possible to clarify *exactly* what is missing and will not work well.
Right now this is like a mystery.
We are all developers and capable of understanding a technical explanation ;-)
Which primitives are we talking about, how are they used and what end user effect do they have ?
I know that NativeBoost is an important difference. The question is, will the image start without proper NB support and will something be broken if NB is non-functional (apart from NB code itself, I mean high level normal stuff) ?
Well so far there is only some FileSystem primitives, and besides the tests nobody ever relied on getting the permissions or checks if a file is an symlink. But we can do that now. NativeBoost is shipped with 2.0 but not yet used in the Kernel, but this is going to change in 3.0 where we hope to rewrite the UI driver talking to Cairo using an NativeBoost-FFI binding. The thing is, I don't want to care and define which external VMs work with which Pharo version. (Still, yes you can run Pharo 20 on CogVM, we just don't like it :P ) Pharo ships and runs only with the Pharo and the PharoS VM. Currently the situation is not perfect with our VMs being unstable