Last updated: 20080311
effort at the moment is being directed to putting the MFL language support into its own library with its own API. I believe this will allow development to be better focused on individual components as needed (e.g. a specific application or the MFL library) without impacting other components as much as when the MFL support is intertwined, code-wise, with other things in the package. The MFL component will become a separately downloaded and compiled library (much like mml). The mfl-ectomy is a bit complicated; I made one pass at it late last year but started again. The end is getting nearer; I am anxious to get this behind me so that I can focus on some pressing improvements in the mvmda and mvmtr applications.