Gpc

gpc@gnu.de

5400 discussions

strict productions
by Paul Isaacs 01 Mar '17

01 Mar '17

Hello, Is the 10206 spec not strict? 6.8.6.2 Indexed-function-accesses An indexed-function-access shall denote a component of the value of a function-access possessing an array-type or a string-type. indexed-function-access = array-function `[' index-expression { `,' index-expression } `]' j string-function `[' index-expression `]' . array-function = function-access . But: 6.8.6 Function accesses function-access = entire-function-access | component-function-access | substring-function-access . component-function-access = indexed-function-access | record-function-access . entire-function-access = function-designator . And: 6.8.5 Function-designators function-designator = function-name [ actual-parameter-list ] According to the productions an indexed-function-access => array-function => function-access=>indexed-function -access Therefore, the only exit is via entire-function-access. But this would lead to a sentence of the form: x( a,b,c)[ 6,7,8 ] being valid and it is not. From: 6.8.6.2 Indexed-function-accesses An indexed-function-access shall denote a component of the value of a function-access possessing an array-type or a string-type. But this would be an identifier and the function-access productions do not indicate identifiers. Are the productions not strict? Does function-access include identifiers? Regards, Paul Isaacs

3 10

10206 productions re-write
by Paul Isaacs 24 Feb '17

24 Feb '17

Hello, Is the following rewrite correct? variable-access = entire-variable | component-variable | identified-variable | buffer-variable entire-variable = variable-identifier component-variable = indexed-variable | field-designator identified-variable = pointer-variable, '^' buffer-variable = file-variable, '^' indexed-variable = array-variable, `,', index-expression, < `,', index-expression > `]' field-designator = record-variable, ` .', field-specifier | field-designator-identifier array-variable = variable-access record-variable = variable-access pointer-variable = variable-access file-variable = variable-access field-specifier = field-identifier REWRITTEN variable access = entire variable | ( array variable, '[' index expression, < ',', index expression > ']' | record variable, '.' field specifier | field designator identifier | pointer variable, '^' | file variable, '^' | field specifier ), { '^' | '[' index expression, { ',', index expression }, ']' | '.', field specifier | field designator identifier } Thanks, Paul Isaacs

3 4

Two Dimensional Arrays
by Peter 14 Feb '17

14 Feb '17

Hi, Does anyone know the syntax for initializing a dynamic array of more than one dimension? type {$ifdef __GPC__} tMSet (n:CWord) = Array [1..n, 1..n] Of double; {$else} tMSet = Array Of Array Of double; var MSet : tMSet; {$endif} pMSet : ^tMSet; ........ {$ifdef __GPC__} new (pMset, n, n); {$else} SetLength (Mset, n, n); pMSet := @Mset; {$endif} The above works in FPC, but fails in GPC on the "new" with "error: `New' applied to this schema requires 1 discriminant value" This general approach works fine for 1D arrays. Regards, Peter B

2 3

10206 lexical ambiguity
by Paul Isaacs 24 Jan '17

24 Jan '17

Hello, Am I correct that, without semantic type tie-ins, that the production new-ordinal-type = enumerated-type | subrange-type ; is ambiguous because (a) could be both an enumerated type and the expression for the lower bound of a subrange? Regards, Paul Isaacs

5 9

function-pointer
by Paul Isaacs 23 Jan '17

23 Jan '17

Hello, From ISO spec: production: expression can be variable-access variable-access can be function-identified-variable function-identified-variable is pointer-function '^' pointer-function is function-access function-access can be entire-function-access entire-function-access is function-designator function-designator is function-name But: function test : boolean; begin test := false; end; procedure test1; begin if test^; end; generates the error "invalid type of argument of '^'" function-identified-variable only appears on the rhs of the variable access production. The expression test^ seems lexically correct. I know I am wrong. But where? How is function-identified-variable used? I really can't understand 6.8.6.4 Function-Identified-Variables of the spec. It sounds like a function-identified-variable is the return value of a pointer function. Is test^ a pointer function? Regards, Paul Isaacs

1 1

Re: type-inquiry
by Waldek Hebisch 23 Jan '17

23 Jan '17

I wrote: > > Paul Isaacs wrote: > > > > On 22/01/17 11:09 AM, Waldek Hebisch wrote: > > > It seems that if you want you can replace type-inquiry by explicit > > > definition. > > > > Hello Waldek, > > > > Thanks for the reply. I just assumed, incorrectly, that type-inquiry was > > a reflective construct of some sort. > > It _is_ a reflective construct. Just most of time you can live > without it. Maybe an example: > > var a : record i : integer end; > > Note that if you write: > > var b : record i : integer end; > > then b will be of different type than a (because each 'record' > introduces entirely new type). You can solve the problem > using named type: > > type t = record i : integer end; > var a : t; > > var b : t; > > Or you can use type-inquiry: > > var b : typeof(a); > > If you can modify declaration of 'a' you probably prefer > first version. But in real life you may be unable to > modify declaration of 'a'... > > Note: in GPC 'typeof' is only implemented for object types > (which are absent in Extended Pascal) so this does not work. Oops. I should write: var b : type of(a); 'typeof' is a Borland Pascal stuff, 'type of' is Extended Pascal. Both are obscure enough that I confused them. -- Waldek Hebisch

1 0

type-inquiry
by Paul Isaacs 23 Jan '17

23 Jan '17

Hello, How is the production type-inquiry used? var p : integer; type q = type of p; How would it be possible that inquiring as to the type of p is useful? Under what circumstances would the type of p not be already known? Even if the type of p were not known, how would q be usable if its type were not fixed? The only reference I can find is in the GNU-Pascal Manual. function CompilerAssert( condition : boolean, result : Anytype ) : type of Anytype; What would be returned? Unless Anytype is restricted to types that CompilerAssert is aware of. Regards, Paul Isaacs

3 4

program parameters
by Paul Isaacs 19 Jan '17

19 Jan '17

Hello, Are program parameters tied in any way to command line parameters? Is it possible to set BindingType.Name from the command line using a program parameter? program( a ... var a : bindable Text; b : BindingType; begin b := Binding( a ); Bind( a, b ); where b.Name has been set from the command line. Thank you, Paul Isaacs

3 3

Re: Gpc Digest, Vol 43, Issue 19
by Oscar Flor 16 Jan '17

16 Jan '17

Thanks You very much Peter... El 16/1/2017 8:00, <gpc-request(a)gnu.de> escribió: > Send Gpc mailing list submissions to > gpc(a)gnu.de > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.g-n-u.de/mailman/listinfo/gpc > or, via email, send a message with subject or body 'help' to > gpc-request(a)gnu.de > > You can reach the person managing the list at > gpc-owner(a)gnu.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Gpc digest..." > > > Today's Topics: > > 1. Re: rpm available for fedora (Peter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 15 Jan 2017 17:10:55 +0000 > From: Peter <peter(a)pblackman.plus.com> > To: gpc(a)gnu.de > Subject: Re: rpm available for fedora > Message-ID: <52de0911-c796-8df9-e265-2c46a12ce673(a)pblackman.plus.com> > Content-Type: text/plain; charset=utf-8 > > On 13/01/17 15:16, Oscar Flor wrote: > > Hi Pals: > > > > I find on rpm.pbone rpm packages of gpc20070904 for 64 and 32 bits. I > > test it on Fedora 20 and works. I realize that this version of Fedora > > have the gcc 4.8 installed on it, thats have me to think that this is > > not used to compile gpc and make the rpm package. > > > > I will test on newest fedora releases to know if they still work. > > Meanwhile I will learn read about GCC and his tools to try to make a > > compile on newest vesions on GCC. > > > > Best Regards > > > > Oscar Flor > > > > Hi Oscar, > > The build process is well defined here > http://alignment.hep.brandeis.edu/Software/Pascal/Pascal. > html#Compiling%20from%20Sources > > > The Fedora source packages will likely contain extra patches to help > build (with 4.8) the version of GCC that GPC is based on. There may be > other fixes to the Autotools stuff too. > > > Regards, > Peter > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Gpc mailing list > Gpc(a)gnu.de > https://www.g-n-u.de/mailman/listinfo/gpc > > ------------------------------ > > End of Gpc Digest, Vol 43, Issue 19 > *********************************** >

1 0

rpm available for fedora
by Oscar Flor 15 Jan '17

15 Jan '17

Hi Pals: I find on rpm.pbone rpm packages of gpc20070904 for 64 and 32 bits. I test it on Fedora 20 and works. I realize that this version of Fedora have the gcc 4.8 installed on it, thats have me to think that this is not used to compile gpc and make the rpm package. I will test on newest fedora releases to know if they still work. Meanwhile I will learn read about GCC and his tools to try to make a compile on newest vesions on GCC. Best Regards Oscar Flor

2 1

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

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