Good handling of persistent data and related issues is Muq's greatest single strength, and future releases will continue to focus upon this.
Improvements which I expect to introduce roughly in the year 2000-2001 timeframe include:
.muqfiles into memory. This will speed db open and close (particularly of uncompressed dbs) and somewhat speed up disk I/O on large objects, but primarily it will enable the following.
.muqfiles. This will allow high-bandwidth communication with a variety of helper applications, such as lapack operations and sound, still and video I/O and transformations via large shared arrays.
.dbfiles, in particular large, static read-only
.dbfiles. This would be an appropriate way of making large datasets such as MRI voxel datasets, gene sequence data, image libraries and such available to softcode without having to actually copy them into the master
.muqfile and duplicate their contents at each backup of the
In a slightly longer timeframe, it would be good to investigate input journalling, so as to be able to back up and reproduce a run exactly -- very handy for debugging, among other things.
Go to the first, previous, next, last section, table of contents.