Poly/ML December 2011

polyml@lists.polyml.org

2 participants
4 discussions

Inspecting structures
by ramana.kumar＠gmail.com 27 Jan '16

27 Jan '16

Is there a way to look at the contents (i.e. signature) of a structure without opening it? (I suppose you could just open it then call a lot of PolyML.Compiler.forgetXXX, but that's quite tedious) Also, is it possible to retrieve the long path of an identifier in scope? Something that will, for example, take the rev in scope and say that it came from List. Finally, what about searching for an identifier that would come into scope if you opened some structures?

3 5

[Fwd: Re: [polyml] Building Poly/ML on MacOS X 10.6]
by rda＠lemma-one.com 29 Dec '14

29 Dec '14

I wrote: > I am completely baffled. I thought I hada solved all my problems on > MacOS X > 10.6 and was just tidying up, when I had to recompile a 32 bit > version of > Poly/ML to test a tidied up make file. This failed because > PolyML.Compiler.printTypesWithStructureName no longer exists. The same > problem happened when i rebuild a 64 bit version. What has happened? but it was a false alarm: my make file was wrong for other reasons and the absence of PolyML.Compiler.printTypesWithStructureName was not relevant. No doubt there are good reasons why this variable has been withdrawn. Regards, Rob.

3 6

Sourceforge tracker
by phil.clayton＠lineone.net 13 Dec '11

13 Dec '11

David, I have started adding minor issues to the Sourceforge tracker, rather than bother the mailing list with mundane matters. I hope that is all right. Phil

2 1

Null pointer and comparing CInterface.vol values
by phil.clayton＠lineone.net 02 Dec '11

02 Dec '11

I am currently implementing type t val null : t val isNull : t -> bool where type t = CInterface.vol. There is no problem doing this but I wondered whether I could improve the CInterface structure to avoid annoying little C library functions. Would it be at all controversial to include null : vol in CInterface? Regarding comparison of vols, it makes sense that vol is not an eqtype because it stores more than just the "raw vol". Generally, is it safe to compare vols using their "raw vols"? I.e. could garbage collection or data sharing cause the raw vols to become invalid? Even if the raw vols were valid but changed behind the scenes, such comparisons may be of dubious value if the result could change due to garbage collection or data sharing. If vol comparison is reliable, would it be useful to have an eq or compare function in CInterface? Otherwise, could CInterface include isNull : vol -> bool ? I am happy to have a go at a patch is this sounds useful. Phil

5 32

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Poly/ML December 2011