Poly/ML August 2013

polyml@lists.polyml.org

11 participants
9 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

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

Compiler in SVN
by David.Matthews＠prolingua.co.uk 03 Sep '13

03 Sep '13

There's been quite a lot of work on the intermediate code optimiser since the last release and it's largely been rewritten. The main aim has been to reduce the number of cases where heap storage was allocated for argument tuples or closures. There were a number of bugs that appeared during testing but I'm not aware of anything outstanding. Isabelle2013 and HOL4 both seem to build successfully and there does seem to be some speed-up. I'd like to release this version in the next month or so but I'd like to fix any other bugs that have been introduced. Please try out the SVN version and let me know how it goes. Don't forget that after the configure and make steps you need to run "make compiler" at least once and preferably twice. Otherwise you will still be using the 5.5 compiler. David

6 16

pretty printing infrastructure
by Michael.Norrish＠nicta.com.au 28 Aug '13

28 Aug '13

First a feature request: could we please have a version of the basic function for adding a string that takes an optional argument indicating how wide the Oppen algorithm should treat the string? At the moment, the infrastructure just seems to count the bytes emitted, and this causes premature line breaks if I'm emitting UTF-8 characters. Of course, if the infrastructure could magically become aware of UTF-8 or wide characters that would solve this particular use-case, but I'd still ask for this feature because I also want to emit byte-sequences that are terminal control codes. (On appropriate terminals, I emit vt100 codes to colour certain substrings, for example.) Secondly, I'm a bit concerned that the new, recommended approach to pretty-printing requires me to translate into the Pretty structure before anything happens. I'd feel more comfortable if the structure could be produced and consumed lazily so that I don't end up with a large (strictly unnecessary) Pretty structure in memory. Michael ________________________________ The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

3 10

call Poly/ML from not native Poly/ML threads
by pob_001＠mail.ru 15 Aug '13

15 Aug '13

Hi, Please forgive me for troubling you but I have a small question. Whether it is possible to make callback from C to PolyML from threads that not created by Poly/ML ? Thanks, Dmitry

4 11

Printing of function types
by rda＠lemma-one.com 12 Aug '13

12 Aug '13

Poly/ML seems to be a little inconsistent about when it uses type names supplied by the user to abbreviate types as shown in the following transcript: > type COMPLEX = {re : real, im : real}; type COMPLEX = {im: real, re: real} > val unity : COMPLEX = {re = 1.0, im = 0.0}; val unity = {im = 0.0, re = 1.0}: COMPLEX > fun negate ({re, im} : COMPLEX) : COMPLEX = {re = ~re, im = ~im}; val negate = fn: COMPLEX -> {im: real, re: real} Regards, Rob.

3 2

Linking exported object files
by David.Matthews＠prolingua.co.uk 02 Aug '13

02 Aug '13

I've updated the "polyc" script so that as well as accepting an ML source file to compile and link it can also be used to link object files created with PolyML.export. Switching to static linking by default in SVN has turned up a few problems. In particular it seems that it's important to include the libraries required by libpolyml. The problem is that this can depend on how it was built. In particular, the configure script will use GMP if it is present but falls back to the internal arbitrary precision package if it is not. That has the effect that if GMP was detected during the build process then the linking line must include -lgmp. However, if GMP is not present then including -lgmp will result in an error message. This makes it rather difficult to write a general purpose linking script. The linking line found at http://www.polyml.org/FAQ.html#standalone has gone through several versions and still has to be tweaked. It should now just require polyc -o hello hello.o Although "polyc" is a shell script it is produced during the build process and includes the appropriate options for linking depending on what the configure script found. The name "polyc" was meant to be analogous to "cc" or "gcc". I don't know whether it might be better to use the name "poly" for both the "batch" and interactive versions depending on the options. Any ideas? David

2 2

Linking exported object files
by David.Matthews＠prolingua.co.uk 01 Aug '13

01 Aug '13

On 01/08/2013 16:23, Rob Arthan wrote: > > On 1 Aug 2013, at 16:07, David Matthews wrote: >> ... In particular, the configure script will use GMP if it is >> present but falls back to the internal arbitrary precision package >> if it is not. That has the effect that if GMP was detected during >> the build process then the linking line must include -lgmp. >> However, if GMP is not present then including -lgmp will result in >> an error message. > > What are the advantages in building with GMP? If you are working with large arbitrary precision values particularly multiplying and dividing GMP is likely to be significantly faster. The default code is fairly naive. It's unlikely to make any difference for values that are only slightly longer than short precision (31-bits on 32-bit; 63-bits on 64-bit) and doesn't affect arithmetic on short precision values. Regards, David

1 0

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 August 2013