Gpc

gpc@gnu.de

5400 discussions

gcc-2.8.1 and gpc
by Mehul Sanghvi 04 Jun '98

04 Jun '98

'allo, Does GPC work with GCC 2.8.1 or do I still have to use GCC-2.7.2.1 for it ? Thanks, mehul -- Mehul Sanghvi email: <mehul(a)ziplink.net> wwweb: <http://www.ziplink.net/users/mehul/> Windows 95: n. Computing software with a graphical shell and 32 bit extensions for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company, that can't stand 1 bit of competition.

2 2

Re: GPC REFERENCES: do
by Nick Burrett 04 Jun '98

04 Jun '98

On 3 Jun 98 at 11:34, Miklos Cserzo wrote: > do > > SYNTAX: > for iteration_variable := initial_value to final_value do statement > > or > for iteration_variable := initial_value downto final_value do statement > > or > > while boolean_expression do statement > > or > > with list_element[,...] do statement > If we are going to supply syntax to Pascal constructs then I suggest that they are suppled as proper grammar i.e. the LALR(1) format. Nick.

3 3

GPC REFERENCE: until
by Miklos Cserzo 03 Jun '98

03 Jun '98

until SYNTAX: repeat statement1; statement2; .... until boolean_expression; DESCRIPTION: The "until" keyword is used exclusively in combination with "repeat" keyword in all Pascal standards. See the reference page for "repeat" for the details. STANDARDS: All EXAMPLE: SEE ALSO: repeat

2 1

Re: GPC REFERENCE: begin
by Frank Heckenbach 03 Jun '98

03 Jun '98

> > DESCRIPTION: "begin" is word-symbol (reserved word) in all Pascal ^a > > standards. "begin" with its enclosing "end" groups together the statements Is "enclosing" the right word? English is not my native language, but I'd think the statements between "begin" and "end" are "enclosed", not the "end" itself. > > Wherever the Pascal syntax requires one statement "begin" ... > > "one single"? > > > "end" constructions can be used. Perhaps a small example here (a "for" or "while" loop)? > > "begin end;".) The execution part of a program block syntactically is a > > single statement therefore should be enclosed into a "begin ... end." > > construction. Perhaps clarify that it *must* be enclosed. Otherwise, someone might get the idea that the following would be valid: program foo; writeln('Hello, world.'). > This holds for the (optional) initialization part of Units as well. Don't forget to mention in the "Standards" section that this is a BP (or already UCSD?) extension, in contrast to "to begin/end do" which are EP. -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

2 1

Re: GPC REFERENCES: do
by Frank Heckenbach 03 Jun '98

03 Jun '98

Miklos Cserzo wrote: > The later form is for easy access of fields of record or schema type > variables. or object type -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

Re: GPC REFERENCE: repeat
by Frank Heckenbach 03 Jun '98

03 Jun '98

Miklos Cserzo wrote: > "repeat" is reserved word in all Pascal dialects for creating loops in the ^a > program execution. The statements after the "repeat" executed ^are > sequentially. When the "until" statement reached the execution continues ^is > with the next statement if the boolean expression evaluates "true". If it > is "false" the execution continues at the next statement after the ^^^^first(?) > starting "repeat" of the loop and the enclosed statements will be executed > again. > > The statements in the loop will be executed at least once. If the > expression in the "until" statement always "false" the execution falls ^is > into infinite loop. ^an > It is allowed the create nested "repeat - until" loops where the closest ^^^to > .... > repeat { echo the input from "infile" to "outfile" } > readln(infile,buffer); > writeln(outfile,buffer); > until eof(infile); > close(infile); close(outfile); > .... IMHO a bad example for repeat, better suited for a while loop, since infile can be empty. -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

Re: GPC REFERENCE: for
by Kevin A. Foss 03 Jun '98

03 Jun '98

On Wed, 3 Jun 1998 18:54:27 +0200 (MEST), Peter Gerwinski wrote: >According to Miklos Cserzo: >> After the execution of the loop the value of the control variable is >> undefined. > >While this is stated in ISO-10206 I have seen some ISO-7185 test programs >that require the value to be <final_value>. Somebody knows definitly? ISO 7185:6.8.3.9 says that it should be undefined, unless the loop is exited via a goto. (This same discussion came up recently on c.l.p.ansi-iso, so I'm fairly sure of this... don't have the standard in front of me right as I write this :) ) >> A proper code should not relay on that value. I agree with this, so I'm interested to hear about the test programs you have that rely on post loop values of the control variable. Perhaps this is something that wasn't enforced in early Pascal implementations and later was codified in the standard. >(You see: The "Standards" section is taking over ... ;-) > >(You also see why I am so slow in writing documentation. ;-)-: I think this might be the best benefit of the current process of having everyone post their entries to the list. Partially so others can comment on other standards that the author of each section might not be familiar with, and partially so the developers can comment on any extra GPC-specific features that might also be available. -Kevin -- Kevin A. Foss -- kfoss(a)mint.net

1 0

Subject: Re: GPC REFERENCES: do
by Frank Heckenbach 03 Jun '98

03 Jun '98

(* The subject line is misleading now since this will be in the "to begin"/ "to end" sections, but I kept it anyway. *) > to begin do statement; > or ^ Better mention it with or without this one? > to end do statement; In this case, I'd say, with the semicolon, since the semicolon is necessary because of the "to begin do". In other cases, like the various loops, there should be -- strictly speaking -- no semicolon at the end, because it's not required by the loop, and actually doesn't have to be there (e.g. before an "end" or an "else" that belongs to a "case"), and sometimes even must not be there (before an "else" that belongs to an "if"). -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

Subject: Re: GPC REFERENCE: for
by Frank Heckenbach 03 Jun '98

03 Jun '98

Just some spelling corrections and such... > variable set to the initial value then incremented by 1 after each ^is > loop executed ones. If the initial value higher than the final value the ^s ^^^^once ^is > body of the "do" statement not executed. ^is > In the second form of the command the control variable decremented by 1 in ^is > inside the loop. The code that violate that rule will compile and run - if ^^^() ^s > After the execution of the loop the value of the control variable is > undefined. A proper code should not relay on that value. ^^^^^rely -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

GPC REFERENCE: begin
by Miklos Cserzo 03 Jun '98

03 Jun '98

begin SYNTAX: begin statement1; statement2; .... end; DESCRIPTION: "begin" is word-symbol (reserved word) in all Pascal standards. "begin" with its enclosing "end" groups together the statements between them so they are treated as one single statement during the execution. Wherever the Pascal syntax requires one statement "begin" ... "end" constructions can be used. (It is allowed to use empty statement: "begin end;".) The execution part of a program block syntactically is a single statement therefore should be enclosed into a "begin ... end." construction. This apply to the execution part of procedures and functions as well. It is a syntax error having a "begin" without an enclosing "end". STANDARDS: all EXAMPLE: var ok:boolean; ... if not ok then begin writeln('Error occurred, execution aborted.'); halt; end; SEE ALSO: end, for, while, do _________________________ Comment this please. miklos

2 1

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

2001

2000

1999

1998

1997

1996

1995

Gpc