Poly/ML February 2012

polyml@lists.polyml.org

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

Lifespan of pointers to callback functions passed via C FFI
by phil.clayton＠lineone.net 13 Aug '12

13 Aug '12

I have been assuming that the pointer back to an ML function passed to a foreign C function will still be valid after the C function has returned, so the callback can occur sometime later (from a different C function). Is that a valid assumption? I made this assumption based on some tests in which one such callback pointer remained valid for the life of the application. It would be nice to know I wasn't just being (un)lucky! Phil

2 5

Calling C functions
by phil.clayton＠lineone.net 15 Feb '12

15 Feb '12

I thought it could be useful to mention the approach that I have been taking for calling C functions. In particular, it avoids the need to have a family of callN functions. For example, instead of writing call2 (load_sym lib "sum") (DOUBLE, DOUBLE) DOUBLE operators --> and &&> are used to construct function specifications that are given to a single call function: call (load_sym lib "sum") (DOUBLE &&> DOUBLE --> DOUBLE) The resulting function takes nested pair arguments rather than an n-tuple, so we would give the argument e.g. (x & y), where & is an infixr constructor for a pair type, rather than (x, y). See example 1 in attached. I didn't extend this scheme for passing parameters by reference because that was easily dealt with elsewhere (still avoiding the family of callNretX functions): in my approach, each C function binding has two levels: a low-level as above and a high-level wrapper that is introduced for - converting between abstract types and concrete C types - controlling ownership of C allocated memory These high level wrappers can also perform the required address/deref operations for passing parameters by reference. At the lower-level, parameters passed by reference are just pointers: val swap_ = call (get_sym lib "swap") (POINTER &&> POINTER --> VOID); Then this is wrapped, using operators ---> and &&&>, as follows: val swap = (withRef INT &&&> withRef INT ---> I) swap_; The resulting function takes/returns nested pair arguments, so we could write e.g. val x & y & () = swap (2 & 3) See example 2 in attached. For the attached examples, the C library shared object is built with 'make bin'. Don't forget to include the example directory in LD_LIBRARY_PATH when invoking poly. Phil P.S. The same high-level binding wrappers can be used for both Poly/ML and MLton by creating a common interface, so reducing compiler specific code.

1 0

Overloaded operators for Time.time
by phil.clayton＠lineone.net 06 Feb '12

06 Feb '12

It appears that Poly/ML overloads operators + - < <= >= > for Time.time but they shouldn't be, according to the Basis Library. http://www.standardml.org/Basis/top-level-chapter.html#section:3 Perhaps they were overloaded once upon a Time.time... Phil

5 8

Add --error-exit option
by fw＠deneb.enyo.de 02 Feb '12

02 Feb '12

The patch below adds an --error-exit option and uses it in the makefile. This avoids replacing the compiler with something that doesn't work at all due to compilation errors. diff --git a/Makefile.am b/Makefile.am index af5853d..51372ad 100644 --- a/Makefile.am +++ b/Makefile.am @@ -104,7 +104,7 @@ polytemp.txt: $(POLYIMPORT) # This builds the compiler but does not update the files in the imports directory. # It then builds a version of poly containing the new compiler. compiler: all - ./poly $(BOOTSTRAP_OPTIONS) < mlsource/BuildExport.sml + ./poly $(BOOTSTRAP_OPTIONS) --error-exit < mlsource/BuildExport.sml $(MAKE) reboot: compiler diff --git a/basis/FinalPolyML.sml b/basis/FinalPolyML.sml index 0480aba..651f573 100644 --- a/basis/FinalPolyML.sml +++ b/basis/FinalPolyML.sml @@ -250,6 +250,8 @@ local if ! useMarkupInOutput then prettyPrintWithIDEMarkup(stream, lineWidth) else PolyML.prettyPrint(stream, lineWidth) + val exitOnError = ref false + (* Top-level prompts. *) val prompt1 = ref "> " and prompt2 = ref "# "; @@ -706,7 +708,10 @@ local fun handledLoop () : unit = ( (* Process a single top-level command. *) - readEvalPrint() handle _ => (); + readEvalPrint() handle _ => + if !exitOnError + then OS.Process.exit OS.Process.failure + else (); (* Exit if we've seen end-of-file or we're in the debugger and we've run "continue". *) if !endOfFile orelse exitLoop() then () @@ -873,6 +878,7 @@ local (* Generate mark-up in IDE code when printing if the option has been given on the command line. *) useMarkupInOutput := List.exists(fn s => s = "--with-markup") (CommandLine.arguments()); + exitOnError := List.exists(fn s => s = "--error-exit") (CommandLine.arguments()); topLevel false (globalNameSpace, fn _ => false) ) end diff --git a/basis/TopLevelPolyML.sml b/basis/TopLevelPolyML.sml index 405d5ae..0a18243 100644 --- a/basis/TopLevelPolyML.sml +++ b/basis/TopLevelPolyML.sml @@ -1121,6 +1121,7 @@ in print "--help Print this message and exit\n"; print "-q Suppress the start-up message\n"; print "--use FILE Executes 'use \"FILE\";' before the ML shell starts\n"; + print "--error-exit Exit shell on unhandled exception\n"; print "--with-markup Include extra mark-up information when printing\n"; print "--ideprotocol Run the IDE communications protocol\n"; print "\nRun time system arguments:\n";

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 February 2012