Hi David,
On 30/10/15 23:35, David Matthews wrote:
I don't like the idea of changing the existing behaviour but there may
be other alternatives. Something that occurs to me would be to provide
a function to load a complete hierarchy, say
PolyML.SaveState.loadHierarchy: string list -> unit
Then PolyML.SaveState.loadHierarchy["grandparent", "parent", "child"]
would load a set of files. Each file currently has a signature for the
parent as well as a path and these are checked in case a parent has
changed so the only difference would be that the paths to all the files
would be provided from ML.
That sounds good as well. Then the path calculation could be implemented
using showParent.
Japheth
________________________________
The information in this e-mail may be confidential and subject to legal
professional privilege and/or copyright. National ICT Australia Limited accepts
no liability for any damage caused by this email or its attachments.
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
