2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

List overview
Download

Poly/ML March 2005

polyml@lists.polyml.org

3 participants
5 discussions

Start a nNew thread

Seg. fault
by m.a.ellis＠ncl.ac.uk 14 Apr '05

14 Apr '05

FYI, Lest anyone be planning an upgrade, I get segmentation faults on PolyML startup using Linux 2.6.9 (using PolyML as distributed with Isabelle). Maybe it's just me though. 2.6.8.1 seems fine though. Martin

6 9

Spontaneous corruption of PolyML 4.13 Database on WinXP
by byron.hale＠einfo.com 19 Mar '05

19 Mar '05

Hi, I'm sorry to report this, but the database on PolyML 4.13, Win XP, has saved state when I have studiously avoided doing so. Suggestions? Thanks, Byron Hale

1 0

Recursive type definitions resolved well enough for me.
by byron.hale＠einfo.com 19 Mar '05

19 Mar '05

Thanks to WIlliam Lovas, I have a reasonable answer for the errors I was getting and what might be done about them. SMLNJ seemed to handle errors more consistently than PolyML, but once there is a syntactic error, error handling is problematic anyway. Byron Hale

1 0

Interpreted Version of PolyML 4.1.3
by brucker＠spamfence.net 18 Mar '05

18 Mar '05

Hi, while trying to build an interpreted PolyML system based on version 4.1.3 (version 4.0 works fine) I'm getting linker errors, e.g.: /tmp/driver/improve.c:724: undefined reference to `MD_update_code_addresses' Any hints? Achim

2 2

Problem with datatype definition
by byron.hale＠einfo.com 18 Mar '05

18 Mar '05

Hi, I have a situation where a recursive datatype has a number of declarations, including type constructors. Yet when I try to use those same constructors for further declaration within the datatype, the compiler does not recognize them. Yet top-level recognizes them. I am using PolyML for a rapid prototyping environment. I suspect a problem with PolyML 4.13, but probably I have blundered. Below is a snippet of the code which displays the behavior, which is also shown. The compiler does not have a problem with "NUM," but has problems with "LBRACKET" and "LBRACKET," when declaring type "lbr_num_rbr_o." Note that top-level recognizes the constructors in question, after the compiler fails. I always start the compiler fresh after each error. Best Regards, Byron Simplified code: datatype type_specifierK = INT | VOID and relopK = LE | LT | GT | GE | EQ | NE and addopK = PLUS | MINUS and mulopK = TIMES | OVER and arithopK = addopK | mulopK and tokenK = ENDFILE | ERROR | ELSE | IF | RETURN | WHILE | ID | NUM | ASSIGN | SEMI | COMMA | LPAREN | RPAREN | LBRACKET | RBRACKET | LCURLY | RCURLY | arithopK | relopK | type_specifierK withtype lbr_num_rbr_o = (LBRACKET * NUM * RBRACKET) option ; Upon loading the above into PolyML 4.13, the following results are obtained: > datatype type_specifierK = INT | VOID and relopK = LE | LT |GT | GE | EQ | NE and addopK = PLUS | MINUS and mulopK = TIMES | OVER and arithopK = addopK | mulopK and tokenK = ENDFILE | ERROR | ELSE | IF | RETURN | WHILE | ID | NUM | ASSIGN | SEMI | COMMA | LPAREN | RPAREN | LBRACKET | RBRACKET | LCURLY |RCURLY | arithopK | relopK| type_specifierK withtype lbr_num_rbr_o = (LBRACKET * NUM * RBRACKET) option ; # # # # # # # # # # # Error: Type constructor (RBRACKET) has not been declared Found near datatype type_specifierK = INT | VOID and relopK = LE | LT | GT | ... and addopK = PLUS | MINUS and mulopK = TIMES | ... and arithopK = ... and ... withtype lbr_num_rbr_o = (LBRACKET * NUM * RBRACKET) option Error: Type constructor (LBRACKET) has not been declared Found near datatype type_specifierK = INT | VOID and relopK = LE | LT | GT | ... and addopK = PLUS | MINUS and mulopK = TIMES | ... and arithopK = ... and ... withtype lbr_num_rbr_o = (LBRACKET * NUM * RBRACKET) option Static errors (pass2) > > ; > NUM; val it = NUM : tokenK > LBRACKET; val it = LBRACKET : tokenK > RBRACKET; val it = RBRACKET : tokenK > Please let me know your conclusions. Thanks, Byron Hale

2 1