Rob Arthan wrote:
On Monday 23 Oct 2006 11:49 am, David Matthews wrote:
This comes at one significant cost: the persistent store system that has been a feature of Poly/ML almost since the beginning has been removed.
One advantage of the persistent object store is that it is organised as a hierarchy: if many people want to share a body of ML code and data, the common material can be put in one database and the individuals can work in descendants of that database. At least one group of ProofPower users have large applications that are only feasible when organised in this way. Is anything like this possible under the new set-up?
Rob, I did wonder about this but I felt that on balance the advantages outweighed the drawbacks. The new version does mean that every image, the equivalent of a database in the old version, has to contain everything that is in the hierarchy but the only effect is that this requires more disc space than it used to. Given that the maximum size of all the databases in a chain from child to root parent was 400Mbytes and hard discs routinely come in the hundreds of gigabytes I find it hard to believe that this duplication would be a problem. What exactly do you mean by "only feasible"? What is the constraint?
Regards, David.