Gpc November 1997

gpc@gnu.de

32 participants
113 discussions

BP string compatibility
by Frank Heckenbach 18 Nov '97

18 Nov '97

The African Chief wrote: > Problem: > Under BP, one can do; > Var S:String; > Count:Integer; > .... > Dec(S[0], Count); > > This does not compile under GPC, but "Dec(Length(S), Count)" > compiles, and seems to work okay. Then I think this is a bug in GPC, and must be prevented. The Length field of a string should only be accessible read-only. However, there is (in the current developer version, not yet in the last beta) a built-in function AssignLength which … [View More]

2 1

BP string compatibility
by The African Chief 18 Nov '97

18 Nov '97

Hi all Problem: Under BP, one can do; Var S:String; Count:Integer; .... Dec(S[0], Count); This does not compile under GPC, but "Dec(Length(S), Count)" compiles, and seems to work okay. Observation: This is an incompatbility b/w BP and GPC - probably because of the way strings are implemented under GPC. Questions: 1. Is GPC ever going to support the BP syntax "Dec(S[0], Count);" ? 2. Is it desirable to do so ? (obviously this would entail changes to the internal GPC string format ???) … [View More]

1 0

None
by Jim Brander 18 Nov '97

18 Nov '97

Further to the previous message about a problem with sets in the cygwin version. The following program causes the compiler to crash in construct_set. The crash does not occur if the set definition is directly in the program rather than imported. The crash occurs whether the interface is in the same or separate files. # 1 "/Orion/pas/creatvar.pas" module data1 interface; export data1_interface = (usage1); type usage1 = (sysusage,sysgen,syscopy,master); end. module creatvar; export … [View More]

1 0

Assign statements in GNU Pascal
by Badri Gomatam 18 Nov '97

18 Nov '97

Hello all: I am new to gnu pascal, so this is a newbie question: I have a _ton_ of code written ca. 1992/3 on Borland Pascal 5.0 which for various reasons I need to port to a Unix environment: the present version runs on DOS: I downloaded the binary for linux-(i386) and installed on my linux box..no problems (at least, not yet:) (i have gcc 2.7.2)...thinking "i'll just do gpc on these files and all will be OK "...:) when i compiled one of the (several hundred) files i have in my legacy code … [View More]

1 0

Re: undeclared identifiers
by Peter Gerwinski 17 Nov '97

17 Nov '97

Hi, Tom! Hi, all! According to Tom Dye: > > A while back I forwarded a bit of extended Pascal code that I thought > should compile with gpc, but doesn't. > [...] > I suspect that I have found something that gpc does not do correctly, ... Indeed, but I have posted a patch to `module.c' at this list on 10 November that fixes the problem (and causes some others which are fixed meanwhile in my development version;-). Your example modules work fine on my Linux box. > ..., but … [View More]

2 1

None
by chris＠bockermann.ping.de 17 Nov '97

17 Nov '97

Subject: Re: Dodgy email To: richard.kerry(a)quantel.com Date: Mon, 17 Nov 1997 15:14:18 +0100 (MET) From: "Christian Bockermann" <chris(a)bockermann.ping.de> Cc: gpc(a)hut.fi In-Reply-To: <80256552.00422CA2.00(a)buffer1.quantel.com> from "richard.kerry(a)quantel.com" at Nov 17, 97 12:08:55 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 826 Hello ! Richard.Kerry(a)Quantel.com … [View More]

1 0

Re: `case' statments: `default' and `others'
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Peter Wrote: According to richard.kerry(a)quantel.com: > [`begin/end' after `otherwise' ...] > [...] > Oh, and the lack of trailing colon is easier as that's the way Oregon has > it. Again, if it's optional it doesn't matter. Just to be sure that I have understood everything correctly: It is okay for you if we drop the colon after `otherwise' (i.e. forbid it) as long as we do not forbid a `begin/end' pair after `otherwise'? ------- That is correct. Oregon has no colon, and has '… [View More]

1 0

Dodgy email
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Does anyone recognize any of the names in the following extract : ------------------------- Could not deliver Message to ------------------------- CN=??r J Rodriguez/O=almenna kerfisfraedistofan@almenna kerfisfraedistofan User ??r J Rodriguez/almenna kerfisfraedistofan@almenna kerfisfraedistofan not ------------------------- I am getting this whenever I send a message to the mailing list. I am told that the names are not in the list explicitly. Does anyone have them in a sub-list ? Or … [View More]

1 0

Re: `case' statments: `default' and `others'
by Peter Gerwinski 17 Nov '97

17 Nov '97

According to richard.kerry(a)quantel.com: > [`begin/end' after `otherwise' ...] > [...] > Oh, and the lack of trailing colon is easier as that's the way Oregon has > it. Again, if it's optional it doesn't matter. Just to be sure that I have understood everything correctly: It is okay for you if we drop the colon after `otherwise' (i.e. forbid it) as long as we do not forbid a `begin/end' pair after `otherwise'? So it will be correct to write case foo of 1: writeln ( '… [View More]

1 0

Re: `case' statments: `default' and `others'
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Peter Wrote : I am currently fixing the bug with `otherwise' in `case' statements. While the ISO 10206 Extended Pascal standard wants case foo of (* 1 *) bar: writeln ( 'foobar!' ); otherwise write ( 'The answer is: ' ); writeln ( answer ); end (* case *); GPC implemented case foo of (* 2 *) bar: writeln ( 'foobar!' ); otherwise: begin write ( 'The answer is: ' ); writeln ( answer ); … [View More]

1 0

← Newer
1
2
3
4
5
6
7
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

Gpc November 1997