I've been reading in a few places about this, and have noticed there are a few misinterpreted items from the implementation of the new embedded FMC. The vasFMC embedding was done for the CRJ. While the core of vasFMC and this small tidbit of code is/will be public domain, the CRJ is still unique in it's FMC functionality to the true aircraft. I have read in various places that some assume the FMC provided with the CRJ will simply be a straight shoot of the vasFMC as it stands (which is based on the Airbus FMC). Such is not truly the case, and, of course, such code and other information used to make the FMC unique will not be shared with the public. So, while vasFMC certainly will become an option to many developers, it's not going to be a simple swap process, and aside from that fact, if left at default functionality it will not be true to the aircraft without the developers' hard work to alter the information and how it's passed around into the FMC itself. You'll need to get comfy with C.