Gpc March 2002

gpc@gnu.de

22 participants
41 discussions

GPC 2.1 RC 4 released
by Frank Heckenbach 19 Mar '02

19 Mar '02

Hi everyone, GPC version 20020318, the release candidate #4 for GPC 2.1, has been uploaded to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/current/gpc-20020318.tar.gz Compared to RC 3, this release contains only some minor bug fixes and portability enhancements. One bug in the recent OOP extensions has been fixed (thanks to Maurice Lombardi for the report). Some build problems on Cygwin/mingw have been resolved (thanks to the Chief). Some minor problems on Linux/S390 have been fixed (thanks to Gerhard Tonn and Matthias Klose for providing a test account). Some bugs regarding types of size 0 have been fixed (thanks to reports by Emil Jerabek). The cooperation with GCC patched for Cygwin/mingw, gcc-2.95.3-5, gcc-2.95.3-6 and gcc-2.95.4 has been improved. Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

2 1

Re: Record alignment
by KOCHERALKOTA harikrishna 19 Mar '02

19 Mar '02

Hello, Is it possible to make the set datatype to occupy only one byte? Now by default the compiler allocates 4 bytes.We even tried packing it,but it's still the same. Have a Great Day! Kind Regards, Karthic and Hari P.S: As specified in one of your mails in the mailing list for a similar problem, we even tried builiding the compiler by changing the P/rts/sets.pas(Tsetelement = byte) and also in P/util.c(set_word_size and set_alignment = 8).Still we are unsuccessful.

1 0

combining Gnu pascal and Fortran 77
by Dusan Fiala 19 Mar '02

19 Mar '02

Hi gpc-subscribers, has anybody experience or has tried to call a module written in GNU pascal from a Fortran 77 routine (run on unix platforms) and is happy to give advice on that? I would be grateful for any advice on whether or not it is (in principle) possible to (i) call modules available in GNU pascal from routines written in Fortran 77 (unix) and (ii) exchange data i.e. program parameters and variables (incl. arrays) between the modules. This bi-directional data exchange is supposed to be performed for every (time) step of a dynamic simulation process. Thanking in anticipation. Best regards Dusan Fiala --------------------------------------------------------------------------- Dr. Dusan Fiala Phone : (+44) 0116 257 7971 Institute of Energy and Sustainable Development De Montfort University, Scraptoft Campus Fax : (+44) 0116 257 7981 Leicester LE7 9SU - United Kingdom e-mail: dfiala(a)dmu.ac.uk ---------------------------------------------------------------------------

2 1

emx_os2 target works
by Yuri Prokushev 18 Mar '02

18 Mar '02

Compiled using pgcc 2.95.3 with emxlibc 0.9d fix 4. Not very fine, but works ;-) # of GPC tests 2602 # of GPC tests passed 2470 # of GPC tests skipped 12 # of GPC tests failed 120

2 1

Dynamic arrays
by Silvio a Beccara 18 Mar '02

18 Mar '02

Hello, is there a way that dynamic arrays can be created (using schemata) which are GLOBAL, i.e. not accessible in the sole main program, but also in all functions and procedures included in it? For instance this little piece of code gives me this error: espon.pas: In procedure `Merce': espon.pas:50: undeclared identifier `Vett' (first use in this routine) espon.pas:50: (Each undeclared identifier is reported only once espon.pas:50: for each routine it appears in.) espon.pas:50: subscripted object is not an array or string the code follows: program skifo; type TVecDob (Size: Integer) = array [ 1 .. Size ] of double; PVecDouble = ^TVecDob; Function Power ( base: real; espon: integer ): double; var i, j: integer; buff: real; begin buff := base; for i :=1 to espon - 1 do begin buff := buff * base; end; result := buff; end; Procedure merce; var i,j: integer; begin for i := 1 to 10 do begin writeln (' vett ', i, '=', vett [i] ); end; end; var nelem, i, j : integer; begin nelem := 10; var vett: TVecDob ( nelem ); for i := 1 to 10 do begin vett [i] := 1+0.1*i; end; merce; end. Thank you very much Silvio

4 6

Re: Again a question on Enumerated datatype
by Anuradha 18 Mar '02

18 Mar '02

Hello , It gives us 264 as size and capacity is 0. we have gpc-20010924.Is it corrected in a newer version? Thanks and Regards, Anuradha. Prof Abimbola Olowofoyeku wrote: > On 18 Mar 2002 at 13:05, Anuradha wrote: > > > Hello , > > > > The following program works in BP but prints blank in GPC. > > Can you tell us why. > > > > program sts; > > type mytype = (a,b,c,d); > > myrec =record > > st:string; > > end; > > var arr : array[mytype] of myrec; > > begin > > arr[d].st :='anu'; > > writeln(arr[d].st); > > end. > > It doesn't print blank here. It prints 'anu'. > > FWIW, there may be a problem with your record. What is the > size/capacity of the string 'st' ? > > Best regards, The Chief > -------- > Prof. Abimbola A. Olowofoyeku (The African Chief) > web: http://www.bigfoot.com/~African_Chief > email: African_Chief(a)bigfoot.com

3 3

Fwd: Re: constants in rts/rts.c
by Yuri Prokushev 18 Mar '02

18 Mar '02

==================BEGIN FORWARDED MESSAGE================== >From: "Yuri Prokushev" <prokushev(a)freemail.ru> >To: "Frank Heckenbach" <frank(a)g-n-u.de> >Date: Mon, 18 Mar 2002 11:10:59 -0500 (EST) >Reply-To: "Yuri Prokushev" <prokushev(a)freemail.ru> >Priority: Normal >X-Mailer: PMMail 2.20.2380 for OS/2 Warp 4.5 >In-Reply-To: <200203172125.WAA10698(a)goedel.fjf.gnu.de> >MIME-Version: 1.0 >Content-Type: text/plain; charset="koi8-r" >Content-Transfer-Encoding: 7bit >Subject: Re: constants in rts/rts.c > On Sun, 17 Mar 2002 22:25:07 +0100, Frank Heckenbach wrote: >Yuri Prokushev wrote: > >> Where defined F_* constants for rts.c? >> >These should be defined in <sys/stat.h> or some other system header. > >> rts.c: In function `_p_FlushHandle': >> rts.c:1682: warning: implicit declaration of function `fsync' > >This code is enclosed in `#ifdef HAVE_FSYNC'. Similar for other >functions (and the F_* constants which are in `#ifdef HAVE_FCNTL'). > >Since HAVE_FSYNC is set (by configure, unless you changed this >manually), I assume your system does in fact have these functions, >but it's missing the declarations in the headers (as for the S_* >constants). > >This is for EMX, is it? Well, I haven't used EMX myself so I don't >know what its headers look like. Perhaps you just have to include >some more header (if I know which one, I can do it automatically in >the future, but you can try adding #include statements in rts.c >manually). Yes. This is for emx. sys/stat.h contains all required definitions, but seem to be incorrect include path (/usr/local/... instead c:/emx/include). I don't understand yet how to fix it. But fcntl.h doesn't contain file lock definetions. fcntl.h from posix/2 lib seems to be more fine. >Is anyone on this lists who's used EMX recently? I haven't heard >much of it for some years ... Latest emx+gcc is 0.9d fix 4 (dated 20 march 2001). But in emx+gcc old gcc 2.8.1. Now presented pgcc-2.95.3 (I trying compile gpc with it), and GNU CC 3.0.x. This compilers patched and compiled by Andrew Zabolotny. So, now used emxlibc and gcc from AZ. Now developing libext (also known as libemu or posix/2) wich seems to be successor of emxlib. ===================END FORWARDED MESSAGE===================

2 1

Re: Again a question on Enumerated datatype
by Anuradha 18 Mar '02

18 Mar '02

Hello, Thankyou.It is working fine in 20011215.Sorry for the trouble. Regards, Anuradha Prof Abimbola Olowofoyeku wrote: > On 18 Mar 2002 at 13:42, Anuradha wrote: > > > Hello , > > > > It gives us 264 as size and capacity is 0. > > Hmmm ... the capacity (AFAIK) should not be 0. I thought GPC defaults > to a capacity of 255 when no capacity is supplied? > > > we have gpc-20010924.Is it corrected in a newer version? > > Apparently. But I think you need to correct it in your code. It is not > a good idea to declare a string field in a record without specifying > the size/capacity of the string. Basically, it means that you are > leaving it to someone else (e.g., the compiler) to determine the size > of your record - and it may decide on a size that is different from the > one you would like (as seems to have beem done here). > > Something like this would be a better solution, should work with all > compilers, and should solve your specific problem; > > type myrec = record > st : string [128]; > end; > > Best regards, The Chief > -------- > Prof. Abimbola A. Olowofoyeku (The African Chief) > web: http://www.bigfoot.com/~African_Chief > email: African_Chief(a)bigfoot.com

1 0

Again a question on Enumerated datatype
by Anuradha 18 Mar '02

18 Mar '02

Hello , The following program works in BP but prints blank in GPC. Can you tell us why. program sts; type mytype = (a,b,c,d); myrec =record st:string; end; var arr : array[mytype] of myrec; begin arr[d].st :='anu'; writeln(arr[d].st); end. Thanks and Regards, Anuradha

2 1

constants in rts/rts.c
by Yuri Prokushev 17 Mar '02

17 Mar '02

Where defined F_* constants for rts.c? ../.././xgcc -B/usr/local/i386-pc-os2_emx/bin/ -B../.././ -I/usr/local/i386-pc-os2_emx/include -c -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 -DRTS_RELEASE_STRING="'`cat /gpc/pgcc-2.95.3/gcc/p/rts/rts-version`'" rts.c rts.c: In function `_p_Real_Ln1Plus': rts.c:717: warning: unused parameter `x' rts.c: In function `_p_Mode2SysMode': rts.c:1566: `S_IRUSR' undeclared (first use in this function) rts.c:1566: (Each undeclared identifier is reported only once rts.c:1566: for each function it appears in.) rts.c:1566: `S_IWUSR' undeclared (first use in this function) rts.c:1566: `S_IXUSR' undeclared (first use in this function) rts.c:1567: warning: control reaches end of non-void function rts.c: In function `_p_SysMode2Mode': rts.c:1571: `S_IRUSR' undeclared (first use in this function) rts.c:1571: `S_IWUSR' undeclared (first use in this function) rts.c:1571: `S_IXUSR' undeclared (first use in this function) rts.c:1572: warning: control reaches end of non-void function rts.c: In function `_p_Stat': rts.c:1610: storage size of `st' isn't known rts.c:1614: warning: implicit declaration of function `stat' rts.c:1635: warning: implicit declaration of function `S_ISDIR' rts.c:1610: warning: unused variable `st' rts.c: In function `_p_FlushHandle': rts.c:1682: warning: implicit declaration of function `fsync' rts.c: In function `_p_CStringChMod': rts.c:1757: warning: implicit declaration of function `chmod' rts.c: In function `_p_TruncateHandle': rts.c:1841: warning: implicit declaration of function `ftruncate' rts.c: In function `_p_LockHandle': rts.c:1855: storage size of `Lock' isn't known rts.c:1858: `F_WRLCK' undeclared (first use in this function) rts.c:1858: `F_RDLCK' undeclared (first use in this function) rts.c:1861: `F_SETLKW' undeclared (first use in this function) rts.c:1861: `F_SETLK' undeclared (first use in this function) rts.c:1855: warning: unused variable `Lock' rts.c: In function `_p_UnlockHandle': rts.c:1876: storage size of `Lock' isn't known rts.c:1879: `F_UNLCK' undeclared (first use in this function) rts.c:1882: `F_SETLK' undeclared (first use in this function) rts.c:1876: warning: unused variable `Lock' make[1]: *** [rts.o] Error 1 make[1]: Leaving directory `/gpc/pgcc-2.95.3/gcc/p/rts' make: *** [pascal.rts] Error 2

2 1

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 March 2002