Poly/ML

polyml@lists.polyml.org

695 discussions

Poly/ML and SML/NJ warn inconsistently about using op for an infix constructor
by phil.clayton＠lineone.net 04 Apr '12

04 Apr '12

For example, given infix & datatype t = & Poly/ML (5.4) reports: Warning-(&) has infix status but was not preceded by op. So Poly/ML seems to prefer the use of 'op' in a datatype declaration. However, if 'op' is present, i.e. datatype t = op & SML/NJ (110.73) reports: stdIn:2.14-2.16 Warning: unnecessary `op' Generally, it is a good principle to avoid warnings but, in this particular respect, that isn't possible for code that is shared between Poly/ML and SML/NJ. Note that MLton (20100608) doesn't warn either way. Does the Standard provide any guidance about the use of op here? Can anything be done to align the warnings from Poly/ML and SML/NJ in this respect? Thanks, Phil

4 9

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

Exception- Empty unexpectedly raised while compiling
by itz＠buug.org 29 Jan '12

29 Jan '12

Getting this one. WTH? Code is here: git@github.com:nobrowser/easylib.git just do 'use "load-all";' from the top level directory ... PolyML 5.4.1 (release), Linux i386 (32-bit), 2G RAM. -- Ian Zimmerman gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD Rule 420: All persons more than eight miles high to leave the court.

2 4

Exceptions and standalone executables
by itz＠buug.org 06 Jan '12

06 Jan '12

[17]matica:~$ poly Poly/ML 5.4.1 Release > fun main () = raise Domain ; val main = fn: unit -> 'a > PolyML.export ("foo", main); val it = (): unit [19]matica:~$ cc -o foo foo.o -lpolymain -lpolyml [20]matica:~$ ./foo [21]matica:~$ echo $? 0 I find this quite surprising, am I the only one? I know that I can easily work around it by including an exception catching wrapper in main, but it seems to me that wrapper should be in libpolymain .. -- Ian Zimmerman gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD Rule 420: All persons more than eight miles high to leave the court.

5 4

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

Y combinator crashes Poly/ML
by lhe＠it.uu.se 26 Nov '11

26 Nov '11

Hi, I have an implementation of the Y which crashes Poly/ML. Take the program below and evaluate "fact n" with n>3. I've tried it on both x86 and SPARC Solaris systems with Poly/ML 5.3, as well as on a (x86) MacOSX system with Poly/ML 5.4.1. The program works in both Moscow ML and SMLNJ, so I'm pretty sure it is correct SML. Best regards, Lars-Henrik Eriksson, PhD, Senior Lecturer Computing Science, Dept. of Information Technology, Uppsala University, Sweden E-mail: lhe(a)it.uu.se, Web: http://www.it.uu.se/katalog/lhe?lang=en Phone: +46 18 471 10 57, Mobile: +46 705-36 39 16, Fax: +46 18 51 19 25 -------- (* The Y combinator in ML *) abstype 'a ft = FT of 'a ft -> 'a with val Y = fn f => (fn (FT x) => (f (fn a => x (FT x) a))) (FT (fn (FT x) => (f (fn a => x (FT x) a)))) end (* Y is the fixed point operator, i.e. fix F = Y(F) *) (* Y has type (('a -> 'b) -> ('a -> 'b)) -> ('a -> 'b) *) (* Recursive definitions such as val rec f = ... can be written val f = Y (fn f => ...) *) fun Fact f n = if n = 0 then 1 else n * f(n-1) val fact = Y Fact

3 3

scanaddrs.cpp:107: Assertion Failed
by tjark.weber＠gmx.de 24 Nov '11

24 Nov '11

Hi, Poly/ML fixes-5.4 (revision 1373) just terminated with poly: scanaddrs.cpp:107: PolyWord ScanAddress::ScanStackAddress(PolyWord, StackObject*, bool): Assertion `val.IsDataPtr()' failed. on my machine (Linux 3.1.1-2.fc16.x86_64) while I was trying to build Isabelle/HOL. I am afraid the error is intermittent and has only occurred once so far. Is there anything I can do to provide more useful debugging information if this happens again? Kind regards, Tjark

2 2

← Newer
1
...
34
35
36
37
38
39
40
...
70
Older →

Jump to page:

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