
Hi, We're going to be making use of some new libraries shortly, which means these new libraries have to be downloaded for each machine that builds Yhc, so could everyone do a "scons depends". For information, we're going to be killing the Yhc general package, which contained a home-grown binary library and a tweaked play library - moving to the official Play library (now modified to support our hacks natively) and the official Binary library (much much faster, we hope). We are also updating to the filepath libary that will be in GHC 6.6.1. Once we've done that, we can move to making a proper Cabal package for Yhc.Core, with proper dependencies, making programs that depend on Yhc.Core much more deployable. When I do the work to move to the binary library, this will mean that the on disk Yhc.Core format will change. Not yet, but just a warning for people. I don't think this will have much of an impact to many people, but those who use Yhc.Core a lot will probably need to rebuild their libraries. I'll send out an email when this happens. Thanks Neil

Hi
When I do the work to move to the binary library, this will mean that the on disk Yhc.Core format will change.
Just to clarify, we currently have the abstract data type for Core, that will remain unchanged. We use DrIFT plus some horrible binary instances to automatically generate an on-disk format, which is a but yuk, and quite slow. We are going to move to Data.Binary, which will give us a documented, consistent, smaller and faster on-disk binary representation. If you use the Yhc.Core API you will not notice any changes. Thanks Neil
participants (1)
-
Neil Mitchell