Poly/ML January 2014

polyml@lists.polyml.org

5 participants
8 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

polyc and poly --script
by rene.neumann＠in.tum.de 24 Mar '15

24 Mar '15

Hi, two completely orthogonal questions/remarks for PolyML 5.5.1: 1.) When building PolyML with '--with-system-libffi' the '-lffi' part is missing in the linker line in polyc. 2.) Is it somehow possible to see if an ML file is run via 'poly --script' or as a standalone executable? Because for the one the logic has to be wrapped in 'fun main ()', and for the other it should not :). (Ie, what I want: if is_script then main() else () ) Thanks, Ren? -- Ren? Neumann Institut f?r Informatik (I7) Technische Universit?t M?nchen Boltzmannstr. 3 85748 Garching b. M?nchen Tel: +49-89-289-17232 Office: MI 03.11.055

4 9

[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

Isabelle/ML IDE
by makarius＠sketis.net 29 Sep '14

29 Sep '14

Dear friends of Poly/ML, or Standard ML in general, Isabelle2013-2 is now available from the usual mirror sites: Cambridge (UK) http://www.cl.cam.ac.uk/research/hvg/Isabelle/ Munich (Germany) http://isabelle.in.tum.de/ Sydney (Australia) http://mirror.cse.unsw.edu.au/pub/isabelle/ It is mainly an environment for interactive and automated theorem proving, but the integration of Isabelle/ML into the Prover IDE makes it suitable for general Standard ML development (potentially in teaching scenarios). After downloading / unpacking / running the main application of Isabelle/jEdit, the Documentation panel on the right-hand side gives quick access to Examples, notably src/HOL/ex/ML.thy for some Isabelle/ML basics. The manual on Isabelle/jEdit in the same panel provides further details on the IDE, which is based on the jEdit text editor. Makarius

1 1

Incorrect floating point conversion
by fw＠deneb.enyo.de 24 Mar '14

24 Mar '14

I noticed this: Poly/ML 5.5.1 Development > val a = 0.99999999999999972244424384371086489409208297729492187;; val a = 1.0: real > val b = 0.999999999999999722444243843710864894092082977294921876;; val b = 1.0: real > a < b;; val it = false: bool > a > b;; val it = false: bool So both values are equal according to Poly/ML. But the correct conversion for the first one is (in hexadecimal floating point notation) 0x1.ffffffffffffdp-1, and for the second 0x1.ffffffffffffep-1, so the values should be different.

4 4

PolyML.pointerEq
by Brian.Campbell＠ed.ac.uk 05 Feb '14

05 Feb '14

What semantics, if any, does PolyML.pointerEq have? In particular, is it supposed to be guaranteed that if pointerEq (x,y) is true, then it will remain true after GC? My reason for asking is that I've been having trouble with assertion failures in HOL when reducing large terms. The assertions check that the left hand side of the conclusions of two theorem objects are equal according to pointerEq, because this allows a fast comparison that "should" always be true if the theorem is manipulated carefully. I'm fairly certain the assertion failures are related to GC: they are non-deterministic on code that ought to be deterministic, and vary in frequency across different machines. (I haven't seen it at all on a 4GB 32-bit machine, rarely on 4GB 64-bit, often on the 8GB I normally use and infrequently on a compute server with much more.) There's no sign of any data corruption, however. Brian

3 4

checking --enable-shared from within the REPL
by David.Matthews＠prolingua.co.uk 14 Jan '14

14 Jan '14

On 13/01/2014 22:31, Michael Norrish wrote: > I'll look at the relevant lib directories; thanks. > > The reason is that the HOL build process wants to create executables (for > mlyacc, mllex and others), and doing so without --enable-shared will fail > mysteriously. If I can cut this off at the pass, I can provide better error > messages. There was a problem that I discovered with making --disable-shared the default that I hadn't anticipated. It seems that when linking with the static library it is necessary to include some extra libraries (e.g. gmp) that are used within libpolyml. These don't seem to be needed when linking with the dynamic library so presumably they have already been linked into the dynamic library. > I confess I haven't properly looked at polyc; would this give us a uniform approach? That is the intention. "polyc" is written as part of the process of building "poly" and should include all the libraries that are needed. Regards, David

1 0

checking --enable-shared from within the REPL
by michael.norrish＠nicta.com.au 13 Jan '14

13 Jan '14

Is there any way to detect if the system has been built with --enable-shared? Something in the PolyML structure (say)? I'd like to be able to have my build script abort if the PolyML hasn't been built correctly. Or is there anything obvious my script could check in the file system to make this determination? Thanks, Michael

3 2

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 January 2014