Poly/ML December 2012

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 and SVN
by David.Matthews＠prolingua.co.uk 24 Jun '13

24 Jun '13

I have "upgraded" the Poly/ML site on SourceForge (there didn't seem to be any choice) and as a consequence the subversion site has changed. Anyone who is following Poly/ML SVN will need to change to the new site. For trunk this is svn checkout svn://svn.code.sf.net/p/polyml/code/trunk polyml and for the 5.5 fixes branch svn co svn://svn.code.sf.net/p/polyml/code/fixes-5.5 polyml I am currently working on the stages of the compiler that process and optimise the intermediate code. These are parts of the compiler that haven't been looked at for a very long time and some of it was obviously translated automatically from my original Poly code back in the 1980s. I tend to commit changes fairly regularly rather than accumulate a long set of changes and commit all at once. This does mean that things could be broken and only fixed by a later commit but it makes it much easier to find a bug if it shows up much later. Season's greetings and best wishes for the New Year, David

3 5

Unable to build fixes-5.5 debian style
by itz＠buug.org 28 Dec '12

28 Dec '12

For some time now, Debian tries to build all binaries with some "hardening" flags. This includes the -pie linker flag, which forces building of position-independent binaries. But I cannot build the current tip of the fixes-5.5 branch this way. At the point where poly reads the portable export, I get: ./poly -H 50 --error-exit < mlsource/BuildExport.sml lt-poly: memmgr.cpp:915: void MemMgr::AddTreeRange(SpaceTree**, MemSpace*, uintptr_t, uintptr_t): Assertion `t->tree[r] == 0' failed. /bin/bash: line 1: 14570 Aborted ./poly -H 50 --error-exit < mlsource/BuildExport.sml make[2]: *** [compiler] Error 134 make[2]: Leaving directory `/tmp/polyml-fixes/polyml' Attached is the build log both _with_ (bad) and _without_ (good) the -pie flag. I suspect that the successful build without -pie is an accident, ie. an uninitialized location is being read and it just happens to be 0 in this case. Arch amd-64, gcc/g++ 4.7.2 -- Ian Zimmerman gpg public key: 1024D/C6FF61AD fingerprint: 66DC D68F 5C1B 4D71 2EE5 BD03 8A00 786C C6FF 61AD http://www.gravatar.com/avatar/c66875cda51109f76c6312f4d4743d1e.png Rule 420: All persons more than eight miles high to leave the court.

2 1

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 2012