Are there any reasons not to define an eval function that is just like PolyML.use but reads from a string instead of a file? I've done it and it seems to work okay, but I'm wondering whether it was purposefully omitted from the PolyML structure (or maybe it is there and I haven't seen it). (I would use such a function instead of writing a string out to a temporary file and use-ing that file back in.)
I don't think it was a deliberate omission. It's easy to write in terms of PolyML.compiler so maybe it was just that there wasn't much demand for it. If you want to send me your code I'll have a look at it and see if it should be included.
Regards, David
Ramana Kumar wrote:
Are there any reasons not to define an eval function that is just like PolyML.use but reads from a string instead of a file? I've done it and it seems to work okay, but I'm wondering whether it was purposefully omitted from the PolyML structure (or maybe it is there and I haven't seen it). (I would use such a function instead of writing a string out to a temporary file and use-ing that file back in.) _______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml