- Gpc - gnu.de

Re: fatal signal 6
by Frank Heckenbach 05 Jul '00

05 Jul '00

Mariusz Zynel wrote: > Claude, Victor and Others > > Khimenko Victor wrote: > > > > 30-Jun-00 13:16 you wrote: > > > Maruisz, > > > > > The package wants to install in /usr/local. Will this clobber (i.e. > > > overwrite) my existing gcc 2.95.2 installation? > > > > If gcc is installed in /usr/local then it CAN do it. Probability is SMALL, > > though: files common for gcc and gpc should be equal anyway. > > Victor is right. Since my package is based on gcc 2.95.2, I think > common files i.e. libgcc.a, collect2 and specs should be equal up > to functionality. One problem I've seen with libgcc.a: It contains common code used by all compilers and some special code for C++ (and perhaps other languages such as Fortran). So, if the GPC binary was built with C++ disabled, the libgcc.a might be missing this code, causing C++ programs to fail. However, GPC does not add special code to libgcc.a (all of GPC's runtime code is in libgpc.a), so keeping (or restoring) the libgcc.a from the GCC installation is safe for C and C++, and should work for GPC as well. > Files my differ due to compiler used. Please, > correct me if I'm wrong. Different compiler versions might have slightly different libgcc.a's (though I've done a mixed C/C++/Pascal project with different versions of GCC, G++ and GPC, and it was linked without problems under Solaris and Linux), but in this case there's no danger of overwriting files because the compiler backend version (e.g., 2.95.2) is part of the directory name. > Sorry List for being a bit OT, Not really, IMHO. :-) 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

1 0

Re:
by Frank Heckenbach 04 Jul '00

04 Jul '00

Nathalie Jarosz wrote: > > > I have change of system: from linux, I am on a Unix workstation and when > >I > > > compile program which used to work under linux, the following message > > > appears: > > > "Internal compiler error in 'emit_library_call_value', at calls.c:3198" > > > > > What does it mean? > > > >Exactly what it said: you just found bug in GPC itself (calls.c is part of > >GPC). In such cases you REALLY must supply all details: > > 1. What type of unix you are using (CPU version, OS version, etc). > Sun Microsystems Inc. SunOS 5.7 > > > 2. What type of GPC you are using (built against GCC v..., GPC v..., > >etc). > gpc version 19991030 based on 2.95.2 19991024 > > > 3. Sample code to get internal error. > ? > > Here is the routine which is involved: > > function travel(djk:real;md:mat;A:minitable;Ak:real;ns,j:integer):real; > {probability of an individual leaving patch j to reach patch k} > const > alpha = 4.910; > zim = 0.263; > lambda = 0.175; > var > Sj,t : real; > begin > Sj:=connect(md,A,ns,j); > t:=(exp(-alpha*djk)*pow2(Ak,zim))/((lambda/Sj)+Sj); > travel:=t; > end; This is exactly the same GPC bug that Clyde Meli has just reported. As I wrote last night, this bug has been fixed meanwhile. According to the `Fixed Bugs' section in the To-Do list <http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html>: 20000503: Sparc: division by reals (fjf237.pas, matt1.pas) or `Round (real_constant)' (chaput1.pas) make the compiler crash <199911040915.KAA11168@@humulus.daimi.au.dk> (Sparc is the processor used in Sun's machines.) Until there is a new GPC release with this bug fixed, you can work around by type-casting the constants to Real: const alpha = Real (4.910); zim = Real (0.263); lambda = Real (0.175); 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

1 0

Re: beta distribution
by Nathalie Jarosz 04 Jul '00

04 Jul '00

>From: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> >To: Nathalie Jarosz <jarosz_n(a)hotmail.com>, gpc <gpc(a)gnu.de> >Subject: Re: beta distribution >Date: Fri, 30 Jun 2000 17:48:58 +0200 >Well it is simple enough to be made by hand (there are no dependencies). >With GNU tools type: > >cd src >gcc -c -O2 com.c >gcc -c -O2 linpack.c >gcc -c -O2 randlib.c ># ^uppercase: meand Optimize ># at this point you have created com.o linpack.o randlib.o ># to put them in a library librandlib.a type: >ar -rv librandlib.a com.o linpack.o randlib.o >ranlib librandlib.a ># ^ no d: it is a system function > >#then move librandlib.a into a system wide library directory e.g. >/usr/local/lib ># randlib.h include >/usr/local/include All seems to be ok until here but when I check the result: >#to check the result >cd ../test >gcc -O2 -o tstbot tstbot.c -lrandlib > ^lowercase: means output the following message appears: tstbot.c: In function `main': tstbot.c:11: warning: return type of `main' is not `int' Undefined first referenced symbol in file log /usr/local/lib/librandlib.a(randlib.o) pow /usr/local/lib/librandlib.a(randlib.o) sqrt /usr/local/lib/librandlib.a(randlib.o) exp /usr/local/lib/librandlib.a(randlib.o) ld: fatal: Symbol referencing errors. No output written to tstbot collect2: ld returned 1 exit status What is the problem now? Thanks in advance, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

2 1

Re: Internal compiler error - bug
by Clyde Meli 04 Jul '00

04 Jul '00

> > I fixed the problem termporarily by commenting out (fmultiple - 1.0) as it is > > equal to 1.0 currently, and by replacing fmultiple in the other > > assignment (b:=uavg*(umax- etc.) by real(2) instead. It seems writing the > > constant there triggered a problem with the compiler. > > Indeed, this was a GPC bug that has been fixed meanwhile. According > to the `Fixed Bugs' section in the To-Do list > <http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html>: > > 20000503: Sparc: division by reals (fjf237.pas, matt1.pas) or > `Round (real_constant)' (chaput1.pas) make the compiler crash > <199911040915.KAA11168@@humulus.daimi.au.dk> > > Unfortunately, there's been no GPC release since 2000-05-03, so > please either wait for the next release, or use the type-casting > workaround in the first assignment as well (this should work, I > think -- can't verify it, since my development compiler doesn't have > this bug anymore): > > a:= (Real (fmultiple) - 1.0) * uavg / delta; > > Frank Ok, thank you very much. I think I can use it as it is. With the previous version I had problems with enumerated types in case statements, now it seems they work fine. Regards, Clyde

1 0

Re:
by Nathalie Jarosz 04 Jul '00

04 Jul '00

>From: "Khimenko Victor" <gpc(a)khim.sch57.msk.ru> >To: jarosz_n(a)hotmail.com, gpc(a)gnu.de >Subject: Re: >Date: Thu, 29 Jun 2000 00:53:40 +0400 (MSD) > >28-Jun-00 15:31 you wrote: > > Hello all! > > > I have change of system: from linux, I am on a Unix workstation and when >I > > compile program which used to work under linux, the following message > > appears: > > "Internal compiler error in 'emit_library_call_value', at calls.c:3198" > > > What does it mean? > >Exactly what it said: you just found bug in GPC itself (calls.c is part of >GPC). In such cases you REALLY must supply all details: > 1. What type of unix you are using (CPU version, OS version, etc). Sun Microsystems Inc. SunOS 5.7 > 2. What type of GPC you are using (built against GCC v..., GPC v..., >etc). gpc version 19991030 based on 2.95.2 19991024 > 3. Sample code to get internal error. ? Here is the routine which is involved: function travel(djk:real;md:mat;A:minitable;Ak:real;ns,j:integer):real; {probability of an individual leaving patch j to reach patch k} const alpha = 4.910; zim = 0.263; lambda = 0.175; var Sj,t : real; begin Sj:=connect(md,A,ns,j); t:=(exp(-alpha*djk)*pow2(Ak,zim))/((lambda/Sj)+Sj); travel:=t; end; Thanks in advance for your help, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

type ^T_Str_t generates a parse error
by Marten Jan de Ruiter 04 Jul '00

04 Jul '00

Hello all, I am trying to port a large program written on a SUN to linux using gpc. So far it goes well, but I run into an error. type T_PtrStr_t = ^TZ_Str_t; compiles perfectly, while type T_PtrStr_t = ^T_Str_t; generates a warning: warning: identifiers should not start with an underscore parse error before `;' I have added the transcription of the session using an as small as possible program. For clarity, the difference between the two source files is the removal of the three Z's: two in the type declaration and one in the var declaration. Can someone point out what is wrong with the compilation of the second program? Thanks in advance, Marten Jan de Ruiter mailto:m.j.deruiter@wbmt.tudelft.nl 37 % cat -n pointertypeOK.p 1 program pointertypeOK; 2 3 type 4 TZ_Str_t = string[6]; 5 T_PtrStr_t = ^TZ_Str_t; 6 7 var s: TZ_Str_t; 8 p: T_PtrStr_t; 9 10 begin 11 s:='world!'; 12 p:=addr(s); 13 writeln('hello ',p^); 14 end. src 38 % gpc pointertypeOK.p -o pointertypeOK src 39 % pointertypeOK hello world! src 41 % cat -n pointertypeNO.p 1 program pointertypeNO; 2 3 type 4 T_Str_t = string[6]; 5 T_PtrStr_t = ^T_Str_t; 6 7 var s: T_Str_t; 8 p: T_PtrStr_t; 9 10 begin 11 s:='world!'; 12 p:=addr(s); 13 writeln('hello ',p^); 14 end. 42 % gpc pointertypeNO.p -o pointertypeNO pointertype.p:5: warning: identifiers should not start with an underscore pointertype.p:5: parse error before `;' pointertype.p:5: extra semicolon pointertype.p:5: extra semicolon pointertype.p:8: type name expected, identifier `T_ptrstr_t' given pointertype.p: In function `program_Pointertype': pointertype.p:12: incompatible types in assignment pointertype.p:13: invalid type argument of ``^''

2 2

Re: type ^T_Str_t generates a parse error
by Frank Heckenbach 04 Jul '00

04 Jul '00

Marten Jan de Ruiter wrote: > I am trying to port a large program written on a SUN to linux using gpc. So far > it goes well, but I run into an error. > type T_PtrStr_t = ^TZ_Str_t; compiles perfectly, while > type T_PtrStr_t = ^T_Str_t; generates a warning: > warning: identifiers should not start with an underscore > parse error before `;' > > I have added the transcription of the session using an as small as possible > program. For clarity, the difference between the two source files > is the removal of the three Z's: two in the type declaration and one in the var > declaration. > > Can someone point out what is wrong with the compilation of the second program? This was a GPC bug that has been fixed meanwhile. According to the `Fixed Bugs' section in the To-Do list <http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html>: 19990618: the construct @samp{^f_oo} is misinterpreted as a Borland-style char constant (fjf350.pas) So, any version after this date (e.g., alpha 19990813 or the soon to come next release) will not suffer from this bug. 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

1 0

Internal compiler error - bug
by Clyde Meli 03 Jul '00

03 Jul '00

I'm compiling a PASCAL program under Solaris with gpc version 19991030 based on gcc 2.95.2. gpc --automake sgamain.pas generate.pas: In function `Prescale': generate.pas:33: Internal compiler error in `emit_library_call_value', at gcc-2. 95.2/gcc/calls.c:3198 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. gpc1: gpc exited with status 1 report.pas:9: module/unit `generate' could not be compiled The code which caused the problem looks like: Procedure Prescale(umax,uavg,umin:real;VAR a,b:real); { Calculate scaling coefficients for linear scaling } CONST fmultiple = 2.0; { fitness multiple is 2 } VAR delta:real; { divisor } Begin if umin > (fmultiple * uavg - umax) / (fmultiple - 1.0) { Non-Negative Test } then Begin { Normal Scaling } Delta:=umax-uavg; a:=(fmultiple - 1.0) * uavg / delta; b:=uavg * (umax - real(2) {fmultiple} * uavg) / delta; End else I fixed the problem termporarily by commenting out (fmultiple - 1.0) as it is equal to 1.0 currently, and by replacing fmultiple in the other assignment (b:=uavg*(umax- etc.) by real(2) instead. It seems writing the constant there triggered a problem with the compiler. I don't know if this counts as a bug or not. Regards, Clyde

1 0

Re: beta distribution
by Frank Heckenbach 30 Jun '00

30 Jun '00

Nathalie Jarosz wrote: > >From: "Khimenko Victor" <gpc(a)khim.sch57.msk.ru> > >To: jarosz_n(a)hotmail.com, gpc(a)gnu.de > >Subject: Re: beta distribution > >Date: Thu, 29 Jun 2000 20:40:28 +0400 (MSD) > > > > So I still have some questions... I have tried with a C routine and the > > > pascal unit and program but it doesn't work. > > > >What exactly you done ? It's really trivial task if you know both C and > >Pascal > >and thus it's hard to guess where newbie without C knowleadge can fail... > > So, I would like to use a beta random deviates I have in C, in my pascal > program. I have downloaded "randlib" which contain this function. > In randlib.h, there is: > extern float genbet(float aa, float bb); > > First, I have written beta.p : > unit beta; > interface > function genbet(x,y:real);C; The result type is missing. Further, `float' in C is `Single' or `ShortReal' in Pascal. On some platforms, the difference to `Real' doesn't cause problems, but on others, it does. So better use: function genbet(x,y:ShortReal):ShortReal;C; > implementation > end. > > Second, test.p: > program betadev; > uses > beta; > begin > writeln(genbet(100,150)); > end. > > Finally, I compile it with gpc and the following message appears: > "undefined first referenced > symbol in file > genbet /var/tmp/cciCa09s1.o > ld: fatal: symbol referencing errors > No output written to test > collect2 : ld returned 1 exit status" > > So... What is wrong? You need to link the C code. For a simple C file, you can insert `{$L foo.c}' into the unit, and GPC will automatically compile the C file. For a library libbar.a, you can use `{$L bar}' in the source which is equivalent to `-lbar' on the command line. 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

1 0

Re: beta distribution
by Nathalie Jarosz 30 Jun '00

30 Jun '00

>From: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> >To: Nathalie Jarosz <jarosz_n(a)hotmail.com> >CC: gpc(a)gnu.de >Subject: Re: beta distribution >Date: Fri, 30 Jun 2000 16:24:07 +0200 > >Have you read these two text files and those contained in the doc folder ? >Usually they contain >instructions on whet do do to install the package. Yes of course but nothing clear to me: INSTALLATION Directory src contains the C source for most of the routines. The files com.c and randlib.c constitute RANDLIB. The file randlib.h contains prototypes for the RANDLIB routines that should be used (and not for a few internal routines). The C code from these directories should be compiled and placed in a library. Directory test contains three test programs for this code. The file randlib.h in directory test is a copy of that in src. >Where have you gotten randlibc-1.3.tar.gz from ? I get from: http://odin.mdacc.tmc.edu/anonftp/page_2.html#RANDLIB Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

Re: beta distribution
by Maurice Lombardi 30 Jun '00

30 Jun '00

Nathalie Jarosz a Ã©crit : > > >From: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> > >To: Nathalie Jarosz <jarosz_n(a)hotmail.com> > >CC: gpc(a)gnu.de > >Subject: Re: beta distribution > >Date: Fri, 30 Jun 2000 16:24:07 +0200 > > > >Have you read these two text files and those contained in the doc folder ? > >Usually they contain > >instructions on whet do do to install the package. > Yes of course but nothing clear to me: > > INSTALLATION > > Directory src contains the C source for most of the routines. The > files com.c and randlib.c constitute RANDLIB. The file randlib.h > contains prototypes for the RANDLIB routines that should be used (and > not for a few internal routines). The C code from these directories > should be compiled and placed in a library. Directory test contains > three test programs for this code. The file randlib.h in directory > test is a copy of that in src. > > >Where have you gotten randlibc-1.3.tar.gz from ? > I get from: > http://odin.mdacc.tmc.edu/anonftp/page_2.html#RANDLIB Well it is simple enough to be made by hand (there are no dependencies). With GNU tools type: cd src gcc -c -O2 com.c gcc -c -O2 linpack.c gcc -c -O2 randlib.c # ^uppercase: meand Optimize # at this point you have created com.o linpack.o randlib.o # to put them in a library librandlib.a type: ar -rv librandlib.a com.o linpack.o randlib.o ranlib librandlib.a # ^ no d: it is a system function #then move librandlib.a into a system wide library directory e.g. /usr/local/lib # randlib.h include /usr/local/include #to check the result cd ../test gcc -O2 -o tstbot tstbot.c -lrandlib ^lowercase: means output ./tstbot #etc... -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0

Re: fatal signal 6
by Frank Heckenbach 30 Jun '00

30 Jun '00

Marinier, M. Claude, G. wrote: > I am trying to port a 3D graphics package from VMS/Alpha with DEC Pascal > to Solaris 7 (a.k.a. Solaris 2.7). I have installed version 19990119 of > gpc with version 2.8.1 of gcc. > > I have successfully compiled the first three levels of the graphics > package. When compiling level4.pas, I get a 'fatal error 6' message, a > .gpi file but no .o file. > > I systematically trimmed code (whole functions and procedures) off the end > of the source file until is compiled. Most of the implementation section > was gone at that point. I tried commenting out the same code with '(*' and > '*)' with the same result: it compiled. I then tried to remove only the > code on the border, i.e. the compilation failed, I removed another > procedure, and it compiled; that last procedure is the one I removed from > the full source. This was based on the assumption that some code triggered > the failure. The compilation failed with the 'offending' code removed. I > abandonned that avenue of research. The bug might be provoked by a combination of two procedures, so this effort wasn't in vain. If the shortest code that still fails is not very long (I suppose it isn't if most of the implementation was removed -- and probably much of the interface can be removed as well), you might want to show it to us so we can have a look at it and try to fix the problem. > Try using the latest gcc as a base? Might help. Also, a new GPC snapshort will be released soon (which will require gcc-2.95.x), and you might want to try it then. > Use Modules instead of Units? I would need documentation of those. Probably not. Units generally work better than (or at least as well as) modules in GPC. 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: beta distribution
by Nathalie Jarosz 30 Jun '00

30 Jun '00

>From: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> >To: Nathalie Jarosz <jarosz_n(a)hotmail.com>, gpc <gpc(a)gnu.de> >Subject: Re: beta distribution >Date: Fri, 30 Jun 2000 15:58:33 +0200 > >What do you mean by compile "one" of the sources. C packages come with >makefiles to handle the >module dependencies and frequently a configure system to handle the >difference between computers and >OSes. You never have to compile files one at a time by hand. After having unpacked the sources called randlibc-1.3.tar.gz, I have the folder randlib.c composed of 2 text files and 3 folders named doc, src and test. In the src folder, there are 4 files : com.c, linpack.c, randlib.c and randlib.h but no makefile?... ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

2 1

Re: beta distribution
by Maurice Lombardi 30 Jun '00

30 Jun '00

Nathalie Jarosz a Ã©crit : > > >Well, if you have only the sources, you have first to compile these sources > >with a C compiler e.g. > >gcc, then to install the resulting libraries in a place where the linker > >can found them. Usually > >with a package come instructions on how to do that. If you have binaries > >(e.g within a redhat rpm > >package) they should be already where they belong to. > When I try to compile one of the sources, the following message appears: > "undefined first referenced symbol in file > ignlgi /var/tmp/crrliybX.o > log /var/tmp/crrliybX.o > pow /var/tmp/crrliybX.o > sqrt /var/tmp/crrliybX.o > exp /var/tmp/crrliybX.o > main /usr/local/lib/gcc-lib/sparc-sun-solaris2.2.95.2/crt1.o > spofa /var/tmp/crrliybX.o > ld:fatal: symbol referencing errors > No output written to a.out > collect2 : ld returned 1 exit status" What do you mean by compile "one" of the sources. C packages come with makefiles to handle the module dependencies and frequently a configure system to handle the difference between computers and OSes. You never have to compile files one at a time by hand. -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0

Re: beta distribution
by Nathalie Jarosz 30 Jun '00

30 Jun '00

>From: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> >To: Nathalie Jarosz <jarosz_n(a)hotmail.com> >Subject: Re: beta distribution >Date: Fri, 30 Jun 2000 13:14:23 +0200 >have you compiled using > >gpc -o test --autobuild test.pas -lrandlib > >the file librandlib.a or librandlib.so must also be in a place where it can >be found by the linker. I realize that maybe I have to do something with randlib because I don't have either lrandlib or librandlib.a... Do you know how to use this Randlib? ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

Re: beta distribution
by Nathalie Jarosz 30 Jun '00

30 Jun '00

>From: "Khimenko Victor" <gpc(a)khim.sch57.msk.ru> >To: jarosz_n(a)hotmail.com, gpc(a)gnu.de >Subject: Re: beta distribution >Date: Thu, 29 Jun 2000 20:40:28 +0400 (MSD) > > So I still have some questions... I have tried with a C routine and the > > pascal unit and program but it doesn't work. > >What exactly you done ? It's really trivial task if you know both C and >Pascal >and thus it's hard to guess where newbie without C knowleadge can fail... So, I would like to use a beta random deviates I have in C, in my pascal program. I have downloaded "randlib" which contain this function. In randlib.h, there is: extern float genbet(float aa, float bb); First, I have written beta.p : unit beta; interface function genbet(x,y:real);C; implementation end. Second, test.p: program betadev; uses beta; begin writeln(genbet(100,150)); end. Finally, I compile it with gpc and the following message appears: "undefined first referenced symbol in file genbet /var/tmp/cciCa09s1.o ld: fatal: symbol referencing errors No output written to test collect2 : ld returned 1 exit status" So... What is wrong? Thanks in advance, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

Re: beta distribution
by Nathalie Jarosz 30 Jun '00

30 Jun '00

>From: Peter Gerwinski <peter(a)gerwinski.de> >To: "Nathalie Jarosz" <jarosz_n(a)hotmail.com> >Subject: Re: beta distribution >Date: Wed, 28 Jun 2000 17:41:48 +0200 So I still have some questions... I have tried with a C routine and the pascal unit and program but it doesn't work. >In short: To use functions > > extern double foo (double x); > extern void bar (void); Where are these functions and in which form? Is it a C program or do I have to put it in the pascal unit or program? >you write a Pascal unit as follows: > > unit FooBar; > > interface > > function Foo (x: Real); C; > procedure Bar; C; > > implementation > > end. Same questions for this part. Is it a file named FooBar or FooBar.p or something else?... >Then your program can call the functions: > > program Something; > > uses > FooBar; > > begin > Bar; > writeln (Foo (42)) > end. > I guess that if I manage to define correctly the 2 previous parts, it will be ok... Thanks for help, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

3 2

Re: beta distribution
by Nathalie Jarosz 29 Jun '00

29 Jun '00

>From: Frank Heckenbach <frank(a)g-n-u.de> >To: gpc(a)gnu.de >Subject: Re: beta distribution >Date: Wed, 28 Jun 2000 17:46:47 +0200 >>OTOH, most of the routines in nrpas are fairly short, so it might be >easier to translate them to Pascal than to link the C routines. This one is quite long... I have tried to do it by this way but it seems to have a problem. That's why I try to find another solution... Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

Fwd: Re: beta distribution
by Nathalie Jarosz 29 Jun '00

29 Jun '00

>From: Peter Gerwinski <peter(a)gerwinski.de> >To: "Nathalie Jarosz" <jarosz_n(a)hotmail.com> >Subject: Re: beta distribution >Date: Wed, 28 Jun 2000 17:41:48 +0200 > >Hi, Nathalie! > > > I got the file `gpm.pas' but I don't really understand what I have to >do? > > Is it like a model to understand how to use something written in C in >order > > to compile it with gpc [...] > >Exactly. > >Some more instructions are in the GPC FAQ list. > >In short: To use functions > > extern double foo (double x); > extern void bar (void); > >you write a Pascal unit as follows: > > unit FooBar; > > interface > > function Foo (x: Real); C; > procedure Bar; C; > > implementation > > end. > >Then your program can call the functions: > > program Something; > > uses > FooBar; > > begin > Bar; > writeln (Foo (42)) > end. > >Hope this helps, > > Peter > >PS: Better continue asking questions about GPC on the GPC mailing >list, so everybody can profit from the answer. (Be welcome to >forward this email to the list.) > >-- >http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de >Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 >GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 >keys: http://www.gerwinski.de/pubkeys/ - AntiSpam: http://spam.abuse.net ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

1 0

None
by Nathalie Jarosz 28 Jun '00

28 Jun '00

Hello all! I have change of system: from linux, I am on a Unix workstation and when I compile program which used to work under linux, the following message appears: "Internal compiler error in 'emit_library_call_value', at calls.c:31" What does it mean? thanks a lot for your help, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

2 1

Re: beta distribution
by Frank Heckenbach 28 Jun '00

28 Jun '00

Peter Gerwinski wrote: > Nathalie Jarosz wrote: > > >You can call C version just fine (take look on GPM library and gmp.pas to > > >see > > >how pascal wrappers for C library can be written). > > Where can I find gpm library? > > A GPM unit is part of the GPC distribution. On my system if I type I think you're talking about gmp, not gpm (typed correctly 1 and false 3 times ;-). GMP (GNU Multi Precision) is a library for arithmetic with arbitrary precision. GPM is a library for text mode mouse handling under Linux (what does it stand for actually? M is for mouse, I guess)... > gpc -v > > I get the information: > > Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.95.1/specs > gpc version 20000619, based on 2.95.1 19990816 (release) > > >From this I read that can find the units in Only if you know something about the directory structure used by GPC, and a default installation is used. In general, `gpc --print-file-name=units' will print the unit directory if GPC can find it at all. > If you have another C library that exports the beta > distribution function you can use it the same way by writing a unit. OTOH, most of the routines in nrpas are fairly short, so it might be easier to translate them to Pascal than to link the C routines. 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

1 0

Re: beta distribution
by Nathalie Jarosz 28 Jun '00

28 Jun '00

>From: "Khimenko Victor" <gpc(a)khim.sch57.msk.ru> >To: njarosz(a)fr.packardbell.org, Maurice.Lombardi(a)ujf-grenoble.fr >CC: gpc(a)gnu.de >Subject: Re: beta distribution >Date: Sat, 24 Jun 2000 00:34:56 +0400 (MSD) > >>Gosh! If you have C version then why you need pascal version at all ? Because I am sorry but I don't know how it works and I don't know how to use something in C in pascal... >You can call C version just fine (take look on GPM library and gmp.pas to >see >how pascal wrappers for C library can be written). Where can I find gpm library? Thanks, Nathalie ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

2 1

Re: graphic
by Nathalie Jarosz 25 Jun '00

25 Jun '00

-----Message d'origine----- De : Peter Gerwinski <peter(a)gerwinski.de> Ã : Nathalie Jarosz <njarosz(a)fr.packardbell.org> Cc : gpc(a)gnu.de <gpc(a)gnu.de>; grx(a)gnu.de <grx(a)gnu.de> Date : vendredi 23 juin 2000 10:32 Objet : Re: graphic >> " 2) set the GRX font dir. >> " SET GRXFONT=<directory for the GRX fonts> >> " This is required for GRX graphics text output. Path: <GRX base>/fonts >> " NOTE: You can define a default font directory when compiling GRX. >> " E.g, if you installed the fonts in /usr/local/lib/grx/fonts add >> " CCOPT += -DGRX_DEFAULT_FONT_PATH="/usr/local/lib/grx/fonts" >> " to makedefs.gnu (Linux / GNU-make example) > >For Unix (optional): Put into your `.profile' something like: > > set GRX20DRV=xwin > set GRXFONT=/usr/local/lib/grx/fonts > >... or whereever you have installed the GRX fonts. Is it credible to put "/usr/src/grx-2.3.1/fonts"? >> " 1) Go to GRX base dir and check the makefile and makedefs file >> " for your system setup >> " 2) Switch to src sub dir and check the makefile >> What do you mean by check? >> " 3) run make -f <your makefile> >> " 4) if every thing worked fine go to <GRX base>/test, check the makefile >> " and build all test files / examples: >> " make -f <your makefile> >> Do I have here to put all the makefile.something? > >Under Linux with SVGAlib installed, you can also use: > > make -f makefile.lnx > I did this and the following message appears: "make[1]:entering directory '/usr/src/grx-2.3.1/src' gcc -c -06 -Wall -DLFB_BY_NEAR_POINTER -pipe -fomit-frame-pointer -I. -I. /include -I /include -I .. /addons/printdraw/bitblt.c -o draw /bitblt.o make[1] : gcc : command not found make[1] : *** [draw/bitblt.o] Error 127 make[1] : leaving directory 'usr/src/grx-2.3.1/src' make : *** [static_libs] error 2" What I have to do now? Thanks, Nathalie

3 2

Re: beta distribution
by Nathalie Jarosz 25 Jun '00

25 Jun '00

>it contains beta.pas (beta function), betai.pas (incomplete beta function which comes in F test), >and betacf.pas, an auxiliary function needed by betai.pas. What do you want exactly: reference ? I need something called "betadev" for beta deviation. I found it in C language but not in pascal.

2 1

Re: graphic
by Nathalie Jarosz 25 Jun '00

25 Jun '00

-----Message d'origine----- De : Peter Gerwinski <peter(a)gerwinski.de> Ã : gpc(a)gnu.de <gpc(a)gnu.de> Date : jeudi 22 juin 2000 18:48 Objet : Re: graphic > http://www.gnu.de/software/GRX/ I try to install GRX 2.3.1, I did not succeed: - "unpacking the GRX archive" was ok. - but "set the environment variables" was not: " 1) set the default driver and graphics mode info: " SET GRX20DRV=<driver> gw <width> gh <height> nc <colors> " (very useful but not required) " Available drivers are for " DOS : stdvga, stdega, et4000, cl5426, mach64, ati28800, VESA, " memory " Linux: svgalib, memory " X11 : xwin, memory " 2) set the GRX font dir. " SET GRXFONT=<directory for the GRX fonts> " This is required for GRX graphics text output. Path: <GRX base>/fonts " NOTE: You can define a default font directory when compiling GRX. " E.g, if you installed the fonts in /usr/local/lib/grx/fonts add " CCOPT += -DGRX_DEFAULT_FONT_PATH="/usr/local/lib/grx/fonts" " to makedefs.gnu (Linux / GNU-make example) I don't really understand what I have to do here? - "compiling GRX" was not ok as well: " 1) Go to GRX base dir and check the makefile and makedefs file " for your system setup " 2) Switch to src sub dir and check the makefile What do you mean by check? " 3) run make -f <your makefile> " 4) if every thing worked fine go to <GRX base>/test, check the makefile " and build all test files / examples: " make -f <your makefile> Do I have here to put all the makefile.something? Thank you for your help, Nathalie

2 1

Re: beta distribution
by Nathalie Jarosz 25 Jun '00

25 Jun '00

-----Message d'origine----- De : Frank Heckenbach <frank(a)g-n-u.de> Ã : gpc(a)gnu.de <gpc(a)gnu.de> Date : jeudi 22 juin 2000 23:16 Objet : Re: beta distribution >I downloaded nrpas from >ftp://garbo.uwasa.fi/pc/turbopas/nrpas13.zip >and it seems to contain beta distribution. Yes, I did to but beta distribution is not in. Is someone get something else? Nathalie

1 0

Re: beta distribution
by Frank Heckenbach 22 Jun '00

22 Jun '00

Nathalie Jarosz wrote: > >Hello, Nathalie and everyone! > > > >> Another question. I have some numerical recipies for pascal downloaded > from > >> a website but I don't have the program for a beta distribution. Is > someone > >> got it? > > > >I do not quite understand what you mean. Beta and alpha > >distributions of GNU Pascal can be found at: > > > > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ > > > >But you are probably asking for something different ... :-] > > yes, I am asking for mathematical routine in pascal which simulate beta > (statistical) distribution. > Is it more understandable? I downloaded nrpas from ftp://garbo.uwasa.fi/pc/turbopas/nrpas13.zip and it seems to contain beta distribution. 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

1 0

RE: graphic
by Mason Ip 22 Jun '00

22 Jun '00

OK, I got it thru. Look like -I/usr/X11R6/include pointed to no where on my box. After fixing fix, compilation proceeded. > ---------- > From: Mason Ip > Sent: Thursday, June 22, 2000 10:35 AM > To: 'gpc(a)gnu.de' > Subject: RE: graphic > > I got an error compiling it on Sparc Solaris 7 using gcc-2.95.1. > Any idea how I can fix it? > > grx-2.3.1> make -f makefile.x11 > make -C src STATIC=1 -f makefile.x11 > make[1]: Entering directory `/export/home/mip/tmp/grx-2.3.1/src' > gcc -c -O6 -Wall -fomit-frame-pointer -D__XWIN__ -I. -I./include > -I../include -I/usr/X11R6/include -I../addons/print -I../addons/bmp > mouse/xwininp.c -o mouse/xwininp.o > mouse/xwininp.c: In function `_XGrKeyboardGetKey': > mouse/xwininp.c:738: void value not ignored as it ought to be > make[1]: *** [mouse/xwininp.o] Error 1 > make[1]: Leaving directory `/export/home/mip/tmp/grx-2.3.1/src' > make: *** [static_libs] Error 2 > >

1 0

RE: graphic
by Mason Ip 22 Jun '00

22 Jun '00

I got an error compiling it on Sparc Solaris 7 using gcc-2.95.1. Any idea how I can fix it? grx-2.3.1> make -f makefile.x11 make -C src STATIC=1 -f makefile.x11 make[1]: Entering directory `/export/home/mip/tmp/grx-2.3.1/src' gcc -c -O6 -Wall -fomit-frame-pointer -D__XWIN__ -I. -I./include -I../include -I/usr/X11R6/include -I../addons/print -I../addons/bmp mouse/xwininp.c -o mouse/xwininp.o mouse/xwininp.c: In function `_XGrKeyboardGetKey': mouse/xwininp.c:738: void value not ignored as it ought to be make[1]: *** [mouse/xwininp.o] Error 1 make[1]: Leaving directory `/export/home/mip/tmp/grx-2.3.1/src' make: *** [static_libs] Error 2 > ---------- > From: Peter Gerwinski[SMTP:peter@gerwinski.de] > Sent: Thursday, June 22, 2000 9:48 AM > To: gpc(a)gnu.de > Subject: Re: graphic > > Hello, Nathalie and everyone! > > > I just wonder if it is possible to plot some graphs with pascal? > > If the answer is yes, how it works? > > You can use the GRX graphics library from GNU Pascal. > I just uploaded a new GRX snapshot - see: > > http://www.gnu.de/software/GRX/ > [snip]

1 0

Re: beta distribution
by Nathalie Jarosz 22 Jun '00

22 Jun '00

-----Message d'origine----- De : Peter Gerwinski <peter(a)gerwinski.de> Ã : gpc(a)gnu.de <gpc(a)gnu.de> Date : jeudi 22 juin 2000 18:39 Objet : Re: beta distribution >Hello, Nathalie and everyone! > >> Another question. I have some numerical recipies for pascal downloaded from >> a website but I don't have the program for a beta distribution. Is someone >> got it? > >I do not quite understand what you mean. Beta and alpha >distributions of GNU Pascal can be found at: > > ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ > >But you are probably asking for something different ... :-] yes, I am asking for mathematical routine in pascal which simulate beta (statistical) distribution. Is it more understandable? Nathalie

1 0

graphic
by Nathalie Jarosz 22 Jun '00

22 Jun '00

Hello all! I just wonder if it is possible to plot some graphs with pascal? If the answer is yes, how it works? And if not, how can I use my output files to easily generate graphs? Thanks for your help, Nathalie

3 2

beta distribution
by Nathalie Jarosz 22 Jun '00

22 Jun '00

Hello all again! Another question. I have some numerical recipies for pascal downloaded from a website but I don't have the program for a beta distribution. Is someone got it? thanks a lot in advance, Nathalie

2 1

Problem with last patch of grx23
by Maurice Lombardi 21 Jun '00

21 Jun '00

http://www.gnu.de/software/GRX/grx23.update.000520.gz 1 - it is not gzipped 2 - four hunks failed (with respect to the original grx23.zip, no update) in highlow.h grdriver.h makebase.dj and makefile.bcc two (in makebase.dj and makefile.bcc) contain "return return linefeed" instead of "return linefeed" as end of lines dtou solves that the other are cosmetic changes (some extra spaces to align consecutive lines) which seem different between your version of "original" grx23 and the one on simtelnet. The best is probably to make fresh new diffs rather than to try to modify the present diff file. 3 - more seriously, compiling tests on grx23 fails at the first file (arctest.c) for not finding GrLine. The problem seems that the src/bgi/line.c coming from bcc2grx (which is merged now) shadows in the merged library libgrx20.a the src/draw/line.c which comes from the original grx23 (and which contains the function GrLine() ). This was not a problem with the old setup where compiling with -lbcc2 -lgrx20 (for bcc2grx) or simply -lgrx20 for pure grx solved the problem. In fact looking to the output of the "ar -rv" command in the make command I see that indeed bgi/line.o is replaced (flagged r) instead of to be added (a). And the same is true for polygon.o fillpatt.o and fillpoly.o according to the same listing. Since the problem is with the filenames, not with the functions which they contain (the systematic prefix Gr in libgrx avoids that), I have renamed these four files (in src/bgi) as lineb.c polygonb.c fillpatb.c and fillpolb.c and modified accordingly src/stdobjs.mak. All compiles without problem now. All tests run perfectly except for one in bccbgi: the sierpinski test (i.e. the first floodfill test), while the snake test (the second floodfill) works. In looking to floodfill() contained in src/bgi/fldfill.c I see that you have changed the content of that function with respect to old BCC2GRX to call directly grx functions. If I restore the old content by replacing at the beginning of the floodfill() function: #if (GRX_VERSION_API-0)>=0x0225 by #if 0 everything works perfectly. I have not tried to understand further. 4 - A directory grx23/chr containing the .chr files (which are presently in src/bgi) should be included in order that the character tests work (or replace the BGI_PATH in the tests programs, but creating a chr directory analogous to the font directory seems better). 5 - I have tried the pascal tests. They work except for two problems which were already presents in previous versions of grx and bgi2grx. - pascal/bgi/demos/color.pas fails due to an invalid typecast between real and word. Replacing word() by a function realtoword() which rounds the real corrects it. - the polygon tests (DrawPoly and FillPoly) in pascal/bgi/demos/demo.pas fail due to a problem when transferring "open arrays" parameters between pascal and C for recent alphas of gpc. gpc pushes in that case an extra parameter on the stack so that "var Polypoints: array of PointType" in pascal is no more equivalent to "PointType *Polypoints" in C, because C pushes only the address of Polypoints. The trick is to use in the pascal unit an untyped variable "var Polypoints" which pushes also only the address of Polypoints on the stack. With this correction the demo program works perfectly. It is necessary to change that way pascal/bgi/bgi2grx.pas and also pascal/grx20.pas (I have no test program at hand to check in that case however). Hope this helps. -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

2 1

Debugging GPC compiled code with GDB
by Pierre Muller 16 Jun '00

16 Jun '00

I got the djgpp binary distribution of GPC and made some tests with my pascal aware GDB. But if I compile a simple program (similar to hello word ) and a start GDB and insert a breakpoint at main (which is what allmost vevery body would do in C, and that works as expected with Free Pascal compiled code) If I then use "run" the program stops at the end of the main code, which is rather odd! If this a known problem and is it or will it be fixed. The source code used follows I wanted to test the internal form of string to see if I could support it ! program test_gpc(input,output); type string32 = string[32]; var s1, s2 : string32; begin s1:='It '; s2:=s1+'works'; Writeln('It works'); Writeln(s2); end. Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

2 1

Re: Debugging GPC compiled code with GDB
by Pierre Muller 16 Jun '00

16 Jun '00

> the program stops at the end of the main code, which is rather odd! Whoops, it seems that this was due to a problem of wrong linker or gcc version recompiling from djgpp bin dir gives something a little bit better : the main break works and the program is indeed stopped before the main procedure but nevertheless main has no line info and thus "next" command will go right to the end ! Couldn't the startup code be integerate at begin of the main code directly ? This way "next command would stop at the begin of the line s1:='It'; > program test_gpc(input,output); >type > string32 = string[32]; >var >s1, s2 : string32; >begin > s1:='It '; > s2:=s1+'works'; > Writeln('It works'); > Writeln(s2); >end. Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

1 0

None
by FSR SoWi 16 Jun '00

16 Jun '00

unsubscribe gpc

1 0

Solaris 7 Sparc binaries of GPC
by Anuradha 15 Jun '00

15 Jun '00

Hello, When we use this zip file from the directory you specified.We are not able to understand it. For eg.,It says, "From a directory of your choice (e.g.@: @file{/usr/local/src}), unpack the GNU CC and GNU Pascal source distributions. This will create separate subdirectories for GCC and GPC." Where are the source distrinbutions then? Thanks and regards, Anuradha > Subject: Solaris 7 Sparc binaries of GPC > From: mariusz(a)math.uwb.edu.pl > To: NAGARAJ.BATNI/OU=DCCH1(a)bt0200.net.alcatel.be > > Nagaraj Batni wrote: > > > > Hello , > > > > We tried downloading the package from the site you had mentioned > > Nice to know that my packages are usefull. Thanks. > > > But when i unzip it with gunzip it gives a error message saying "invalid > > compressed data--format voilated".gtar is not working in my system. > > Solaris 7 comes with unzip, so I put this package into zip archive. > It is available at: > > > ftp://mizar.uwb.edu.pl/pub/misc/solaris7/sparc/gpc-2.1-19991030-Solaris7-sparc.pkg.zip > > Hope you will get it working > > -- > . > Mariusz Zynel > > Institute of Mathematics | phone: +48 (85) 745 75 52 > University of Bialystok | > Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl > 15-267 Bialystok | > Poland | http://math.uwb.edu.pl/~mariusz/

2 1

None
by FSR SoWi 15 Jun '00

15 Jun '00

unsubscribe

1 0

Re: [Fwd: Re: Absolute in Pascal]
by Frank Heckenbach 15 Jun '00

15 Jun '00

Maurice Lombardi wrote: > 1 - djgpp is a linear frame 32 bits system. It does not know about Segment:Offset addresses. > > 2 - djgpp is a protected mode system libe BP (not TP): The address even in BP would be Selector:Offset instead of > Segment:Offset. You would need to replace Const BiosSeg=$40 by Const BiosSeg=seg0040 (BP takes care to put the correct > selector instead of $40 in seg0040). > > 3 - there are a lot of functions to address physical memory in the djgpp's libc: look at _dpmi... functions by info > libc. > But probably the simplest would be to look to _far* functions (_farpeekb etc...) to peek/poke values at such addresses > with a minimum effort. You just have to declare these functions in your pascal program with asmname to make them known, > e.g. > > function farpeekb(selector:ShortWord; offset:MedWord): byte; asmname "_farpeekb"; > > please read carefully the explanation in the _far* section of the info libc on how to use these functions (get > selectors...) Besides, if you want to get the screen size, you can use `ScreenSize' in the CRT unit. For other things where you need to access BIOS variables in TP, there are also Pascal routines available in GPC. 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

1 0

[Fwd: Re: Absolute in Pascal]
by Maurice Lombardi 15 Jun '00

15 Jun '00

-------- Original Message -------- Objet: Re: Absolute in Pascal Date: Thu, 15 Jun 2000 12:33:10 +0200 De: Maurice Lombardi <Maurice.Lombardi(a)ujf-grenoble.fr> A: Penza Kenneth at MITTS <kenneth.penza(a)magnet.mt> RÃ©fÃ©rences: <JA8AAAAABE1ZiAABYQABlXwdgctU(a)magnet.mt> Penza Kenneth at MITTS a Ã©crit : > > I am tring to compile a unit that defines some bios variable which does compile > under TP 7.0. However when I use gpc I get the following messages. > > bios.pas:18: warning: variables at absolute adresses may cause problems > bios.pas:18: missing semicolon > bios.pas:18: parse error before `:' > > Part of the coding is as follows. > INTERFACE > CONST BiosSeg = $40; > > VAR > ScrnCols : BYTE ABSOLUTE BiosSeg :$4a; 1 - djgpp is a linear frame 32 bits system. It does not know about Segment:Offset addresses. 2 - djgpp is a protected mode system libe BP (not TP): The address even in BP would be Selector:Offset instead of Segment:Offset. You would need to replace Const BiosSeg=$40 by Const BiosSeg=seg0040 (BP takes care to put the correct selector instead of $40 in seg0040). 3 - there are a lot of functions to address physical memory in the djgpp's libc: look at _dpmi... functions by info libc. But probably the simplest would be to look to _far* functions (_farpeekb etc...) to peek/poke values at such addresses with a minimum effort. You just have to declare these functions in your pascal program with asmname to make them known, e.g. function farpeekb(selector:ShortWord; offset:MedWord): byte; asmname "_farpeekb"; please read carefully the explanation in the _far* section of the info libc on how to use these functions (get selectors...) Hope this helps -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0

Pascal support in GDB
by Pierre Muller 15 Jun '00

15 Jun '00

I just want to send you a note that I started to integrate pascal language support inside GDB. ( I now have "Write after approval" rights in the cygwin main GDB cvs tree and I just committed 4 new files specific to pascal language). I already mentionned several time that I have patches to add pascal support for GDB, but I never got any feedback from the GNU pascal team. (I am one of the developpers of Free Pascal Compiler, another GPL pascal compiler). Does any of you use GDB to debug pascal code? Where annoyed by getting some "unknown type 10" error? Currently my patches only support Free Pascal strings and I have no idea of the current support of pascal string in GNU pascal, could someone please enlight me? Pierre Muller Institut Charles Sadron 6,rue Boussingault F 67083 STRASBOURG CEDEX (France) mailto:muller@ics.u-strasbg.fr Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99

4 6

Absolute in Pascal
by Penza Kenneth at MITTS 15 Jun '00

15 Jun '00

I am tring to compile a unit that defines some bios variable which does compile under TP 7.0. However when I use gpc I get the following messages. bios.pas:18: warning: variables at absolute adresses may cause problems bios.pas:18: missing semicolon bios.pas:18: parse error before `:' Part of the coding is as follows. INTERFACE CONST BiosSeg = $40; VAR ScrnCols : BYTE ABSOLUTE BiosSeg :$4a; Can anyone please tell me how can I rectify this problem. Thanks

1 0

Re: Pascal support in GDB
by Frank Heckenbach 14 Jun '00

14 Jun '00

Maurice Lombardi wrote: > from the (old) gpc info file: > > The string type in gpc is something equivalent to > > TYPE > STRING = RECORD > Capacity : integer; > length : integer; > string : packed array [ 1..Capacity ] of char; > END; > > In fact I suppose that it is actually cardinal (identical to word), i.e. "unsigned int" in C (this doc is somewhat > outdated). Indeed. The current declaration is: type String (Capacity : Cardinal) = record Length : 0 .. Capacity; Chars : packed array [1 .. Capacity + 1] of Char end; (We added one extra char for easy conversion to CStrings.) > Of course gpc strings can contain any number of #0 inside the actual length. > > On the other hand Pchar exists, with an equivalent (but more understandable) Cstring, to enable interface with C system > functions, and there are lots of conversion functions between the two, but you don't need to know for GDB interface, > they are just like other functions. Yes. There can be no #0's inside CStrings. Of course, they can be stored there -- but then they signify the end of the string, like in C... 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

1 0

upload ?
by Maurice Lombardi 07 Jun '00

07 Jun '00

Hallo Somebody ("Barry Hanley" <Eagles7(a)btinternet.com>) in the comp.os.msdos.djgpp had problems with gpc under djgpp, presumably due to inconsistent versions of gpc and gcc. He has gcc 2.9.5.2 and all djgpp binaries on agnes are for gcc 2.8.1 Rather than asking him to downgrade gcc it would prefer to give him my compiled binary: gpc-19991030-gcc-2952-djgpp.zip But how to do that ? The file is too large to be attached to a mail. I have no more any ftp server in my lab, all have been closed last week after a security problem. I tried to upload to the incoming directory in agnes, but this is forbidden (at least for anonymous). Is there any way to do that ? -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

1 0

Manpage
by Frank Heckenbach 06 Jun '00

06 Jun '00

Hi, while updating the GPC Manual, Peter and I came accross the manpage. Though I removed most of the fossils from it, we don't have the time to maintain the manpage and to document, e.g., all the options there (as they are now in the manual), and we don't really know the format... Would anyone like to take over the maintenance of the manpage, or does anyone know of tools to generate it automatically from, say, Texinfo? (texi2roff might do, but I don't know much about it, and don't have an actual example to show, e.g., which Texinfo commands to use for `SYNOPSIS' etc. and for highlighting...) Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: copyright
by Frank Heckenbach 06 Jun '00

06 Jun '00

Russ Whitaker wrote: > Text version of old faq was released without copyright notice. > Think it was because texi wants 2 copies of copyright - one for > texinfo and the other for TeX. > > So my question is - how should the copyright notice read for the > new faq? Unless you object, I'd like to integrate the FAQ into the manual. This means, it will become one chapter of it (in the Info, HTML, and DVI and PostScript versions), and the text file `FAQ' will be extracted from it with `makeinfo' (just as is done for `INSTALL' and other files already). In this case, I think it should be sufficient if you add a header like the following (which I added to the other chapters of the manual) to the start of the file (replace the authors and dates, of course :-). gpc.texi is the "root" file of the manual, and contains the 2 copies of copyright, and faq.texi will be put in the same directory then. @c Copyright (C) 1999-2000 Free Software Foundation, Inc. @c For copying conditions, see the file gpc.texi. @c This file is part of the GPC Manual. @c @c Authors: Peter Gerwinski <peter(a)gerwinski.de> @c Frank Heckenbach <frank(a)pascal.gnu.de> @c @c Last modification: 26 May 2000 (file up to date) 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

1 0

copyright
by Russ Whitaker 06 Jun '00

06 Jun '00

Hi Text version of old faq was released without copyright notice. Think it was because texi wants 2 copies of copyright - one for texinfo and the other for TeX. So my question is - how should the copyright notice read for the new faq? Russ <russwhit(a)mind.net>

1 0

RE: URGENT: Pascal Clock -
by Wren Lee 05 Jun '00

05 Jun '00

I have this routine that will extract the processor time on a Linux based PC. It's written in C but I'm sure it could be converted, or at least linked in. extern __inline__ unsigned long long int rdtsc() { unsigned long long int x; __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x)); return x; } This routine will return the number of processor cycles since system boot, an in order to make any sense of it you need to know your system CPU clock speed. Regards, Lee. > -----Original Message----- > From: Raymond Wang [SMTP:rayw@wireless.stanford.edu] > Sent: 03 June 2000 11:23 > To: gpc(a)gnu.de > Subject: URGENT: Pascal Clock > > Hi, > > When I compile my pascal code with GNU Pascal's compiler, I get > undeclared > identifier `Clock' when I reference it in my code: > > e.g. y := clock/1000-y1 > > I thought Clock is a predefined global function. What should I do in > order > for the compiler to recognize the clock command? > > Thanks! > Ray > - - - - - - - - - - - - - > Raymond Wang > Department of Electrical Engineering > Stanford University > > www.stanford.edu/~rayw -- The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful.

1 0

Re: unsubscribe
by Clyde Meli 04 Jun '00

04 Jun '00

> Clyde Meli wrote: > > > > The hut.fi came from the reply header, so perhaps it needs to be > > updated. > > Huh? There is no reply header unless you set one. Sorry :) My unix mailer replied to the from header then. > > (Before anyone asks: This is intentionally so. > See: http://www.unicom.com/pw/reply-to-harmful.html) > > > You are right about the fact that it would have flagged/ > > rejected these emails also. IMHO it's worth it. > > Okay. Any objections? > > Peter > Let me suggest an alternative: adding something to the subject line which would identify the email as from the gpc list. We subscribers would know that the unsubscribe request is for the gpc list for example since the subject would be: *gpc* unsubscribe (or something similar). Regards, Clyde

1 0

Re: unsubscribe
by Clyde Meli 04 Jun '00

04 Jun '00

> Clyde Meli wrote: > > Sorry, can't the gpc majordomo automatically flag unsubscribe requests, > > rather than send them to everyone on the list? > > It could do so but then it would also have sorted out these two > emails which contain "unsubscribe" somewhere at the beginning of > the body. > > Any votes? > > Peter > > PS: It's <gpc(a)gnu.de> now. > <gpc(a)hut.fi> still works but should not be used any longer. The hut.fi came from the reply header, so perhaps it needs to be updated. You are right about the fact that it would have flagged/ rejected these emails also. IMHO it's worth it. Regards, Clyde

1 0

Re: unsubscribe
by Peter Gerwinski 04 Jun '00

04 Jun '00

Clyde Meli wrote: > > The hut.fi came from the reply header, so perhaps it needs to be > updated. Huh? There is no reply header unless you set one. (Before anyone asks: This is intentionally so. See: http://www.unicom.com/pw/reply-to-harmful.html) > You are right about the fact that it would have flagged/ > rejected these emails also. IMHO it's worth it. Okay. Any objections? Peter -- http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 keys: ftp://ftp.gerwinski.de/pub/keys/ - AntiSpam: http://spam.abuse.net

1 0

Re: unsubscribe
by Clyde Meli 04 Jun '00

04 Jun '00

> unsubscribe > Sorry, can't the gpc majordomo automatically flag unsubscribe requests, rather than send them to everyone on the list? Just a minor suggestion... Regards, Clyde

2 1

Re: URGENT: Pascal Clock
by Frank Heckenbach 04 Jun '00

04 Jun '00

Raymond Wang wrote: > I see what the problem is: I'm using GNU Pascal as opposed to DEC VAX > Pascal (where clock is a global function defined below). > > Does anyone know a way to mimic this "clock" in GNU Pascal? (I apologize > for my lack of Pascal knowledge!) No problem (it's nothing to do with Pascal in general, anyway -- as Peter noted, the only predefined routines to deal with time in Pascal are GetTimeStamp etc., but they measure real time, not CPU time). As I said in my last mail, if you have a not too old GPC release, you can use GetCPUTime. (In contrast to VAX Pascal, the result is not "most likely" in 10ms intervals, but definitely in seconds and microseconds. :-) So, if you want a "most likely";-) VAX Pascal compatible `Clock' routine, you can use the following code. (I use `LongInt' for the return value just in case -- `Integer' would be good for 2^31/100/86400 ~ 249 days.) The demo program shows that really CPU time is measured, i.e., `Sleep' doesn't take up time, but the loop does. program Foo; uses GPC; { Compatible to VAX Pascal. Result is in 10ms intervals. } function Clock : LongInt; var Second, MicroSecond : Integer; begin Second := GetCPUTime (MicroSecond); Clock := 100 * LongInt (Second) + MicroSecond div 10000 end; var i : Integer; begin Writeln (Clock); Sleep (1); Writeln (Clock); for i := 1 to 100000000 do; Writeln (Clock); end. 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

1 0

Re: URGENT: Pascal Clock
by Raymond Wang 03 Jun '00

03 Jun '00

I see what the problem is: I'm using GNU Pascal as opposed to DEC VAX Pascal (where clock is a global function defined below). Does anyone know a way to mimic this "clock" in GNU Pascal? (I apologize for my lack of Pascal knowledge!) e.g. y := clock/1000-y1 Source:http://www.openvms.digital.com/wizard/group3/335.HTML Ask the Wizard Questions PASCAL Language: PASCAL CLOCK The Question is: What is the granularity of the CLOCK command in VAX PASCAL, also, what units does it measure? The Answer is: According to the DEC Pascal Language Reference Manual: " 8.21 CLOCK Function The CLOCK function returns an integer value indicating the amount of central processor time (in milliseconds) used by the current process. This function does not have a parame- ter list. The result of CLOCK includes the amount of central processor time allocated to all previously executed images." That being the case, the value is most likely taken from the system clock which is incremented at 10ms intervals - hence the granularity will be 10ms. A simple program seems to support this: PROGRAM CheckClock(OUTPUT); VAR LastTime,NextTime : INTEGER; BEGIN LastTime:=CLOCK; REPEAT NextTime:=CLOCK; UNTIL LastTime <> NextTime; WriteLn('LastTime = ',LastTime,' NextTime = ',NextTime); END. $ run checkclock LastTime = 3495890 NextTime = 3495900 Note however that the granularity may vary in future as OpenVMS is capable of expressing times to an accuracy of 100ns. - - - - - - - - - - - - - Raymond Wang Department of Electrical Engineering Stanford University www.stanford.edu/~rayw

1 0

Re: URGENT: Pascal Clock
by Frank Heckenbach 03 Jun '00

03 Jun '00

Peter Gerwinski wrote: > Hi, Raymond Wang, > > you wrote: > > When I compile my pascal code with GNU Pascal's compiler, I get undeclared > > identifier `Clock' when I reference it in my code: > > > > e.g. y := clock/1000-y1 > > > > I thought Clock is a predefined global function. > > It is not. > > > What should I do in order > > for the compiler to recognize the clock command? > > If `Clock' stands for what the name suggests, you can write your > own one using the `Date' and `Time' routines. Please search the > documentation for these words and `GetTimeStamp'. These routines return real time. If you want to get processor time (like clock() in C), try GetCPUTime instead (only available in recent GPC versions). 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

1 0

URGENT: Pascal Clock
by Raymond Wang 03 Jun '00

03 Jun '00

Hi, When I compile my pascal code with GNU Pascal's compiler, I get undeclared identifier `Clock' when I reference it in my code: e.g. y := clock/1000-y1 I thought Clock is a predefined global function. What should I do in order for the compiler to recognize the clock command? Thanks! Ray - - - - - - - - - - - - - Raymond Wang Department of Electrical Engineering Stanford University www.stanford.edu/~rayw

2 1

HELP! Running Pascal 'exe's in Unix
by Anuradha 03 Jun '00

03 Jun '00

Hello , I tried downloading full.exe for installation of Cygnus. ftp://sunsite.auc.dk/pub/cygwin/cygwin-b20/ and then the GPC from ftp://agnes.dida.physik.uni-essen.de/pub/home/chief/gpc-20000401-i686-pc-cygwin.zip I tried compiling the pascal programs that came along in windowsNT and run it in unix environment. The compilation was fine but it didn't run. Should i compile them under unix environment,say Linux? Can somebody tell me how to run them? COMPILING PROGRAMS THAT USE UNITS : I am not able to give units directory though i change the setupgpc.bat .It says files not found. COMPILING PROGRAMS THAT USE WINAPI The compilation indicates that winapi doesnot exist. LINKING OBJECTS I tried giving -fautolink as one of the compile parameters but it doenot work. Where do i find the list of compile parameters?I find many in readme.text but i find different ones in setupgpc.bat. Thanks in advance . Regards, Anuradha

4 3

Re: HELP! Running Pascal 'exe's in Unix
by Anuradha 01 Jun '00

01 Jun '00

Hello, May i know where i can find binaries for compiling pascal sources on Solaris system / Linux? Regards, Anuradha. African_Chief(a)bigfoot.com wrote: > On 1 Jun 2000, at 14:51, Anuradha wrote: > > > Hello , > > > > Thankyou for responding. > > Probably i have the wrong environment and the compiler. > > I am in the look-out for a compiler that can compile pascal programs > > and makes 'exe's that can run on Unix. I am not particular about > > compiling the pascal programs in windows.I can also compile them in > > Linux/Unix.Is it enough if i install Linux on my system? > > Like I said, there are (old) Linux binaries on agnes. Check in the > 'beta' directory (or is it 'alpha'?). There are also binaries for some > unix platforms (e.g., Solaris). You have given no indication as to the > unix platform that you are using. It may be that binaries already exist > for that platform (others will be able to tell you). On the other hand, > you may need to download the GPC and GCC sources and compile > GPC yourself. > > > Thankyou in advance . > > Regards, > > Anuradha > > > > PS : Should i have directed this message to the maillist? > > Yes. > > Best regards, The Chief > ----- > Dr Abimbola A Olowofoyeku (The African Chief) > Email: African_Chief(a)bigfoot.com > Author of Chief's Installer Pro v5.22 for Win32 > http://www.bigfoot.com/~African_Chief/chief32.htm

2 1

Unit-path and uses 'winapi'
by Anuradha 30 May '00

30 May '00

Hello, Unit-directory : When i change the unit-path in the setupgpc.bat , it doesnot seem to take up the units from the changed directory.I did the compile of the build.pas as mentioned in the readme.txt.But still it doenot compile with those units.So,I am putting the units in the working directory itself. Winapi : I get an error in the units that use 'winapi'.How do i change them. Thank you. Regards, Anuradha

1 0

Re: posible bug question...
by Frank Heckenbach 29 May '00

29 May '00

J. David Bryan wrote: > Nearly. ;-) I believe item "g" actually refers to this case: > > for i := 1 to 10 do > for i := 11 to 20 do ; > > The second for-statement is contained in the first and threatens the first > for-statement's control variable, and so is illegal by item "g". Alright, this makes sense. > > Yes, but is a goto into a loop legal at all (the last sentence of > > 6.9.2.4 seems to indicate not to me, but I'm not completely sure)? > > [...] > > (c) S is a statement of the statement-sequence of the > compound-statement of the statement-part of a block containing G." Wow, 4 "of"s in a row! ;-) > Item "b" appears to be the key, as the question fails items "a" and "c". > Going out of a for-statement is legal: > > for i := 1 to 10 do > goto 1; > 1: ; > > ...because the for-statement (part of the statement-sequence containing G) > and the null-statement (S) are both part of the same statement-sequence. > However, going into a for-statement is not legal: > > goto 1; > for i := 1 to 10 do > 1: ; > > ...because the null-statement (S) is not part of the statement-sequence > containing the goto-statement (the statement-sequence containing the goto- > statement consists of the goto-statement and the for-statement but *not* > the null-statement). > > It took me three days of head-scratching to decide this, so I hope I am > correct (this time)! I hope so, too -- it does make sense, after all... 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

4 5

ok!
by Nathalie Jarosz 27 May '00

27 May '00

Hi again again! I manage to get my e_mail back. So, don't take into account my previous mail! Thanks a lot for your numerous answers about random, I will try immediately! Nathalie

1 0

random again
by Nathalie Jarosz 27 May '00

27 May '00

Hi! Could you send me again your answer because I had troubles with my e_mail yesterday.. thanks, Nathalie

1 0

Re: random
by Frank Heckenbach 26 May '00

26 May '00

Marco van de Voort wrote: > > In GPC, in may be very large, e.g.: > > <snip> > > > a := Random (1000000000000000000); > > Random has a 64-bit definition? Or both 64 and 32 with overloading? The internal RNG is 32 bit, but is a 64 bit number is wanted, Random calls it twice. The `Random' function is overloaded (with compiler magic) for LongestReal and LongestCard (i.e., the longest available real and (unsigned) integer types -- this may by 64 bit, or 128 bit on 64 bit systems). 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

1 0

Re: random
by Frank Heckenbach 26 May '00

26 May '00

George Shapovalov wrote: > var N:any_integer_type; (may be not extended (very large) integer integer) > random(N); would return integer type in the range 0..N-1 In GPC, in may be very large, e.g.: program Foo; var a : LongInt; begin a := Random (1000000000000000000); Writeln (a) end. > random; (without parameters) would return float in the range 0..1. (with 0 inclusively and 1 exclusively) 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

random
by Nathalie Jarosz 26 May '00

26 May '00

Hi, I'd like to use random numbers generator. Is someone knows some efficient procedures or functions in pascal? Thanks a lot in advance for your help, Nathalie

4 3

Re: revised faq
by Frank Heckenbach 26 May '00

26 May '00

Hi, after Russ Whitaker has updated the FAQ (thanks!), I've discovered a problem: The old version of the FAQ was written in Texinfo. A version translated to ASCII was distributed with GPC, and that's proabably all you've seen, Russ, and consequently edited this version. Now, it would be nice to have the current FAQ in Texinfo format again. Then we could, e.g., provide an HTML version on the GPC home page and include it into GPC's documentation (and it could also contain direct cross-links to the various URLs and to other Info files, e.g. the DJGPP FAQ). So, would you be willing to convert the FAQ back to Texinfo? This would be greatly appreciated. FYI, a Texinfo version of the old FAQ can be found at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpc-faq-0.4.tar.gz (in case you want to check how some formatting was done there, etc.) 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

1 0

Re: possible bug question...
by Frank Heckenbach 25 May '00

25 May '00

Russ Whitaker wrote: > Does the Standards Committiee still exist? I think the members meet at irregular time intervals. Some (or at least one) of them is reading c.l.p.a-i, so you might want to post there... > It would be nice to > start the ball rolling tward a rewrite, even if nothing more than > a conversion into real english. Unlikely. However, be invited to help improving the GPC documentation where real English descriptions of this and many other features are urgently needed. 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

1 0

Re: possible bug question...
by Russ Whitaker 25 May '00

25 May '00

Hi Sounds like someone tried to define Pascal by using a Flow Chart and someone else converted the Flow Chart itself into english :-) Does the Standards Committiee still exist? It would be nice to start the ball rolling tward a rewrite, even if nothing more than a conversion into real english. In the meanwhile, just for fun patched the original program that started this thread: program prime1; {find prime numbers up to 100} var i,j,k: integer; begin for i := 2 to 100 do begin k := 0; for j := 2 to i do if i mod j = 0 then begin k := j; break; end; if k = i then writeln( k ); end; end. It prints out 25 prime numbers 2,3,5, ... ,97 useing 1158 passes through the inner loop. program prime2; {find prime numbers up to 100} var i,j: integer; k: boolean; begin for i := 2 to 100 do begin k := false; j := 1; repeat inc( j ); if i mod j = 0 then k := true; until( k or ( j > sqrt( i ))); if not k or ( j = i ) then writeln( i ); end; end. It prints out the same list useing 261 passes Russ <russwhit(a)mind.net>

1 0

Re: posible bug question...
by Frank Heckenbach 24 May '00

24 May '00

J. David Bryan wrote: > On 20 May 2000, at 9:31, Russ Whitaker wrote: > > > So what does the Pascal specs say? > > The Extended Pascal standard, section 6.9.3.9.1, says: > > "After a for-statement is executed, other than being left by a > goto-statement, the control-variable shall be undefined." > > That's remarkably clear. :-) That means that variable "b" in the code > below isn't guaranteed to be true: In fact, i = 10 in the current GPC version (but don't rely on it :-). > procedure p; > var i : integer; > b : Boolean; > begin > for i := 1 to 10 do ; > b := (i > 10); > end; > The next part of the standard is a bit less clear: > > "Neither a for-statement nor any procedure-and-function-declaration-part > of the block that closest-contains a for-statement shall contain a > statement threatening (see 6.9.4) a variable-access denoting the > variable denoted by the control-variable of the for-statement." > > I believe that says that you can't modify the control variable of a for- > statement (a "threat" is defined in the standard as one of ten ways that a > variable may be assigned a value). Including a `for' statement (item g :-). Therefore I conclude that a `for' statement by itself is illegal in Pascal. Alright, we'll take it out of the next GPC release. Just kidding... > So this would clearly be illegal: > > procedure p; > var i : integer; > begin > for i := 1 to 10 do > i := 11; > end; > > However, it also says that a block containing a for-statement cannot > contain a threat to the control variable. In other words, this would be > illegal too: > > procedure p; > var i : integer; > begin > i := 0; > for i := 1 to 10 do > end; > > I suppose the reason is to disallow something like this: > > procedure p; > var i : integer; > label 1, 2, 3; > begin > goto 1; > 2: i := 11; > goto 3; > > 1: for i := 1 to 10 do > begin > goto 2; > 3: > end > end; > > ...which is functionally equivalent to the second code example. Yes, but is a goto into a loop legal at all (the last sentence of 6.9.2.4 seems to indicate not to me, but I'm not completely sure)? If it is legal, what should the following code do? procedure p; var i : integer = 42; label 1; begin goto 1; for i := 1 to 10 do begin 1: Writeln (i) end end; > So it would seem that to comply with the EP standard, GPC must prohibit any > threat (i.e., variable assignment) to a for-statement control variable > anywhere within the scope of that variable, and not just within the for- > statement itself. This would mean that the loop variable could practically not be used outside of the for loop. If this is really true, I'd really favour a syntax that makes this clear (like `for i : Integer = 1 to 10 do ...'), so i has only the corresponding scope. 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

3 2

Re: posible bug question...
by Frank Heckenbach 24 May '00

24 May '00

J. David Bryan wrote: > Hello Marco, > > I have copied my reply to the list. > > > On 21 May 2000, at 15:56, Marco van de Voort wrote: > > > Or do they mean: > > > > procedure x; > > > > var i : integer; > > > > procedure nestedx; > > > > begin > > i:=5; > > end; > > > > begin > > for i:=1 to 5 do nestedx; > > end; > > I believe you are correct, and my original reading that: > > i := 0; > for i := 1 to 10 do ; > > was incorrect is itself incorrect. The key part of the statement in the > standard is that the "...procedure-and-function-definition part of the > block that closest-contains a for-statement..." cannot threaten the control > variable. In your example, the "procedure x" block (the second begin-end > block) is the "block that closest-contains a for-statement." Therefore, > your first block, that of "procedure nestedx", forms the "procedure-and- > function-definition-part of the block...." > > So your example breaks the requirement listed in the standard, meaning your > interpretation is correct. In my example, the threat ("i := 0") is not in > either the for-statement nor the procedure-and-function-definition part, so > it is legal. I see. So `for' statement are not illegal by themselves in Pascal, I'm relieved. ;-) Checking all this seems quite difficult, but at least in principle possible... 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

PPC
by f.c. kuechmann 24 May '00

24 May '00

Has anyone compiled gpc to run on PowerPC platforms under LinuxPPC? I'd hate to go to the trouble if somebody already did it. Cheers fk

1 0

Re: revised faq
by Frank Heckenbach 23 May '00

23 May '00

Russ Whitaker wrote: > Attached is a .gz file. It should look ok. Yep. > > (Note: The syntax given here is valid for GPC releases of May 2000 > > and newer.) > > > ok entered change > visited agnes earlier today - No May releases yet. I didn't claim there were any. ;-) (Which means that the syntax doesn't yet work with the existing releases, but since I expect Peter to make the next release soon, I think we can put this forward-looking information in the FAQ already.) Since there were no more comments (besides the ones by The Chief and mine which you've integrated), I'm putting this version of the FAQ into the GPC distribution now. In the future, you will be able to put updates into the distribution yourself via CVS. (Please contact Peter after he's announced the CVS server.) 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

1 0

Re: revised faq
by Russ Whitaker 23 May '00

23 May '00

Hi Andreas Jaeger writes> > >>>>> Russ Whitaker writes: > > Mandrake is NOT compatible with RedHat despite claims - you need less > > manual tweaks then in case with SuSE or Debian but ONLY RedHat is > Why do you need manual tweaks at all with SuSE? SuSE 6.4 ships with: > rpm -q -f /usr/bin/gpc > gpc-2.95.2-19 > (Version from October 1999) > Any given binary should install easily on the target it was intended for. Any other target you may have problems. For instance, SuSE 5.1, 5.2, 6.1, 6.2 did not have GPC, so you might run into problems trying to install the SuSE 6.4 package into a 5.1 box. Russ <russwhit(a)mind.net>

1 0

Re: revised faq
by Frank Heckenbach 23 May '00

23 May '00

Khimenko Victor wrote: > > {$ifdef DJGPP} > > var > > MinStackSize : Cardinal = $200000; asmname '_stklen'; > > {$endif} > > Hmm. If here we said about DJGPP's stack handling perhaps setrlimit(2) and > ulimit from bash(1) should be mentioned as well ? In SVr4 and BSD 4.3-based > systems (including Linux) you can raise stack size limit via setrlimit(2) in > run-time or from bash's command line BEFORE starting program with ulimit -s ... > Of course in Linux you'll need not `array[1..4000000] of byte' but > `array[1..10000000] of byte' to get exception (with default 8MiB limit) but > anyway ... That's one difference. The main difference, of course, is that a Linux user can set the stack size on the command line (and if s/he or the admin limits it, they might have their reasons, so a program probably should not usually override it) while under DJGPP the stack size has to be written into the executable (and the whole stack has to be allocated in physical memory at program startup due to a weakness of the DPMI specification), so one cannot just set it to some large value without problems. Finally, the method of setting the stack size is quite different (DJGPP: declare a constant(*) with a certain asmname; Unix: call a function at any time), so these are almost completely different matters, IMHO. Now, I wouldn't object to putting the information for Unix into the FAQ, but since the DJGPP information is in the DJGPP specific section, one would have to find a suitable place for it... (*) I wrote `var', but it should rather be `const'. Russ, can you please change it in the FAQ? 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

1 0

Re: posible bug question...
by Frank Heckenbach 23 May '00

23 May '00

Maurice Lombardi wrote: > Frank Heckenbach a Ã©crit : > > This would mean that the loop variable could practically not be used > > outside of the for loop. If this is really true, I'd really favour a > > syntax that makes this clear (like `for i : Integer = 1 to 10 do ...'), > > so i has only the corresponding scope. > > In fact this very syntax was used in one of the intermediate Wirth > languages between algol and pascal (we used at Grenoble an algolW > compiler implementing it at that time). It was done so exactly to forbid > any use of the for control variable outside of the loop, because in many > CPU for control variables are maintained in registers (CX in 16 bit 386 > CPU for example) and need not at any time to be affected into memory (at > least the for control variable of the innermost loop). > So a good idea was lost in going into EP. > But who may update the standard ? The commitees... ;-) But we could perhaps implement it in GPC (like we've already implemented a lot of other non-standard extensions)... 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

1 0

Re: revised faq
by Russ Whitaker 22 May '00

22 May '00

Hi Frank wrote: > Russ Whitaker wrote: > > > COPYING.LIB GNU Library Public License > > The precise name is "GNU Library General Public License". > ok > > http://www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.htm > > l > > Bad line break. > Have 2 computers on my desk - the old one runs Windows 95 and it is used strictly for email. When I insert a .txt file it breaks lines where it wants to. Attached is a .gz file. It should look ok. > > Another way is to add the following code to your program to define a > minimum stack size (here: 2 MB). This value will be honored even if > a user sets a lower value by using stubedit, so this method might be > a little safer. > > (Note: The syntax given here is valid for GPC releases of May 2000 > and newer.) > ok entered change visited agnes earlier today - No May releases yet. Did find version 0.4 of the FAQ Russ <russwhit(a)mind.net>

1 0

Re: revised faq
by Frank Heckenbach 22 May '00

22 May '00

Russ Whitaker wrote: > hi > here's the monthly :-) revised faq > > > COPYING.LIB GNU Library Public License The precise name is "GNU Library General Public License". > http://www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.htm > l Bad line break. > I'm accessing an `array[1..4000000] of byte' and I got an exception. > ==================================================================== > > Per default, the maximum stack size of a djgpp application is 256K. > If you need more, you have to adjust it with the stubedit program, i.e.: > > stubedit your_app.exe minstack=5000K Another way is to add the following code to your program to define a minimum stack size (here: 2 MB). This value will be honored even if a user sets a lower value by using stubedit, so this method might be a little safer. (Note: The syntax given here is valid for GPC releases of May 2000 and newer.) {$ifdef DJGPP} var MinStackSize : Cardinal = $200000; asmname '_stklen'; {$endif} 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: posible bug question...
by J. David Bryan 22 May '00

22 May '00

Hello Marco, I have copied my reply to the list. On 21 May 2000, at 15:56, Marco van de Voort wrote: > Or do they mean: > > procedure x; > > var i : integer; > > procedure nestedx; > > begin > i:=5; > end; > > begin > for i:=1 to 5 do nestedx; > end; I believe you are correct, and my original reading that: i := 0; for i := 1 to 10 do ; was incorrect is itself incorrect. The key part of the statement in the standard is that the "...procedure-and-function-definition part of the block that closest-contains a for-statement..." cannot threaten the control variable. In your example, the "procedure x" block (the second begin-end block) is the "block that closest-contains a for-statement." Therefore, your first block, that of "procedure nestedx", forms the "procedure-and- function-definition-part of the block...." So your example breaks the requirement listed in the standard, meaning your interpretation is correct. In my example, the threat ("i := 0") is not in either the for-statement nor the procedure-and-function-definition part, so it is legal. -- Dave

1 0

Re: posible bug question...
by Russ Whitaker 21 May '00

21 May '00

Hi 1) p[h] defaults to zero 2) the value of h can exceed the array size 3) In BP 7, If you modify the index inside a for-loop the results are undefined After you exit the for-loop the index is undefined unless you exited with a goto in C, You can mdify the index inside the for-loop The value of the index is visable after you exit the loop (ref K&R 2nd Ed, p61) So what does the Pascal specs say? (I wish I had a copy of each) Russ <russwhit(a)mind.net> ---------- > From: Frank Heckenbach <frank(a)g-n-u.de> > To: gpc(a)gnu.de > Subject: Re: posible bug question... > Date: Friday, May 19, 2000 10:17 AM > > Richard Sharman wrote: > > > Frank Heckenbach writes: > > | Norberto Alfredo Bensa wrote: > > | The problem is the following: You use a for loop counter (h) after > > | the loop, and in Pascal this is undefined (this might be one of the > > | most despised features of Pascal, but it has its reasons). > > | Therefore, it's quite possible that one compiler does what you want > > | and another compiler (or another version of the same compiler) > > | doesn't. > > | > > > > Isn't it also wrong to attempt to modify a FOR loop index variable > > inside the body for the FOR statement? > > Yes, it is. I'd missed that one. (Using a while loop will avoid this > problem as well, of course.) > > > for h := 1 to j-1 do > > if 2*p[h]>i then h := j { <------- } > > else if i mod p[h]= 0 then break; > > > > I thought this was not allowed in Pascal, but I see gpc accepts it. > > I agree, GPC should check this more strictly (at least give a > warning). > > 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: posible bug question...
by Frank Heckenbach 21 May '00

21 May '00

Russ Whitaker wrote: > 1) p[h] defaults to zero I don't think that's the problem since h < j and p [j] is initialized before each increment of j. > 2) the value of h can exceed the array size Only if more than 50 primes <= 100 are found which does not usually happen. ;-) > 3) In BP 7, > If you modify the index inside a for-loop the results > are undefined > After you exit the for-loop the index is undefined unless > you exited with a goto > > in C, > You can mdify the index inside the for-loop > The value of the index is visable after you exit the loop > (ref K&R 2nd Ed, p61) Yes, because there does not even have to be a loop counter in a C for loop (or there can be several counters, or anything). C for loops are really only syntactic sugar for while loops... > So what does the Pascal specs say? Like BP (in this case). > (I wish I had a copy of each) You can find them at ftp://ftp.digital.com/pub/DEC/Pascal/ (but you need a lot of patience to make sense of their formal language)... 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

1 0

revised faq
by Russ Whitaker 20 May '00

20 May '00

hi here's the monthly :-) revised faq Russ <russwhit(a)mind.net> ++++++++++++++++++++++++++++++++++++++++++++++++ GNU Pascal Frequently-Asked Questions List, Edition 0.7, May 2000 by Russ Whitaker <russwhit(a)mind.net> based on GNU Pascal Frequently-Asked Questions List, Edition 0.4, for GPC version 2.0, November 1996 by J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> For up-to-date information, ask the GPC mailing list (see below). Index ***** 1.0 GNU Pascal - what, where and why 2.0 Installation 3.0 After the installation 4.0 Pascal on the DJGPP platform 5.0 (reserved) 6.0 Getting Help 7.0 Miscellaneous 1.0 GNU Pascal *************** 1.1 What and why? ================= The purpose of the GNU Pascal project is to produce a Pascal compiler (called GNU Pascal or GPC) which * combines the clarity of Pascal with powerful tools suitable for real-life programming, * supports both the Pascal standard and the Extended Pascal standard as defined by ISO, ANSI and IEEE (ISO 7185:1990, ISO/IEC 10206:1991, ANSI/IEEE 770X3.160-1989), * supports other Pascal standards (UCSD Pascal, Borland Pascal, Pascal-SC) in so far as this serves the goal of clarity and usability, * may be distributed under GNU license conditions, * can generate code and run on any computer for which the GNU C compiler can generate code and run on. Pascal was originally designed for teaching. GNU Pascal provides a smooth way to proceed to challenging programming tasks without learning a completely different language. 1.2 What is the current version? ================================ The latest release as of this writing is GPC-19991030. GPC requires GCC as a back-end. Patches for GCC 2.8.1 thru GCC 2.95.2 are provided but it is recommended that you use at least GCC 2.95. 1.3 Is it compatible with Turbo Pascal (R) ? ============================================ GPC is *not* a drop-in replacement for Borland's Turbo Pascal (R). Almost all BP language features are supported. Notable exceptions are the string format (as discussed below), or the 'Mem' and 'Port' pseudo arrays, though replacement functions for the latter on x86 platforms exist in the 'Ports' unit. Also, almost all of BP's run time library is supported in GPC (built-in or in units with the same names as their BP counterparts). Some notes: - A BP compatible Graph unit exists but is distributed separately due to its license. - The OOP stuff (Turbo Vision etc.) is not yet completed, but work on several projects is underway. - Some exotic routines need an explicit `uses System' statement, or equivalently a `--uses=system' command line option. See the System unit for details. - A few unportable routines in the Dos unit are only supported under DJGPP if `__BP_UNPORTABLE_ROUTINES__' is defined (i.e., when com- piling with `-D__BP_UNPORTABLE_ROUTINES__'). ---Frank 1.4 Which platforms are supported by GNU Pascal? ================================================ GPC uses the GCC backend, so it should run on any system that is supported by GNU CC. This includes a large variety of Unix systems, MS-DOS, OS/2 and Win32. A full list of platforms supported by GCC can be found in the file `INSTALL' of the GCC distribution. Not all of these have actually been tested, but it is known to run on these platforms: ix86-linux (Linux 2.x, ELF) i486-linuxaout i486-linuxoldld i386-freebsd1.2.0 AIX 4.2.1 AIX 4.3 DJGPP V2 (msdos) EMX 0.9B (OS/2, msdos) cygwin32 beta20 and higher (Windows95, Windows NT) Mingw32 (Windows95/98, Windows NT) mips-sgi-irix5.3 sun-sparc-sunos4.1.4 sparc-sun-solaris2.x sun-sparc-solaris 2.5.1 sun-sparc-solaris 2.6 sun-sparc-solaris 7 alpha-unknown-linux alphaev56-dec-osf4.0d >>> Ok people - send us your success stories, with canonical machine name! <<< 2.0 Installation ***************** 2.1 Why shouldn't I just grab and install a binary? =================================================== On many platforms a binary is a quick and easy way to go. With Linux, however, you may have a problem. Many of the installation details are left up to the implementor and if that isn't enough updating a seemingly unrelated piece of software can cause compatibility problems. Witness this exchange from the mailing list: >>I'm not an expert on this, but I remember that I installed on my Linux >>(RedHat 6.1) two RPM packages: >> >> gpc-19990118-1.i386.rpm >> gpc-extras-19990118-1.i386.rpm > I have install all but it doesn't run anyway! > My Linux is mandrake 7.0, it is maybe the problem?... Mandrake is NOT compatible with RedHat despite claims - you need less manual tweaks then in case with SuSE or Debian but ONLY RedHat is compatible with RedHat (even in this case only if you are lucky enough - see below). ESPECIALLY for GPC: Mandrake traditionally using very "advanced" (read: barely working) versions of gcc and gpc relies HEAVILY on gcc. If you DO NOT have RPM for EXACTLY your distribution then better (=easier) to recompile GPC from sources. And when I'm saying EXACTLY I mean exactly: RPM for RedHat 5.0 WILL NOT work in RedHat 5.2, RPM for RedHat 6.0 WILL NOT work in RedHat 6.2, etc. In some cases even "RedHat x.y" can be incompatible with "RedHat x.y with updates" :-(( Usually it can be easily tracked down and fixed by knowledgeable person (almost any package for any distribution can be forced to work in almost any other distribution) but just "rpm -Uvh" quite often will not work. When you are compiling program from sources autoconf usually can find and compensate most differences automagically but rpm/dpkg/apt is NOT sophisticated enough. That's why we recommend to start from sources when binaries do not work for you. 2.2 How do I get and install GPC on my computer? ================================================ 1. The easiest way is is from a distribution - if you can find it. All the dependency files should be there, also. The downside is if the GPC release date is prior to Oct. 1999 you should plan on doing an update. 2. The recommended way is to build it yourself from the source listings. If you have everything you need to compile a kernel except the kernel source then all you need is the GPC source and a GCC source. The down- side is if you have a slow computer the build could take several hours. You can get the GPC source from ftp://agnes.dida.physik.uni-essen.de/ You can get the GCC source from http://gcc.gnu.org 3. You may not want to install a new distribution just to get GPC and the build project on a 386 can take several hours as well as some 50M of hard drive space. Then try one of the several pre-compiled binaries available. The downside is you need one that is compatible with your computer and C library. GNU Pascal Compiler binaries for Sun Solaris 7 (Sparc/x86) operating environment in native Solaris packages form are available at: Sparc: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/sparc http://math.uwb.edu.pl/download/solaris7/sparc x86: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/x86 http://math.uwb.edu.pl/download/solaris7/x86 For installation instructions read Readme.txt file on that site. GPC 19991030 was compiled based on GCC 2.95. Binaries for Solaris 8 (Sparc and Intel) are now available on: http://math.uwb.edu.pl/download/solaris8/ ftp://mizar.uwb.edu.pl/pub/misc/solaris8/ -- Mariusz Zynel Also, on Feb 9th, 2000 the following binaries were found in a FTP directory at agnes.dida.physik.uni-essen.de: Directory: /gnu-pascal/alpha/binary/ gpc-19990607-djgpp.zip Directory: /gnu-pascal/beta/binary/ gpc-19990118-1.i386-pc-linux-gnu.rpm gpc-19990118-egcs-1.1.1.i386-linux-glibc2.tar.gz gpc-19990118-egcs-1.1.1.i386-pc-mingw32.zip gpc-19990118-egcs-1.1.1.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.alpha-unknown-linux-gnu.tar.gz gpc-19990118.alphaev56-dec-osf4.0d.tar.gz gpc-19990118.i386-pc-djgppv201.zip gpc-19990118.i386-pc-emx0.9d.zip gpc-19990118.i386-pc-mingw32.zip gpc-19990118.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.mips-sgi-irix6.2.tar.gz gpc-19990118.sparc-sun-solaris2.6.tar.gz gpc-19990430-i386-pc-djgppv202.zip gpc-extras-19990118-1.i386-pc-linux-gnu.rpm 2.3 How do I build a GPC compiler? ================================== CAUTION: There have been extensive changes in GCC from 2.8 to 2.95. The old GPC build instructions, for GCC-2.8 and earlier, will not work on GCC-2.95 and up. If you have a typical ix86 box the routine is fairly simple. Any other computer you should carefully read the documentation in gcc*/install. Assuming you have: 1. A working C compiler. 2. The usual tools: ar, awk, bash, bison, ld, make, patch, sed 3. The GPC and GCC tar.gz source in directory /usr/local/src Then here's a cookbook recipe: 1. Unpack the two sources: tar -xvzf gcc-2.95.2.tar.gz tar -xvzf gpc-19991030.tar.gz 2. Since GCC recommends building gcc in a separate directory, lets make one: we'll call it gcc-build. mkdir gcc-build 3. Now we need to move GPC into GCC: mv gpc/p gcc-2.95.2/gcc NOTE: Don't try using a symlink instead. This is known not to work. You have to actually move the directory. 4. Next is a patch to GCC: cd gcc-2.95.2/gcc patch -s -p1 < p/diffs/gcc-2.95.2.diff However, since the configure script will apply the patch automatically when necessary, you can usually skip this step. 5. Now GCC is ready to build several languages, including Pascal. If you want to know what languages (besides C), grep language= */config-lang.in will give you a list. 6. Next step is to do a configure: cd ../../gcc-build ../gcc-2.95.2/configure --enable-languages=pascal This will configure the compiler for installation under /usr/local. If you want to install it in another place, e.g. /usr or in your home directory, you can specify this with the '--prefix' option: ../gcc-2.85.2/configure --enable-languages=pascal --prefix=/home/me/usr (note: one line - it's two here because of length) If configure complains that it couldn't figure out what your computer is, for a Linux system and a pentium or pentium II you should add --host=i586-linux-gnu to the configure line. You can find values for other hosts in either the GCC documentation or chapter 3 of Richard Stallman's book, "Using and Porting GNU CC". The following text assumes default configuration: under /usr/local. With --enable-languages=pascal you get both GCC and GPC. The GCC won't interfere with your default compiler because it is installed in a different place. Without the --enable-languages option you get ALL the languages GCC can build. 7. Now let's build it: make bootstrap-lean Bootstrap-lean is recommended instead of bootstrap because it removes files that are no longer needed. That "make bootstrap-lean" will take some time. If you want to know how much, you could date > /time1 ; make bootstrap-lean ; date > /time2 On my 400mhz i586 with 128m ram, no swap, it took 24 min 34 sec. 8. If all went well you can now install it: make install You have to do this last step as root (Unless configured for installation in your home directory), while the other steps can be done under a normal user ID. That's it. Here's where various parts of GPC are installed: /usr/local/bin/gpc The GPC executable /usr/local/info/gpc.info* Info documentation /usr/local/man/man1/gpc.1 Man page (contains only an extract from the Info documentation) /usr/local/doc/gpc/* Some texts about GPC, including this FAQ /usr/local/doc/gpc/demos/* Some interesting demos GPC's units are installed in a directory whose name you can find with gpc --print-file-name=units after installation. If this doesn't give the correct directory (or just says 'units'), your installation is not quite right yet. If you run into installation problems the following might help: gpc --print-search-dirs 3.0 After the Installation ************************** 3.1 What to do first? ===================== Stop right now and go read the file BUGS in directory /usr/local/doc/gpc While you're at it, you should take a look at the other files in that directory: README General Information about GPC AUTHORS List of GPC authors NEWS Changes since the last beta version COPYING GNU General Public License COPYING.LIB GNU Library Public License Another good article on submitting bug reports can be found at either: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html or: http://freshmeat.net/news/2000/02/26/951627540.html 3.2 What additional libraries should I have? ============================================ You will need certain additional libraries when you compile some of the units. These can be found in the directory ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs What follows is the contents of the README file found there: In this directory, you can find the libraries used by some of GPC's units. Currently, there are the following libraries: - gmp: Arithmetic for integers, rationals and real numbers with arbitrary size and precision. Used by the GMP unit. - rx: Regular expression matching and substitution. Used by the RegEx unit. - ncurses, PDCurses: Screen handling. Used by the CRT unit. Depending on your system, you have the following choices: Unix: You can compile terminal applications with ncurses and applications that run in an X11 window with PDCurses (though terminal applications can, of course, also run in an xterm under X11). ncurses is used by default. If you want to use PDCurses (a.k.a. XCurses), give the option `-DX11' when compiling CRT. Dos with DJGPP and MS-Windows with mingw: Only PDCurses is available and will be used by default. MS-Windows with Cygwin: PDCurses and ncurses are available. PDCurses is used by default. If you want to use ncurses, give the option `-DUSE_NCURSES' when compiling CRT. Other systems: Please see the `README's and installation instructions of PDCurses and ncurses to find out which one(s) can be built on your system. See the conditionals at the end of crt.inc and crtc.h (and change them if necessary) on which library is used by default. The source code of the libraries is available in this directory. Most libraries come with one or several patches which should be applied before compiling them. Binaries for some platforms are available in the `binary/<platform>' subdirectories. If you compile the libraries for other platforms, be invited to make the binaries available to us for distribution on this FTP site. There are also the following files: - terminfo-linux.tar.gz This is a patch to enable ncurses programs to make use of the ability of Linux 2.2 and newer kernels to produce a block cursor when needed. The present patch can be installed without recompiling anything, just by copying some files into place. More details can be found in the `README' file included in this archive. The patch will not do any harm on older kernels. Please note that *not* only on Linux machines it is useful to install the patch. Installing them on any other machine will allow users who telnet in from a Linux console to profit from the block cursor capability. Besides, some Unix systems have installed older Linux terminfo entries or none at all, so it's a good thing, anyway, to give them a current version. The patch is included in the terminfo database of ncurses 5.0, so if you install ncurses 5.0 (source or binary), you don't need to get the patch separately. But you can install it on a system with an older ncurses version if you don't feel like upgrading ncurses altogether. - tsort-2.9i.zip A little utility (extracted from util-linux-2.9i, but not Linux specific), needed for the configuration of the rx library. You need it only if you compile rx yourself (and if it's not already present on your system), not when using a rx binary. In addition to the above libraries there is a unit which you can use to interface Svgalib. You can read a mini-FAQ about it at http://ages.dida.physik.uni-essen.de/~nicola complete with links to download the unit via http or ftp. If you want to download the unit directly, get svgalib-gpc-20000216.tar.gz from ftp://agnes.dida.physik.uni-essen.de/home/nicola 3.3 Which components do I need to compile Pascal source code? ============================================================== A complete Pascal compiler system should at least have: 1. The actual compiler, GPC. While there are some binaries available you can build GPC yourself. You need a working C compiler, some tools: bash, ar, patch, make, the GCC source, and the GPC source. 2. An editor, assembler, linker, librarian and friends. 3. A C library. If you have a working C compiler you already have this. 4. A debugger, if you want to debug your programs. For most people, the GNU binutils and GNU debugger (gdb) are a good choice, although some may prefer to use vendor specific tools. 3.4 How do I debug my Pascal programs? ======================================= To debug your programs, (a) GNU Pascal must be able to generate executables with debug info for your platform, and (b) you must have a debugger which understands this. * If `gpc -g -o hello hello.p' says: `gpc: -g not supported for this platform', then GPC is unable to generate debug info. Usually, installing GAS instead of your system's assembler can overcome this. When you configure the GCC used for GPC, specify `-with-gnu-as', and possibly `-with-gnu-ld' and/or `-with-stabs'. More information can be found in `INSTALL' file in the GNU CC source directory. * Your system's debugger may not understand the debug info generated by GNU tools. In this case, installing GDB may help. The bottom line: if you can debug GCC compiled programs, you should be able to do this with GPC too. The GNU debugger (GDB) currently does not have a "Pascal" mode, so it is unable to display certain Pascal structures etc. When debugging, please note that the Initial Letter In Each Identifier Is In Upper Case And The Rest Are In Lower Case. If you want to display variable `foo' in the debugger, type `show Foo' or `display Foo' instead. 3.5 Can you recommend an IDE? ============================== Users of Borland Pascal may wonder if there's a replacement for the IDE (Integrated Development Environment). Here's a few suggestions: * (X)Emacs. Some people think it's the answer to the question of Life, the Universe and Everything, others decide it's uGNUsable. Available from your friendly GNU mirror and most distributions. * XWPE is an imitation of the Borland IDE, so users of Borland Pascal may find it a good alternative. * RHIDE. DJGPP users should definitely try RHIDE. The latest (beta) release is compatible with GNU Pascal and allows stepping, tracing and watching like Borland's IDE. It can be downloaded from: http://www.tu-chemnitz.de/~sho/rho/rhide/rhide.html * PENG. It's not free software, but it was written with GPC. It's very similar to Borland's IDE, but with many extensions: http://fjf.gnu.de/peng.html 3.6 Debugger? ============== Although GDB is an excellent debugger, it's user interface is not very attractive. Refer to the comp.windows.x FAQ: "Where can I get an X-based debugger?" at: http://www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.htm l Some useful frontends include: XXGDB, tGDB and XWPE. see: http://www.ee.ryerson.ca:8080/~elf/xapps/Q-IV.html Very nice, but resource consuming is the Motif based DDD: http://sol.ibr.cs.tu-bs.de/softech/ddd/ 4.0 GNU Pascal on the DJGPP (MS-DOS) platform ********************************************* This chapter discusses some potential problems with GNU Pascal on MS-DOS, using DJGPP. What is DJGPP? ============== The following paragraph is from the site www.delorie.com/djgpp: DJGPP is a complete 32-bit C/C++ development system for Intel 80386 (and higher) PCs running DOS. It includes ports of many GNU development utilities. The development tools require a 80386 or newer computer to run, as do the programs they produce. In most cases, the programs it produces can be sold commercially without license or royalties. If you need more information ============================ GPC/DJGPP is a DJGPP V2 application, and most of the DJGPP documentation applies for GPC too. A great source of information is the DJGPP FAQ: http://www.delorie.com/djgpp/v2faq/230b.zip Another place to look for DJGPP documentation is the DJGPP Knowledge Base, at this URL: http://www.delorie.com/djgpp/doc/kb/ What do I download? =================== As discussed in section 2.2, other than GPC itself, you need an assembler, linker and friends, a C library and possibly a debugger. The site www.delorie.com/djgpp recommended the following files and they will help you find a mirror: v2/djdev203.zip (C library) v2gnu/bnu2951b.zip (assembler, ....) v2gnu/gcc2952b.zip (gcc) v2gnu/gdb418b.zip (debugger) v2gnu/mak379b.zip (make) v2gnu/txi40b.zip (texi) This list is 10,553,416 bytes not counting GPC. You can use a binary version of GPC from agnes. How do I install the compiler? ============================== If you don't have djgpp installed on your harddisk, create a directory for GNU pascal (`c:\gpc'), and unzip the archives. Make sure you preserve the directory structure (use `pkunzip -d'). Now, add the directory where `gpc.exe' lives (`c:\gpc\bin') to your path and set the DJGPP environment variable to point to your `djgpp.env' file: set DJGPP=c:\gpc\djgpp.env Then, add this to your `djgpp.env' file: --------------------------------------------------------- [gpcpp] C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/lang/pascal; %DJDIR%/include;%DJDIR%/contrib/grx20/include ( note: one line; but split here to fit page ) [gpc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib;%DJDIR%/contrib/grx20/lib --------------------------------------------------------- The binary distribution should come with a `djgpp.env' which is already modified, so you may not have to do this. The GPC online documentation is in GNU info format; you need the Info reader (`txi390b.zip') to read it, or use the built-in Info reader of the RHIDE or PENG IDE. To add the GPC documentation to the info directory file, edit the `c:\gpc\info\dir' file, and locate this section: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- To add GPC, change it to look like this: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GPC: (gpc.inf). The GNU Pascal Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- Specific information for low-memory conditions and more can be found in the DJGPP FAQ and documentation. I cannot read the Info documentation! ===================================== To read the Info documentation, you need the `info' program from `txi390b.zip' or an IDE like RHIDE or PENG. GPC says: no DPMI ================= You don't have a DPMI server installed, and DJGPP v2 requires it to run. You can either use one of the commercial DPMI servers (e.g., run `gpc' in a DOS box under Windows) or download and install CWSDPMI (`csdpmi3b.zip') which is a free DPMI server written for DJGPP. I have troubles with assembly code ================================== The GNU Assembler (`as.exe'), or `gas', called by GCC accepts "AT&T" syntax which is different from "Intel" syntax. Differences are discussed in section 17.1 of the DJGPP FAQ. A guide is available which was written by Brennan Mr. Wacko Underwood <brennan(a)mack.rt66.com> and describes how to use inline assembly programming with DJGPP, at this URL: http://www.rt66.com/~brennan/djgpp/djgpp_asm.html There's also a GPC assembler tutorial at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpcasm.zip Section 17.3 of the DJGPP FAQ discusses some methods to convert "Intel" syntax to "AT&T". Tell me how to do DPMI, BIOS and other DOS related things. ========================================================== DPMI, BIOS and other functions are no different than other system functions. Refer to section 3.1 how to access your system's C-library. This small example shows how to use DPMI, copying some structures and function prototypes of `<dpmi.h>': --------------------------------------------------------- program DPMITest; {$X+} { `Byte' is `unsigned char' in C, `ShortInt' is `short' in C, `MedCard' is `unsigned long' in C, `Word' is `unsigned' in C, etc. (all these types are built-in). } type TDpmiVersionRet = record major : Byte; minor : Byte; flags : ShortInt; cpu : Byte; master_pic : Byte; slave_pic : Byte; end; type TDpmiFreeMemInfo = record largest_available_free_block_in_bytes : MedCard; maximum_unlocked_page_allocation_in_pages : MedCard; maximum_locked_page_allocation_in_pages : MedCard; linear_address_space_size_in_pages : MedCard; total_number_of_unlocked_pages : MedCard; total_number_of_free_pages : MedCard; total_number_of_physical_pages : MedCard; free_linear_address_space_in_pages : MedCard; size_of_paging_file_partition_in_pages : MedCard; reserved1 : MedCard; reserved2 : MedCard; reserved3 : MedCard; end; function DpmiGetVersion (var ret: TDpmiVersionRet): integer; asmname '__dpmi_get_version'; function DpmiGetFreeMemoryInformation (var info: TDpmiFreeMemInfo): integer; asmname '__dpmi_get_free_memory_information'; var version: TDpmiVersionRet; meminfo: TDpmiFreeMemInfo; begin if DpmiGetVersion ( version ) = 0 then begin writeln('CPU type : ', version.cpu, '86'); writeln('DPMI major : ', version.major); writeln('DPMI minor : ', version.minor); end else writeln ( 'Error in DpmiGetVersion' ); if DpmiGetFreeMemoryInformation ( meminfo ) = 0 then writeln ( 'Free DPMI memory : ', meminfo.total_number_of_free_pages, ' pages.') else writeln ( 'Error in DpmiGetMemoryInformation' ); end. --------------------------------------------------------- I'm accessing an `array[1..4000000] of byte' and I got an exception. ==================================================================== Per default, the maximum stack size of a djgpp application is 256K. If you need more, you have to adjust it with the stubedit program, i.e.: stubedit your_app.exe minstack=5000K Still, it might be a good idea to use pointers for this kind of structures, and allocate the memory at runtime. 5.0 (reserved) *************** 6.0 STRINGS *********** What's this confusion about strings? ==================================== Turbo Pascal strings have a length byte in front. Since a byte has the range 0 .. 255, this limits a string to 255 characters. However, the Pascal string schema, as defined in section 6.4.3.3.3 of the ISO-10206: 1990 Extended Pascal standard, is a schema record: type String (Capacity : Integer) = record Length : 0 .. Capacity; String : packed array [1 .. Capacity + 1] of Char end; The `+ 1' is a GPC extension to make it feasible to automatically add the #0 terminator when passing or assigning them to CStrings. Thus at the expense of a little added complexity ( must declare capacity, don't use GetMem, and the additional space requirement ) you can now have very long strings. The following Q&A is also about strings: ======================================== Q: Should the different variants in a variant record overlay in the same memory? Previous Pascals I have used have guaranteed this, and I've got low-level code that relies on this. The variants are not the same length, and they are intended not to be. A: No, this is intentional so that the discriminants are not overwritten, and they can be properly initialized in the first place. Consider: record case Boolean of False: (s1 : String (42)); True: (s2 : String (99)); end; If the strings would overlay, in particular their discriminants would occupy the same place in memory. How should it be initialized? Either way, it would be wrong for at least one of the variants... So, after a discussion in comp.lang.pascal.ansi-iso where this topic came up concerning file variables (which also require some automatic initialization and finalization), we decided to do this in GPC for all types with automatic initialization and finalization (currently files and schemata, in the future this might also be Delphi compatible classes and user-defined initialized and finalized types), since the standard does not guarantee variants to overlay, anyway... There are two ways in GPC to get guaranteed overlaying (both non-standard, of course, since the standard does not assume anything about internal representations; both BP compatible), `absolute' declarations and variable type casts. E.g., in order to overlay a byte array to a variable v: var b: array [1 .. SizeOf (v)] of Byte absolute v; or type t = array [1 .. SizeOf (v)] of Byte; then `t (v)' can be used as a byte array overlayed to v. Q: In standard Pascal you expect s[1] to align with the first character position of s and thus one character to the left is the length of s. Thus s[0] is the length of s. True? A: This holds for UCSD/BP strings (which GPC does not yet implement, but that's planned). The only strings Standard Pascal knows are arrays of char without any length value. Q: Two different kinds of strings with the same name - string - does make a bit of confusion. Perhaps the oldstyle strings could be renamed "short string" ? A: When we implement the short strings, we'll have to do such a distinction. Our current planning goes like this: string (n): string schema (EP compatible) string [n]: short string (UCSD/BP compatible, where n must be <= 255) string: dependent on flags, by default undiscriminated schema, but in BP mode (or with a special switch) short string of capacity 255 (UCSD/BP compatible). ---- Frank Q: So when will these short strings be available? A: It's been planned for over a year. The delay has been caused by more pressing problems. What about C strings? ===================== A C string (`char *') is an array of char, terminated with a `NULL' char. C library functions require C, not Pascal style string arguments. However, Pascal style strings are automatically converted to C style strings when passed to a routine that expects C style strings. This works only if the routine reads from the string, not if it modifies it. E.g., this is how you access the `system()' call in your C library (which is not necessary any more, since `Execute' is already built-in): --------------------------------------------------------- program SysCall; function system(name : CString): integer; C; var result : integer; begin result := system ('ls -l'); writeln('system() call returned : ', result); end. --------------------------------------------------------- There may be other ways to do the same thing; you could use a type `PChar' instead of `CString' and replace all references to `CString' with `PChar'. `PChar' is predefined now (though we recommend `CString' because it makes it clearer that we're talking about some kind of string rather than a single character), and a lot of library routines in Pascal for many applications (in the GPC unit and some other units) have been written (see above)... type PChar = ^char; Do *NOT* pass a "C" style string as a var-argument if the C prototype says `const char *' or you will get a coredump. 6.0 Getting Help **************** If you have never submitted a bug report before there's a good HOWTO article on Freshmeat. The URL is http://freshmeat.net/news/2000/02/26/951627540.html Please read the documentation (info files, readme's and the file `BUGS') that come with GPC, plus other docs that might help (the DJGPP FAQ if you use DJGPP, etc.) before you send email to the maintainers or mailing list. Help! The compiler crashed! =========================== If the compiler crashes, you have discovered a bug. A reliable compiler never crashes. To help the maintainers fix this bug, it is important that you send us a problem report. I think I found a bug - now what? ================================= Bugs are best reported to the GPC mailinglist <gpc(a)gnu.de>. That way, they always reach the maintainers. Try to give as much information as possible, plus a short code snippet that triggers the compiler bug. If you're on Unix, you can find out where the compiler crashed if you enable coredumps, then load the compiler (`gpc1') plus the core file in the debugger (`gdb /your_path_here/gpc1 core'), then type `backtrace' to get a stacktrace. Include this stacktrace in your bug report. Which newsgroup(s) are suited for GPC related problems? ======================================================= There are several Pascal related newsgroups, but none is dedicated just to GNU Pascal. This one may be useful: comp.lang.pascal.misc Pascal in general and ungrouped Pascals. Pascal syntax related questions may be appropriate in: comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO standards. The next newsgroup is a haven for beginners, answering questions that would apply to almost any pascal. However, if you have a GPC-specific question don't post there - use the GPC mailing list. And if in doubt use the GPC mailing list. comp.lang.pascal.borland Borland Pascal questions. Also, the mailing list archives are a good place to look. The URL is http://www.gnu.de/archive/wilma.cgi/gpc and http://www.gnu.de/archive/wilma.cgi/gpc-announce respectively. Now the pages also come in gpc signature colors. :-) Note: Currently, the search option is working fine. If you find it broken, please email me at <anja(a)drewitz.de>. Please don't mail a copy to the GPC list because I let procmail move all mails with To: gpc... and Cc: gpc... to a separate folder and would not see your mail for a long time. --- Anja How to post to the mailing list =============================== You can send a message to the GPC mailing list by sending email to the list address <gpc(a)gnu.de> as if it were a person. How to become a subscriber to the mailing list ============================================== You can join the mailing list by sending a message to <gpc-request(a)gnu.de> (NOT <gpc(a)gnu.de> !) with your request to be added to the list of the form: subscribe your(a)mail.address How to unsubscribe from the mailing list ======================================== To leave the mailing list, send a message to <gpc-request(a)gnu.de> of the form: unsubscribe your(a)mail.address What other mailing lists may be of interest to me? ================================================== There is a (low-traffic) announce list, <gpc-announce(a)gnu.de>, to stay up-to-date. To subscribe to the list, write an email with "subscribe gpc-announce" in the body to <majordomo(a)gnu.de>. (The subject will be ignored.) 7.0 Miscellaneous ***************** I want to contribute; where do I start? ======================================= If you want to contribute, please write to the mailing list. Where is the GNU Pascal FTP site? WWW? ====================================== The master FTP site for GNU Pascal is `agnes.dida.physik.uni-essen.de'. GNU Pascal related files can be found in: http://agnes.dida.physik.uni-essen.de/~gnu-pascal ftp://agnes.dida.physik.uni-essen.de/gnu-pascal A not quite up-to-date mirror is: ftp://sunsite.doc.ic.ac.uk/gnu/MORE_GNU/gnu-pascal/ The latest developer releases can be downloaded from: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html Also, we have a homepage on the web: http://home.pages.de/~GNU-Pascal/ ---Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ For now, this same page appears at http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ About this FAQ. =============== Original Maintainer: J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> Current Maintainer: Russ Whitaker <russwhit(a)mind.net> This is the second incarnation of the GNU Pascal FAQ list. Comments about, suggestions for, or corrections to this FAQ list are welcome. Please make sure to include in your mail the version number of the document to which your comments apply (you can find the version at the beginning of this FAQ list). Many people have contributed to this FAQ, only some of them are acknowledged above. Much of the info in, and inspiration for this FAQ list was taken from the gpc mailing list traffic, so you may have (unbeknownst to you) contributed to this list.

2 1

Re: posible bug question...
by Norberto Alfredo Bensa 20 May '00

20 May '00

> Hope this helps ! Thank you *a lot* Maurice!!!!, it really help me!! Now I know why they call Pascal a severe teacher ;-) ...I need to change the "for h" loop with a "while h < j" loop... Greetings, and thanks so much for your time and help, Norberto

1 0

Re: posible bug question...
by Frank Heckenbach 19 May '00

19 May '00

Richard Sharman wrote: > Frank Heckenbach writes: > | Norberto Alfredo Bensa wrote: > | The problem is the following: You use a for loop counter (h) after > | the loop, and in Pascal this is undefined (this might be one of the > | most despised features of Pascal, but it has its reasons). > | Therefore, it's quite possible that one compiler does what you want > | and another compiler (or another version of the same compiler) > | doesn't. > | > > Isn't it also wrong to attempt to modify a FOR loop index variable > inside the body for the FOR statement? Yes, it is. I'd missed that one. (Using a while loop will avoid this problem as well, of course.) > for h := 1 to j-1 do > if 2*p[h]>i then h := j { <------- } > else if i mod p[h]= 0 then break; > > I thought this was not allowed in Pascal, but I see gpc accepts it. I agree, GPC should check this more strictly (at least give a warning). 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

1 0

Re: posible bug question...
by Frank Heckenbach 19 May '00

19 May '00

Norberto Alfredo Bensa wrote: > If this is not the right place to ask for gnu pascal port to djgpp please > let me know where can I do it... It is. (And, BTW, this problem is not DJGPP specific, anyway.) > Is this a bug in gnu pascal or just a "feature" I didn't know about? > > The code below is intented to find the prime numbers between 1 and 100 (... > ok 1 isn't really a prime number but who cares? ;-)), but it doesn't work... > it just displays 1.... Now if you add "h :=1;" just after "j" is > initialized, then the program works!!!... it doesn't make sense, at least > for me ... (it worked unmodified with the gpc dist from gpc112b.zip) The problem is the following: You use a for loop counter (h) after the loop, and in Pascal this is undefined (this might be one of the most despised features of Pascal, but it has its reasons). Therefore, it's quite possible that one compiler does what you want and another compiler (or another version of the same compiler) doesn't. For a solution, I suggest to convert the for loop into a while loop: h := 1; while h <= j-1 do begin ... Inc (h) end; 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

posible bug question...
by Norberto Alfredo Bensa 19 May '00

19 May '00

If this is not the right place to ask for gnu pascal port to djgpp please let me know where can I do it... ---------------------------------------------------- Is this a bug in gnu pascal or just a "feature" I didn't know about? The code below is intented to find the prime numbers between 1 and 100 (... ok 1 isn't really a prime number but who cares? ;-)), but it doesn't work... it just displays 1.... Now if you add "h :=1;" just after "j" is initialized, then the program works!!!... it doesn't make sense, at least for me ... (it worked unmodified with the gpc dist from gpc112b.zip) btw: gnu pascal for djgpp from gpc20bb.zip, and bnu2951b.zip. This is the output from gpc --verbose Reading specs from c:\djgpp\lib\gcc-lib\djgpp\2.81\specs gpc version 19990503, based on gcc-2.8.1 ---------------------------------------------------- program prime (output); var p: array [0..49] of integer; h,i,j: integer; begin j := 0; for i := 1 to 100 do begin for h := 1 to j-1 do if 2*p[h]>i then h := j else if i mod p[h]= 0 then break; if h >= j then begin write(i,' '); p[j]:= i; inc(j) end end end.

1 0

help with gpc evaluation
by Thompson, Robin S 19 May '00

19 May '00

Hi, I'm currently evaluating gpc as a replacement for a commercial (and no longer supported) Pascal compiler on IBM RS/6000 systems running AIX Unix 4.2.1. The project we're intending to use it on contains nearly 250,000 lines of Pascal code, and needs to interface to libraries written in C. To help with my evaluation, I'd be grateful if anyone else on the list who has used gpc with a major project could let me know if it was successful, and also what, if any, problems were experienced. I'm also seeking general opinions on whether, given the current alpha status of gpc, it's stable enough to be used on such a large project? Many thanks in advance for any help offered. Regards, Robin Thompson P.S. I've successfully compiled and installed gpc 19991030 under gcc 2.95.2 on AIX 4.2.1 and 4.3, so please feel free to add these to platforms supported in the FAQ. Robin Thompson mailto:robin.thompson@eds.com

2 1

gpc questions.
by Brent & Cherith 17 May '00

17 May '00

I was wondering if it was possible to get gpc to compile for the palmos. I have downloaded the gcc to compile for the palmos. I have absolutely =no knowledge of gcc, I.E. how it works. I know that gpc should run on any machine where gcc runs on. Is this =correct for all intense purposes? So in theory I should be able to =compile gpc to to run on windows and compile the code into a palmos =format. I have read and sort of understood the documentation. The problems that I face are the following. Where do I get the source code for gcc (The palm version only gives =the updated source files) I have found what seem to be the files for gcc. But the file names =mean nothing to me. Confusion rules here for me???? Which files do I need, and which don't I. The same for gpc. Where do I get the latest source for gpc. I have searched but to no =avail. The exe's are easy enough to find. How do I then compile gpc to create palmos files. I use windows and my platform for development. I have a good knowledge of pascal, and I am able to convert the palmos =headers to pascal. But this is ofcourse to no avail if I can't get the =compiler to compile these sources. I have noticed that gpc itself is quite old. Is this correct. If so, is =gpc still been maintained? Any help would be appreciated. Brent.

2 1

Re: pascal compiler
by Nathalie Jarosz 17 May '00

17 May '00

Hi >For now, it would be useful to >know what computer, cpu, distribution and it's version no. that >you have. It's a pentium II, 450Mhz pc and the distribution is Mandrake 7.0. >You should have gpc in directory /usr/local/bin gpc is in /usr/bin >(If you build gpc from the sources make install puts it there >along with 9 other files) I have built gpc from the binaries from http://www.rpmfind.net. I took gpc-19990118-2rh6_i386.rpm from "mandrake cooker" as my linux is Mandrake 7.0. >When you invoke gpc it has it's own search path which you can >find with > gpc -print-search-dirs I got a list the following list:: install: /usr/lib/gcc-lib/i386-redhat-linux/egcs.2.91.66/ programs: /usr/lib/gcc-lib/i386-redhat-linux/egcs.2.91.66/ :/usr/lib/gcc-lib/i386-redhat-linux :/usr/lib/gcc/i386-redhat-linux/egcs.2.91.66/ :/usr/lib/gcc/i386-redhat-linux :/usr/i386-redhat-linux/bin/i386-redhat-linux/egcs.2.91.66/ :/usr/i386-redhat-linux/bin/ libraries: /usr/lib/gcc-lib/i386-redhat-linux/egcs.2.91.66/ :/usr/lib/gcc/i386-redhat-linux/egcs.2.91.66/ :/usr/i386-redhat-linux/lib/i386-redhat-linux/egcs.2.91.66/ :/usr/i386-redhat-linux/lib/ :/usr/lib/i386-redhat-linux/egcs.2.91.66/ :/usr/lib/ :/lib/i386-redhat-linux/egcs.2.91.66/ :/lib/ :/usr/lib/i386-redhat-linux/egcs.2.91.66/ :/usr/lib/ >In one of the "libraries" directory you should have this group of >files: > >SYSCALLS.c.X cpp* crtend.o gpc1* libgpc.a >cc1* crtbegin.o crtendS.o include/ specs >collect2* crtbeginS.o gpc-cpp* libgcc.a units/ I can't find all these files in one directory. In /usr/lib/gcc-lib/i386-redhat-linux/egcs.2.91.66/, I have: crtbegin.o crtend.o gpc-cpp* libgcc.a specs crtbeginS.o crtendS.o gpc1* libgpc.a units/ I have looked for the other files and I find them in : /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2 but I don't have gpc1*, libgpc.a, gcc-cpp* and /units here?... And moreover, I can't find these directories!... : :/usr/lib/gcc/i386-redhat-linux/egcs.2.91.66/ , /usr/i386-redhat-linux/lib/i386-redhat-linux/egcs.2.91.66/, /usr/i386-redhat-linux/lib/ or /usr/lib/i386-redhat-linux/egcs.2.91.66/ !!! I start to understand that gpc doesn't have all the informations it needs... How can I do to organize better all this? Do I have to clean all I have installed and start again with maybe a better choice for the binary or by building gpc from the source? Thanks again a lot in advance Nathalie

2 1

Re: 'gpc' Software
by Frank Heckenbach 17 May '00

17 May '00

Janet Casey wrote: > Hello! My name is Janet Casey and I'm working for the Free Software > Foundation assembling a database of free software world wide, which is > why I'm writing to you. > > We have this address listed as the maintainer for 'gpc'. Can you take a > quick look through the information I've assembled to see if everything > is correct and if there's anything I should add? I'd appreciate it > greatly. > > Thank you very much for your help! > > %%full-description: A 32/64 bit compiler without the 64kB or 640 kB > limit found on certain operating systems (even if run on those > systems). It runs on all operating systems supported by GNU C and can > act as a native or as a cross compiler between all supported > systems. Please insert here: It implements Standard Pascal (ISO 7185, level 1), a large subset of Extended Pascal (ISO 10206, aiming for full compliance), is highly compatible to Borland Pascal (version 7.0) with some Delphi extensions, and provides a lot of useful GNU extensions to help make programs portable. > %%maintainer: <gpc-request(a)hut.fi> That's an obsolete subscription address of the mailing list. The current maintainer is Peter Gerwinski <peter(a)gerwinski.de>. > %%keywords: Compiler, C, 32 bit, 64 bit I think this should be Pascal rather than C. :-) > %%web-page: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ Or shorter: http://home.pages.de/~GNU-Pascal/ (which is a redirector to the other URL). > %%redhat: ftp://sunsite.doc.ic.ac.uk/gnu/pascal/gpc-2.0.tar.gz Version 2.0 is very old. If there's no newer version at this place, please don't mention it and refer to the main source archive on agnes instead. > %%repository: Coming very soon. You'll get a separate message from Peter about it. > %%related: ncurses, gmp, rx > %%source-language: C Parts of the run time system are written in Pascal and will be built with the freshly built compiler during the make process. Therefore, it might not be necessary to mention it here, depending on your policy... > %%build-prerequisites: GNU make, sed, awk When getting the sources from CVS, also autoconf, flex, bison, gperf, makeinfo. > %%source-prerequisites: gcc > %%announce-list: gpc-announce(a)gnu.org > %%bug-list: bug-gpc(a)gnu.org Do these addresses exist? I was only aware of gpc-announce(a)gnu.de and gpc(a)gnu.de . 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: Pascal
by Maurice Lombardi 17 May '00

17 May '00

Waldemar Schultz a Ã©crit : > Now this is the remaining eerror log from compiling the DEMOS: > > gpc -o parserdemo.exe --autobuild parserdemo.pas > c:/temp\ccbqwnyf.s: Assembler messages: > c:/temp\ccbqwnyf.s:2010: Error: suffix or operands invalid for `mov' > > gpc -o realpower.exe --autobuild realpower.pas > c:/temp\ccbyznyf.s: Assembler messages: > c:/temp\ccbyznyf.s:1938: Error: suffix or operands invalid for `mov' > > some more Version conflict? I have the same bug. The conflisting assembler line is movl $L177,$__p_MPNGHS IIRC such a bug has already been reported to the gpc mailing list. Has it been corrected in more recent snapshots ? This was from gpc-19991030 (the most recent alpha on agnes, but developper versions are more recent) -- Maurice Lombardi Laboratoire de Spectrometrie Physique, Universite Joseph Fourier de Grenoble, BP87 38402 Saint Martin d'Heres Cedex FRANCE Tel: 33 (0)4 76 51 47 51 Fax: 33 (0)4 76 51 45 44 mailto:Maurice.Lombardi@ujf-grenoble.fr

2 1

Re:'gpc' Software
by Russ Whitaker 17 May '00

17 May '00

The Sunsite.doc URL is not valid try <http://sunsite.doc.ic.ac.uk/gnu/MORE_GNU/gnu-pascal/> you'll find directories called alpha, beta, current etc. Russ <russwhit(a)mind.net>

1 0

Re: faq addition (was Re:help!)
by Frank Heckenbach 16 May '00

16 May '00

Russ Whitaker wrote: > >... may be something about this should be added to FAQ ? > > Good idea. Perhaps the following: > > > Why shouldn't I just grab and install a binary? > ================================= Perhaps mention that this mostly applies to Linux/Unix. (Unix systems other than Linux are often administered by a trained administrator who will want to install from the sources, anyway.) For Dos (DJGPP) and MS-Windows systems, it's usually much easier to grab and install a binary. 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

1 0

faq addition (was Re:help!)
by Russ Whitaker 16 May '00

16 May '00

Hi >... may be something about this should be added to FAQ ? Good idea. Perhaps the following: Why shouldn't I just grab and install a binary? ================================= Linux may be Linux, but many details are left up to the implementor. If that isn't enough updating a seemingly unrelated piece of software can cause compatibility problems. Witness this exchange from the mailing list: >>I'm not an expert on this, but I remember that I installed on my Linux >>(RedHat 6.1) two RPM packages: >> >> gpc-19990118-1.i386.rpm >> gpc-extras-19990118-1.i386.rpm > I have install all but it doesn't run anyway! > My Linux is mandrake 7.0, it is maybe the problem?... Mandrake is NOT compatible with RedHat despite claims - you need less manual tweaks then in case with SuSE or Debian but ONLY RedHat is compatible with RedHat (even in this case only if you are lucky enough - see below). ESPECIALLY for GPC: Mandrake traditionally using very "advanced" (read: barely working) versions of gcc and gpc relies HEAVILY on gcc. If you DO NOT have RPM for EXACTLY your distribution then better (=easier) to recompile GPC from sources. And when I'm saying EXACTLY I mean exactly: RPM for RedHat 5.0 WILL NOT work in RedHat 5.2, RPM for RedHat 6.0 WILL NOT work in RedHat 6.2, etc. In some cases even "RedHat x.y" can be incompatible with "RedHat x.y with updates" :-(( Usually it can be easily tracked down and fixed by knowledgeable person (almost any package for any distribution can be forced to work in almost any other distribution) but just "rpm -Uvh" quite often will not work. When you are compiling program from sources autoconf usually can find and compensate most differences automagically but rpm/dpkg/apt is NOT sophisticated enough. That's why we recommend to start from sources when binaries do not work for you. Russ <russwhit(a)mind.net>

1 0

Re: pascal compiler
by Russ Whitaker 15 May '00

15 May '00

Hi Nathalie Jarosz wrote> > Today, I manage to install patch so I go on a little with the installation > but the step 2 (configuration) is not ok : > > 2. Configuring and building GNU CC GNU Pascal is automatically > configured with GNU CC. Configuration of GNU CC is treated in > depth in *Note the GCC installation instructions: > (gcc)Installation. > Chdir to the GCC object directory. (This can be a directory of > your choice, including the GCC source directory.) From there, run > the `configure' script in the GCC source directory. If both > directories are the same, the command > % ./configure > is sufficient to configure GCC in most cases > > When I do this, the following message appears : > " creating cache./config.cache > checking host system type ... configure : error : can not guess host type ; > you must specify one" Let's back up for a moment: 1. Do you have a working C compiler? try cc -v and you should get version info. The version is not important, the response is, as cc is used for the first of the three passes to build GPC. 2. Did you install a package of "include" files? These are a bunch of files ending in .h and found in a directory or sub directory called include. In the Slackware distribution the package is called linuxinc.tgz and they consider it important enough to provide two copies - one in the D series and the other in the K series. In a simplistic sense these files tell the C compiler how to use the library. Now try make, again Russ <russwhit(a)mind.net>

1 0

'gpc' Software
by Janet Casey 15 May '00

15 May '00

Hello! My name is Janet Casey and I'm working for the Free Software Foundation assembling a database of free software world wide, which is why I'm writing to you. We have this address listed as the maintainer for 'gpc'. Can you take a quick look through the information I've assembled to see if everything is correct and if there's anything I should add? I'd appreciate it greatly. FYI- a short explanation of some of the fields. Programs- any additional programs that come included with this one. Interface- Command line, interactive, X windows, console Support- listed only if it's something other than mailing list support Repository- Any CVS repositories where the program is listed Related- any GNU packages that might be of interest to users of this package Use Requirements- Required for using the executable Build Prereq.- Required for building this package Weak Prereq.- Useful (but not mandatory) to install before building this one Source Prereq.- Packages whose source code must be present in order to build this package. Please bear in mind that not all packages will have all the fields filled in (in fact, I don't think we've run across any yet that have all the fields filled in). If there's anything you think should be added (particularly individuals who have contributed) please e-mail me. Thank you very much for your help! %%name: gpc %%short-description: GNU Pascal compiler %%full-description: A 32/64 bit compiler without the 64kB or 640 kB limit found on certain operating systems (even if run on those systems). It runs on all operating systems supported by GNU C and can act as a native or as a cross compiler between all supported systems. There are a number of GNU extensions that help make the program portable. %%category: development %%license: GPL %%maintainer: <gpc-request(a)hut.fi> %%interface: Command line %%updated: 11 May 2000 %%keywords: Compiler, C, 32 bit, 64 bit %%GNU: yes %%web-page: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ %%support: %%doc: User reference manual available at http://agnes.dida.physik.uni-essen.de/~gnu-pascal/gpc-doc.html %%developers: Jukka Virtanen, Peter Gerwinski, Jan-Jaap van der Heijden %%contributors: Alexey Volokhov, Bill Currie, Frank Heckenbach, Matthias Klose, Nick Burrett %%sponsors: %%source: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ %%debian: http://www.debian.org/packages/stable/devel/gpc.html %%redhat: ftp://sunsite.doc.ic.ac.uk/gnu/pascal/gpc-2.0.tar.gz %%repository: %%related: %%source-language: C %%supported-languages: Pascal %%use-requirements: gcc, binutils %%build-prerequisites: %%weak-prerequisites: %%source-prerequisites: %%version: 2.0 released; gpc-19990118 beta on 5 Jun 1999 %%announce-list: gpc-announce(a)gnu.org %%announce-news: %%help-list: %%help-news: comp.lang.pascal.misc %%dev-list: gpc(a)gnu.de %%dev-news: v %%bug-list: bug-gpc(a)gnu.org Janet Casey Free Software Foundation www.gnu.org jcasey(a)gnu.org

1 0

Re: help!
by Nathalie Jarosz 15 May '00

15 May '00

-----Message d'origine----- De : Tomasz Kowaltowski <tomasz(a)dcc.unicamp.br> Ã : Nathalie Jarosz <njarosz(a)fr.packardbell.org> Date : vendredi 12 mai 2000 13:28 Objet : Re: help! >I'm not an expert on this, but I remember that I installed on my Linux >(RedHat 6.1) two RPM packages: > > gpc-19990118-1.i386.rpm > gpc-extras-19990118-1.i386.rpm I have install all but it doesn't run anyway! My Linux is mandrake 7.0, it is maybe the problem?... -----Message d'origine----- De : Peter Gerwinski <peter(a)gerwinski.de> Ã : Nathalie Jarosz <njarosz(a)fr.packardbell.org> Cc : gpc(a)gnu.de <gpc(a)gnu.de> Date : vendredi 12 mai 2000 11:18 Objet : Re: help! >Please install the C compiler for your system from a file of the >type gcc-something-XrhY_i386(1).rpm. This package will either >contain the needed libraries or have a dependency that will tell >you what else has to be installed. (The same dependency should >then be added to gpc-19990118-2rh6_i386(1).rpm.) there is no gcc-something-XrhY_i386(1).rpm. But I think it is not the problem bacause I have had to install some gcc thnigs to run gpc... Is anybody have already had the same problem or something similar?... Nathalie

3 2

help!
by Nathalie Jarosz 15 May '00

15 May '00

Hi Is someone can help me?!!! I really need to use a pascal compiler and I can't run it correctly. I manage to install a pascal compiler with "gpc-19990118-2rh6_i386(1).rpm... But, at first, when I did the command: $gpc -o test test.p, it says ld : cannot open crt1.o : no file or directory of this type. So, I tried to locate this file, and the only solution I find to go on was to copy it where I want to compile. It was the same for 'begincrt.o' and 'crti.o'. After this, the message was : ld : cannot find -lm. So, I create a variable called LFLAGS to export the libraries: $ export LFLAGs="-L /usr/i586-glibc20-linux/lib" and with the line: $ gpc -o test $LFLAGS test.p 'test' is created but when I run it, the following message appear: 'segmentation fault' What does it mean? thanks a lot in advance for your help, I guess some people use this so explain how you do to run it correctly, it's really important for me. Nathalie

2 1

Re: Help needed, path configuration
by Frank Heckenbach 09 May '00

09 May '00

Ryan K C Wong wrote: > I cannot get GPC working: it always reports missing files. > > I use DJGPP 2.02 and GPC20BB for DOS with GO32V2 support > (please see manifest below) > > Thank you. > > > Description > *************************************** > The first file it says missing is the DJGPP.DJL > the path of the file is C:\DJGPP\LIB\DJGP.DJL > > after I copied this file to the same directory of my > program's source file, it continues to report that > every unit 'CRT0', .... is missing. > > I suspect that the configuration file is corrupted. > I included the DJGPP.ENV here. See below. > > ******************************************* > ***** djgpp.env **************************** > ******************************************* There's no gpc section there. Try adding: [gpc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib 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

1 0

Re: - Initialising enumerated types
by Frank Heckenbach 07 May '00

07 May '00

Wren Lee wrote: > DEC-Pascal has the ability to initialise a boolean or an enumerated type > from a text file.The text is case insensitive and is read just as any > other variable. Is there a way to do this with GPC? No. For Booleans, it would not be too difficult to implement, but for enum types, it would require that they're values (which are program identifiers otherwise) be kept in the executable which is not provided for currently (besides debug info). > If not, are there > any good ways to emulate this behaviour? Something like the following. It also illustrates the limitations... program ReadBooleanEnumDemo; uses GPC; procedure ReadWord (var f : Text; var s : String); const WordChars = ['A' .. 'Z', 'a' .. 'z', '_', '0' .. '9']; begin s := ''; while f^ in SpaceCharacters do if EOLn (f) then Readln (f) else Get (f); while not EOF (f) and not EOLn (f) and (f^ in WordChars) do begin s := s + f^; Get (f) end end; function ReadBoolean (var f : Text) : Boolean; var s : TString; begin ReadWord (f, s); LoCaseString (s); if s = 'false' then ReadBoolean := False else if s = 'true' then ReadBoolean := True else begin IOErrorCString (464, FileName (f)); { error when reading from % } ReadBoolean := False end end; function ReadEnum (var f : Text; const IDs : array of PString) : Integer; var s : TString; i : Integer; begin ReadWord (f, s); LoCaseString (s); i := Low (IDs); while (i <= High (IDs)) and (LoCaseStr (IDs [i]^) <> s) do Inc (i); if i <= High (IDs) then ReadEnum := i else begin IOErrorCString (464, FileName (f)); { error when reading from % } ReadEnum := 0 end end; procedure WriteEnum (var f : Text; EnumVal : Integer; const IDs : array [m .. n : Integer] of PString); begin Write (f, IDs [EnumVal]^) end; type TFruit = (Apple, Orange, Banana); const FruitIDs : array [TFruit] of PString = (@'Apple', @'Orange', @'Banana'); var BoolVar : Boolean; FruitVar : TFruit; begin Write ('Enter a boolean and a fruit: '); BoolVar := ReadBoolean (Input); FruitVar := TFruit (ReadEnum (Input, FruitIDs)); { we have to cast the result to the enum type } Writeln ('You entered:'); Writeln (BoolVar); WriteEnum (Output, Ord (FruitVar), FruitIDs) end. 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

1 0

- Initialising enumerated types
by Wren Lee 05 May '00

05 May '00

DEC-Pascal has the ability to initialise a boolean or an enumerated type from a text file.The text is case insensitive and is read just as any other variable. Is there a way to do this with GPC? If not, are there any good ways to emulate this behaviour? I am currently using GPC v.19991030 based on 2.95.2 19991024 on a LINUX PC. The following program shows the functionallity that I am trying to emulate. Thanks in advance, Lee. --- PROGRAM Read_Enum(input, output); TYPE colour = (red, green, blue); VAR flag : boolean; { Test boolean } mycol : colour; { Test enumerated type } ip_file : TEXT; { input data file } filename : String(80); i : integer; BEGIN filename := "enum.dat"; open(ip_file, filename, history:=old); reset(ip_file); FOR i := 1 to 3 DO BEGIN readln(ip_file, flag); IF (flag) then writeln("Flag is true") ELSE writeln('Flag is false'); END; FOR i := 1 to 3 DO BEGIN readln(ip_file, mycol); CASE mycol OF red : writeln("Your colour is red"); green : writeln("Your colour is green"); blue : writeln("Your colour is blue"); END; END; close(ip_file); END. enum.dat: ======== true False TrUE Red green BLUE output: ====== Flag is true Flag is false Flag is true Your colour is red Your colour is green Your colour is blue -- The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful.

1 0

Bombed Compilation on OSF/1
by John L. Ries 04 May '00

04 May '00

The compilation job told me to submit a full bug report, so here goes... Hardware: DEC 3000/800 AXP OS: Digital UNIX 4.0E (aka OSF/1) GCC Version: 2.95.2 GPC Version: 19991030 Where it dies: ../.././xgpc -B../.././ -c -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 -DRTS_RELEASE_STRING="'__GPC_RTS_VERSION_`cat /attila/src/gcc-2.95.2/gcc/p/rts/rts_release`__'" -DBSD_RTS=0 `if [ x@with_shared@ = xyes ] ; then echo -fPIC; fi` --unit-path=/attila/src/gcc-2.95.2/gcc/p/rts --automake /attila/src/gcc-2.95.2/gcc/p/rts/heap.pas /attila/src/gcc-2.95.2/gcc/p/rts/error.pas: In function `Geterrormessage': /attila/src/gcc-2.95.2/gcc/p/rts/error.pas:365: Internal compiler error in `copy_to_mode_reg', at explow.c:669 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. gpc1: ../.././xgpc exited with status 1 /attila/src/gcc-2.95.2/gcc/p/rts/heap.pas:30: module/unit `error' could not be compiled gmake[2]: *** [heap.o] Error 1 gmake[2]: Leaving directory `/attila/src/gcc/gcc/p/rts' gmake[1]: *** [pascal.rts] Error 2 gmake[1]: Leaving directory `/attila/src/gcc/gcc' gmake: *** [all-gcc] Error 2 I compiled in a separate directory from the source (per standard advice), ran configure without arguments, followed by gmake (ie GNU make) LANGUAGES=pascal (I installed the other stuff previously). ------------------------------------------------------- John L. Ries Salford Systems Phone: (619)543-8880 x25 or (619)667-0056 FAX: (619)543-8888 E-Mail: jries(a)salford-systems.com _______________________________________________________

1 0

pascal compiler
by Nathalie Jarosz 04 May '00

04 May '00

hello! Today, I manage to install patch so I go on a little with the installation but the step 2 (configuration) is not ok : 2. Configuring and building GNU CC GNU Pascal is automatically configured with GNU CC. Configuration of GNU CC is treated in depth in *Note the GCC installation instructions: (gcc)Installation. Chdir to the GCC object directory. (This can be a directory of your choice, including the GCC source directory.) From there, run the `configure' script in the GCC source directory. If both directories are the same, the command % ./configure is sufficient to configure GCC in most cases When I do this, the following message appears : " creating cache./config.cache checking host system type ... configure : error : can not guess host type ; you must specify one" What does it mean? Thanks a lot for you answer, nathalie

2 1

Help needed, path configuration
by Ryan K C Wong 04 May '00

04 May '00

I cannot get GPC working: it always reports missing files. I use DJGPP 2.02 and GPC20BB for DOS with GO32V2 support (please see manifest below) Thank you. Description *************************************** The first file it says missing is the DJGPP.DJL the path of the file is C:\DJGPP\LIB\DJGP.DJL after I copied this file to the same directory of my program's source file, it continues to report that every unit 'CRT0', .... is missing. I suspect that the configuration file is corrupted. I included the DJGPP.ENV here. See below. My Install path: C:\DJGPP I unzipped everything into this directory, with path reconstruction and long filename support. DOS search path: set DJGPP=C:/DJGPP/DJGPP.ENV ************************************** ******************************************* ****** files in the manifest directory *** ******************************************* BNU281B MFT 525 01-12-98 BNU281B VER 65 07-16-97 DJDEV202 MFT 3,040 12-13-98 DJDEV202 VER 38 12-13-98 GCC2952B MFT 1,133 10-26-99 GCC2952B VER 53 10-25-99 GDB418B MFT 556 08-01-99 GDB418B VER 55 05-06-99 MAK377B MFT 274 08-14-98 MAK377B VER 48 08-14-98 TXI312B MFT 517 05-22-98 TXI312B VER 48 05-22-98 GPC20BB VER 86 01-18-99 GPC20BB MFT 1,964 01-18-99 ****************************************** ******************************************* ***** djgpp.env **************************** ******************************************* #= Don't edit this line unless you move djgpp.env outside #= of the djgpp installation directory. If you do move #= it, set DJDIR to the directory you installed DJGPP in. #= DJDIR=%:/>DJGPP% +USER=dosuser +GROUP=root +TMPDIR=%DJDIR%/tmp +EMU387=%DJDIR%/bin/emu387.dxe +LFN=y +TEXMFMAIN=%DJDIR%/share/texmf [bison] BISON_HAIRY=%DJDIR%/lib/bison.hai BISON_SIMPLE=%DJDIR%/lib/bison.sim [cpp] CPLUS_INCLUDE_PATH=%/>;CPLUS_INCLUDE_PATH%%DJDIR%/lang/cxx;%DJDIR%/include C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/include OBJCPLUS_INCLUDE_PATH=%/>;OBJCPLUS_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/lang/objc OBJC_INCLUDE_PATH=%/>;OBJC_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/lang/objc [gcc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib [info] INFOPATH=%/>;INFOPATH%%DJDIR%/info;%DJDIR%/gnu/emacs/info +INFO_COLORS=0x1f.0x31 +INFO_LINES=40 [emacs] INFOPATH=%/>;INFOPATH%%DJDIR%/info;%DJDIR%/gnu/emacs/info [less] +LESSBINFMT=*k<%%X> +LESSCHARDEF=8bcccbcc12bc5b95.b127.b LESS=%LESS% -h5$y5$Dd2.0$Du14.0$Ds4.7$Dk9.0$ +LESSSEPARATOR=/ [ispell] +ISPELL_HOME=%DJDIR%/lib +ISPELL_DICTDIR=%DJDIR%/lib +ISPELL_COLORS=0x1e.0x74 +LINES=40 [locate] +LOCATE_PATH=%DJDIR%/lib/locatedb.dat [ls] +LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31 :*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01 ;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37: *.gl=01;37:*.dl=01;37:*~=08:*.bak=08: [dir] +LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31 :*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01 ;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37: *.gl=01;37:*.dl=01;37:*~=08:*.bak=08: [vdir] +LS_COLORS=no=00:fi=00:di=36:lb=37;07:cd=40;33;01:ex=32:*.cmd=32:*.tar=01;31:*.tgz=01;31:*.arj=01;31 :*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.deb=01;31:*.jpg=01;34:*.gif=01 ;34:*.bmp=01;34:*.ppm=01;34:*.tga=01;34:*.xbm=01;34:*.xpm=01;34:*.tif=01;34:*.mpg=01;37:*.avi=01;37: *.gl=01;37:*.dl=01;37:*~=08:*.bak=08: [enscript] ENSCRIPT_LIBRARY=%DJDIR%/share/enscript [bash] PATH=%/>PATH% [sh] PATH=%/>PATH% [groff] +GROFF_TMAC_PATH=.;%DJDIR%/share/groff/tmac +GROFF_TYPESETTER=ascii +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font [eqn] +GROFF_TMAC_PATH=.;%DJDIR%/share/groff/tmac +GROFF_TYPESETTER=ascii [grodvi] +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font [grolj4] +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font [grops] +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font +GROFF_TMPDIR=%DJDIR%/tmp [grotty] +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font [indxbib] +GROFF_EIGN=%DJDIR%/share/groff/eign [lkbib] +REFER=%DJDIR%/share/Ind [refer] +REFER=%DJDIR%/share/Ind +GROFF_TMPDIR=%TMPDIR% [troff] +GROFF_TMAC_PATH=.;%DJDIR%/share/groff/tmac +GROFF_TYPESETTER=ascii +GROFF_FONT_PATH=.;%DJDIR%/share/groff/font [gawk] +AWKPATH=.;%DJDIR%/share/awk [awk] +AWKPATH=.;%DJDIR%/share/awk [man] MANPATH=%/>MANPATH%;%DJDIR%/man;%DJDIR%/info PAGER=%DJDIR%/bin/less.exe ******************************************* ****end of DJGPP.ENV**************** *******************************************

1 0

Re: GPC on Solaris (fwd)
by Frank Heckenbach 04 May '00

04 May '00

Veselic wrote: > Dear Dr. Heckenbach, ^^^ Not yet. ;-) > thanks for your prompt answer. One more information: > among my sources there are other such 'pairs' i.e. > programs that differ only in the precision 'single' > and 'extended', respectively. All those compile OK > on my Sun, however. > > If this is really a bug in the compiler then I think > it should be repaired with certain priority. I've verified now that my fix indeed cures the problem, as well as a problem with `Complex/Real', reported by Maurice Lombardi some time ago. So it will be fixed in the next release or snapshot. 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

1 0

Re: GPC on Solaris (fwd)
by Frank Heckenbach 04 May '00

04 May '00

Veselic wrote: > Dear Dr. Gerwinski, dear GPC-ers, > > After having installed the new version of gpc all > my sources (originally written for Turbo Pascal, > hundreds of them) are compiled smoothly, BUT ONE. > Here is the story: > > System description: > > SunOS mph 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-2 > > GPC description: > > GNU Pascal version 19991030, based on 2.95.2 19991024 (release), > compiled Nov 1$ > Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. > > Here I try compiling: > > gpc --borland-pascal -o sj sj.p > sj.p: In function `Gjgt_dec_new': > sj.p:466: Internal compiler error in `emit_library_call_value', at calls.c:3198 > Please submit a full bug report. > See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. > > Additional information: > > 1. The corresponding area in the source is: > > 465 x := sqrt( beta * w ) ; > 466 y := 0.5 * alfa / x ; > 467 z := 0.5 * gama / x ; > > 2. another source (named ej.p) which differs from sj.p ONLY in having > 'extended' whenever sj.p has 'single', COMPILES AND EXECUTES SMOOTHLY. > > 3. On my PC-Linux with the gpc version > > GNU Pascal version 19990118, based on gcc-2.8.1, compiled Jul 6 1999 > 16:08:58. > Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. > > all sources, including the incriminated sj.p, compile OK. Yes, that's a known bug, under exactly the circumstances you observed (one operand is Single or Double, and only on Sparc). I think I found the cause of the bug, and if so, it will be fixed in the next release, but I've yet to test it well. 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

GPC: how to patch gcc 2.95.2 ?
by Martin Maechler 04 May '00

04 May '00

I've downloaded the current GPC tar file, unpacked it, and moved (actually symlinked) the p/ directory into gcc-2.95.2/ (which is the unpacked source of the current gcc). Now your INSTALL file tells me to patch gcc with the appropriate p/diffs/*** Which one do I need? There are only ones for old gcc's.. Or is it unnecessary to patch 2.95.x at all ? {{if not, couldn't you have the gcc developers adopt your patches? it would make gpc MUCH MORE reputable if one wouldn't have to patch such a widely used and approved piece of software as gcc .... }} {Your FAQ dates from 1997, which made me not look at it, at all..} Thank you for GPC (and your answers..)! -- Martin Maechler <maechler(a)stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO D10 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><

3 3

pascal compiler
by Nathalie Jarosz 04 May '00

04 May '00

Hello! I still have a problem with the pascal compiler installation but now I have more informations... And it is more a problem with linux than with the installation itself. Here is the generic procedure for installing GNU Pascal : 1. Unpack the source distributions. From a directory of your choice (e.g. `/usr/local/src'), unpack the GNU CC and GNU Pascal source distributions. This will create separate subdirectories for GCC and GPC. `cd' to the GPC directory (`/usr/local/src/gpc' in the example above) and move the contents (a subdirectory `p') to the GCC directory (for instance `usr/local/src/gcc-2.8.1'). At this point, all is ok. Next, go to the GCC source directory and apply the GCC patch required by GNU Pascal: % patch -s -p1 < p/diffs/gcc-2.8.1.diff The problem arise at this moment when I do "cd gcc-2.8.2; patch -s -p1 <p/diffs/gcc-2.8.1.diff", the following message appears : "bash : patch : command not found". So, I understand that it is not a problem with the installation but with my linux configuration. The command patch is missing and I have no idea of how to get it. let me know if my understanding is correct and if you can help me, thanks a lot in advance, Nathalie

2 1

Re: Is it possible that GPC doesnt recognize "file of char" but "text" ?
by Frank Heckenbach 03 May '00

03 May '00

Tim Kaulmann wrote: > A friend told me that his GPC Compiler did not accept "file of char" at his > variable declaration part. He tried "text" instead and it worked. > > Is this solved in a newer version of GPC or is this an unknown bug ? AFAIK, GPC has always supported `file of Char' (at least, for several years, and I don't have an older version to test -- if he's still using GPC 2.0 or such an old version, he might be better off upgrading, also for other reasons). It is true, however, that GPC doesn't treat `file of Char' and `Text' as equivalent (e.g., Readln/Writeln applies to `Text' files only). That's according to the standard, AFAIK, and the same with most other Pascal compilers. But ISTR there are a few compilers (Sun Pascal?) that treat them as equivalent, so if he tried code written for these compilers, it might be that he used `file of Char' where actually `Text' was correct. If that's not the cause, please get some sample code from him, and state the compiler version used. 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

1 0

Is it possible that GPC doesnt recognize "file of char" but "text" ?
by Tim Kaulmann 03 May '00

03 May '00

Hello again. A friend told me that his GPC Compiler did not accept "file of char" at his variable declaration part. He tried "text" instead and it worked. Is this solved in a newer version of GPC or is this an unknown bug ? Greetings, Tim

1 0

BP toys in GPC
by Mariusz Zynel 03 May '00

03 May '00

Hi First of all let me thank Authors for supplying SetTextBuf in GPC (20000401 snapshot). There are still, however, some BP functions missing in GPC: SeekEOLN, SeekEOF, Include and Exclude. Providing them in GPC would make porting from BP easier. Maybe the following code could be utilized: const acTAB = #009; acLF = #010; acCR = #013; acWS = #032; type AnySetElement = 0..255; AnySet = set of AnySetElement; function SeekEoln(var aFile: Text): Boolean; var CurPos: Integer; CurChar: Char; begin if not Eoln(aFile) and not Eof(aFile) then begin repeat CurPos := FilePos(aFile); Read(aFile, CurChar); until ((CurChar <> acTAB) and (CurChar <> acWS)) or Eof(aFile); Seek(aFile, CurPos); end; SeekEoln := Eoln(aFile); end; function SeekEof(var aFile: Text): Boolean; begin while SeekEoln(aFile) and not Eof(aFile) do Readln(aFile); SeekEof := Eof(aFile); end; procedure Include(var aSet: AnySet; aElement: AnySetElement); begin aSet := aSet + [aElement]; end; procedure Exclude(var aSet: AnySet; aElement: AnySetElement); begin aSet := aSet - [aElement]; end; Regards -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

2 1

Re: BP toys in GPC
by Frank Heckenbach 02 May '00

02 May '00

Mariusz Zynel wrote: > First of all let me thank Authors for supplying SetTextBuf in GPC > (20000401 snapshot). There are still, however, some BP functions > missing in GPC: SeekEOLN, SeekEOF, Include and Exclude. Providing > them in GPC would make porting from BP easier. Thanks for the hint. In fact, Include and Exclude have been added on Feb 19, so if you have any luck with 20000401, you have these routines already... > Maybe the following > code could be utilized: > > const > acTAB = #009; > acLF = #010; > acCR = #013; > acWS = #032; Just a few comments, no offense intended: I think it's better not to assume a particular character encoding (even though it's unlikely to change nowadays). ' ' is probably easier than #32, and for Tab, LF and CR, GPC supports "\t", "\n" and "\r" (in the releases up to now only if `char-escapes' is enabled, starting from the next release always in double-quoted strings). Also, it better to avoid `Seek'ing. It might be problematic on systems that have to do translation on text files (i.e., Dos -- but I don't feel like trying this out now), and is probably a little inefficient on any system. Since the BP routines actually skip the white space found, and Pascal provides look-ahead to the next character in text files with `FileVar^', seeking can easily be avoided here. I've put similar code (BP compatible in that it treats everything < ' ' as white space) into the RTS now. However, in BP the argument is optional (and defaults to Input), so we need compiler magic in GPC to do this as well. Peter, will you do this (I hope it's easy to do, just like with a number of other I/O routines)? 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

1 0

Re: GPC on Solaris (fwd)
by Veselic 02 May '00

02 May '00

Dear Dr. Gerwinski, dear GPC-ers, After having installed the new version of gpc all my sources (originally written for Turbo Pascal, hundreds of them) are compiled smoothly, BUT ONE. Here is the story: System description: SunOS mph 5.7 Generic_106541-08 sun4u sparc SUNW,Ultra-2 GPC description: GNU Pascal version 19991030, based on 2.95.2 19991024 (release), compiled Nov 1$ Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. Here I try compiling: gpc --borland-pascal -o sj sj.p sj.p: In function `Gjgt_dec_new': sj.p:466: Internal compiler error in `emit_library_call_value', at calls.c:3198 Please submit a full bug report. See <URL:http://www.gnu.org/software/gcc/faq.html#bugreport> for instructions. Additional information: 1. The corresponding area in the source is: 465 x := sqrt( beta * w ) ; 466 y := 0.5 * alfa / x ; 467 z := 0.5 * gama / x ; 2. another source (named ej.p) which differs from sj.p ONLY in having 'extended' whenever sj.p has 'single', COMPILES AND EXECUTES SMOOTHLY. 3. On my PC-Linux with the gpc version GNU Pascal version 19990118, based on gcc-2.8.1, compiled Jul 6 1999 16:08:58. Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. all sources, including the incriminated sj.p, compile OK. Very grateful in advance for your help, K. Veselic.

1 0

Building 20000401 snapshot on Solaris 8 x86
by Mariusz Zynel 01 May '00

01 May '00

Hi All I've found 20000401 snapshot and tried to build it on my Solaris 8 x86 box. I faced following problems: 1. there are bash extensions like ! [ ... ] used in Makefiles: - Make-lang-2.95.in, - Make-lang-old.in, - Make-lang.in, and - Make-lang - but this one belongs to gcc distribution. In result some precompiled objects do not install. 2. xgpc failed to compile rts modules like heap.pas etc.: ../.././xgpc -B../.././ -c -I. -W -Wall -Wpointer-arith -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -g -O2 -DRTS_RELEASE_STRING="'__GPC_RTS_VERSION_`cat /export/home/admin/soft/gcc-2.95.2/gcc/p/rts/rts_release`__'" -DBSD_RTS=0 `if [ x"@with_shared@" = xyes ] ; then echo -fPIC; fi` --unit-path=/export/home/admin/soft/gcc-2.95.2/gcc/p/rts --automake heap.pas xgpc: Internal compiler error: program gpc1 got fatal signal 11 gpc1: ../.././xgpc exited with status 1 The workaround was to remove RTS_WARN flag in p/rts/Makefile 3. GNU make and M4 are necessary to build GPC, but this is a minor problem as we all use GNU tools. Now to link a Pascal program I have to either, use --automake/build, or specify objects it depends on. What is the reason for this modification? Is there any switch to force GPC to find necessary units without --automake/build, as it was before? Thanks in advance for any suggestions? -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

2 2

bug
by Toby Ewing 01 May '00

01 May '00

Hi, all. I've been fighting a bug for a while, and when I stripped it down to its basics, I was surprised. My test program is appended. The issue involves arrays of size > 255. When I use Ymax = Zmax = 250, the program runs fine. When I use Ymax = Zmax = 260, the portion of the program that runs in Main works fine, but the procedure stops at y = 7, z = 260 - the program hangs, with ^C ineffective. I'm running a pentium 400 under Win98. I've had no trouble with this in small arrays, but 256 seems to be a divide of some sort. Any suggestions appreciated. Toby Toby Ewing Soil Scientist, Iowa State University ------------------------------------------------------------------- Program TestLgArray; Const Xmax = 25 ; {physical space - grid units} Ymax = 260; {physical space - grid units} Zmax = 260; Type Compary = array[1..Ymax, 1..Zmax] of integer; var Comp : Compary; x, y, z : integer; {________________________________________________ } Procedure Zero; var Comp : Compary; x, y, z : integer; begin writeln('Procedure:'); readln; for y := 1 to Ymax do begin {zero the comp array} for z := 1 to Zmax do Comp[y,z] := 0; writeln('y=', y:3, ' z=', z:1); end; end; {________________________________________________ } begin {Main Program} writeln('Main:'); readln; for y := 1 to Ymax do begin {zero the comp array} for z := 1 to Zmax do Comp[y,z] := 0; writeln('y=', y:3, ' z=', z:1); end; Zero; write(' done'); end.

4 3

gpc 19991930 and gcc2.95.2 on LinuxPPC
by Thanh To 01 May '00

01 May '00

Hi, I follow the instruction below trying to build gpc 19991030 and gcc2.95.2 on my LinuxPPC tar xvfz gcc-2.95.2.tar.gz tar xvfz gpc-19991030.tar.gz mv gpc/p gcc-2.95.2/gcc/ mkdir gcc-2.95.2/gpc cd .. ./configure However when I do the make, I got the following error message: make[2]: Leaving directory `/export/home/accounts/tto/gcc-2.95.2/gcc/java' gcc -DIN_GCC -DHAIFA -g -O2 -DHAVE_CONFIG_H -o cc1obj toplev.o version.o tree.o print-tree.o s tor-layout.o fold-const.o function.o stmt.o except.o expr.o calls.o expmed.o explow.o optabs.o intl. o varasm.o rtl.o print-rtl.o rtlanal.o emit-rtl.o genrtl.o real.o dbxout.o sdbout.o dwarfout.o dwarf 2out.o xcoffout.o bitmap.o alias.o gcse.o integrate.o jump.o cse.o loop.o unroll.o flow.o stupid.o c ombine.o varray.o regclass.o regmove.o local-alloc.o global.o reload.o reload1.o caller-save.o insn- peep.o reorg.o haifa-sched.o final.o recog.o reg-stack.o insn-opinit.o insn-recog.o insn-extract.o i nsn-output.o insn-emit.o lcm.o profile.o insn-attrtab.o rs6000.o getpwd.o convert.o mbchar.o dyn-st ring.o splay-tree.o graph.o sbitmap.o resource.o hash.o objc-parse.o objc-act.o c-lex.o c-pragma.o c -decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-iterate.o obstack.o ../libiberty/li biberty.a cd p; make "AR_FLAGS_FOR_TARGET=rc" "AR_FOR_TARGET=ar" "BISON=bison" "BISONFLAGS=" "CFLAGS=-g -O2" " CLIB=" "GCC_FOR_TARGET=/zubat/export/home/accounts/tto/gcc-2.95.2/gcc/xgcc -B/zubat/export/home/acco unts/tto/gcc-2.95.2/gcc/ -B/usr/local/powerpc-unknown-linux-gnu/bin/ -I/usr/local/powerpc-unknown-li nux-gnu/include" "LDFLAGS=" "LEX=flex" "LEXFLAGS=" "LN=ln" "LN_S=ln -s" "MAKEINFO=/zubat/export/home /accounts/tto/gcc-2.95.2/texinfo/makeinfo/makeinfo " "MAKEINFOFLAGS=" "RANLIB_FOR_TARGET=ranlib" "RA NLIB_TEST_FOR_TARGET=[ -f ranlib ] || ( [ "powerpc-unknown-linux-gnu" = "powerpc-unknown-linux-gnu" ] && [ -f /usr/bin/ranlib -o -f /bin/ranlib ] )" "SHELL=/bin/sh" "STAGE_PREFIX=" "exeext=" "build_ex eext=" "objext=.o" "exec_prefix=/usr/local" "prefix=/usr/local" "local_prefix=/usr/local" "gxx_inclu de_dir=/usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.2/../../../..`echo /usr/local | sed -e 's|^/usr/local||' -e 's|/[^/]*|/..|g'`/include/g++-3" "tooldir=/usr/local/powerpc-unknown-linux-gnu" "gcc_tooldir=/usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.2/../../../../powerpc-unknown-li nux-gnu" "bindir=/usr/local/bin" "libsubdir=/usr/local/lib/gcc-lib/powerpc-unknown-linux-gnu/2.95.2" "datadir=/usr/local/share" "distdir=../tmp/\$(subdir)" "localedir=/usr/local/share/locale" "CC=gcc" "CROSS=" "X_CFLAGS=" "EXTRA_LIBS=" "MAYBE_TARGET_DEFAULT=" "MAYBE_USE_COLLECT2=" "SCHED_CFLAGS=-DHA IFA" "includedir=`echo '/usr/local/include'|sed -e 's/\\$/\\\\&&/g'`" "libsubdir=`echo '/usr/local/l ib/gcc-lib/powerpc-unknown-linux-gnu/2.95.2'|sed -e 's/\\$/\\\\&&/g'`" "target_alias=powerpc-unknown -linux-gnu" "version=2.95.2" "target_alias=powerpc-unknown-linux-gnu" "program_transform_name=s,x,x, " "program_transform_cross_name=s,^,powerpc-unknown-linux-gnu-," "exeext=" "GCC_FOR_TARGET=/zubat/ex port/home/accounts/tto/gcc-2.95.2/gcc/xgcc -B/zubat/export/home/accounts/tto/gcc-2.95.2/gcc/ -B/usr/ local/powerpc-unknown-linux-gnu/bin/ -I/usr/local/powerpc-unknown-linux-gnu/include" "GPC_FOR_TARGET =./xgpc -B./" "GPCSOLIBSHORTNAME=libgpc.so" "GPCSOLIBDIR=lib" "WITH_SHARED=@with_shared@" ../gpc1 make[2]: Entering directory `/export/home/accounts/tto/gcc-2.95.2/gcc/p' gcc -c -DIN_GCC -DGPC -g -O2 -DHAIFA -I. -I.. -I. -I./.. -I./../config -I./../../include ./.. /stor-layout.c ./../stor-layout.c:64: initializer element is not constant make[2]: *** [stor-layout.o] Error 1 make[2]: Leaving directory `/export/home/accounts/tto/gcc-2.95.2/gcc/p' make[1]: *** [gpc1] Error 2 make[1]: Leaving directory `/export/home/accounts/tto/gcc-2.95.2/gcc' make: *** [all-gcc] Error 2 How can I fix this problem? Thank you. Thanh To

1 0

String types and relational operators
by Tomasz Kowaltowski 01 May '00

01 May '00

We are using for teaching purposes the GPC compiler under Linux (RedHat 6.1) which was installed from the following RPM packages: gpc-19990118-1.i386.rpm gpc-extras-19990118-1.i386.rpm Our Pascal programs are compiled with the "--borland-pascal" option. I noticed a problem with the type "String" (and the derived types like "String[10]") and the relational operators which do not seem to return correct results. The following test program seems illustrate this point: ---------------------------------------------------------------------- program test; procedure Compare(var x,y : String); begin if x=y then Writeln('"',x,'" = "',y,'"') else if x>y then Writeln('"',x,'" > "',y,'"') else if x<y then Writeln('"',x,'" < "',y,'"') else Writeln('"',x,'" ? "',y,'"') end; { Compare } var a,b : String; Empty,Zeros : String; begin a := 'abcd'; b := 'abce'; Empty := ''; Zeros := '0000'; Compare(Zeros,Zeros); Compare(Zeros,a); Compare(a,Zeros); Compare(Empty,Empty); Compare(Empty,a); Compare(a,Empty); Compare(a,a); Compare(a,b) end. ---------------------------------------------------------------------- The following output was produced: "0000" = "0000" "0000" > "abcd" [*] "abcd" ? "0000" [*] "" = "" "" > "abcd" [*] "abcd" ? "" [*] "abcd" = "abcd" "abcd" > "abce" [*] which shows that some results are wrong (marked with [*]). Any suggestions as to what might be wrong? -- Tomasz Kowaltowski

4 3

Help to work with GPC on Windows NT
by Anuradha 01 May '00

01 May '00

Hello, I want to compile Pascal programs using GNU-pascal. I FTPed the zip files from the agnes.dida.physik.uni-essen.de/gnu-pascal

3 2

GPC and gcc-2.95.2-1-i586-mingw32
by Václav Haisman 01 May '00

01 May '00

Is it possible to run GPC and gcc-2.95.2-1-i586-mingw32? If it is possible, is it possible with precompiled binaries from ftp://agnes.dida.physik.uni- essen.de/gnu-pascal/current/binary/gpc-19990118.i386-pc-mingw32.zip? WilX

1 0

Re: faq version 4
by Russ Whitaker 01 May '00

01 May '00

Hi Tom wrote: > > * two forms of apparently the same thing: > SvgaLib > Svgalib > Agreed. Did some checking and found: svgalib directory name, start of file names Svgalib proper noun in man page, etc but no SvgaLib while at it, visited agnes: ftp://agnes.dida.physik.uni-essen.de/~nicola din't work, but ftp://agnes.dida.physik.uni-essen.de/home/nicola did. The file found there is all lower case. Will correct the FAQ Thanks Russ <russwhit(a)mind.net> ps: wrote the editor I'm using - ( in GNU Pascal ) it's fast, easy, full screen, but it doesn't spell check and it's not an IDE

1 0

note from Professor Knuth
by Maggie McLoughlin 01 May '00

01 May '00

Dear GPC folks, I just installed GPC 2.8.1 on my new Linux machine, which is replacing the Sparc that I've been using since 1989. Naturally I want to be able to achieve on my new machine what I could do on my old one; thus it is important to me that I can still compile the absolutely official Pascal-based version of TeX, even though everybody [including me] uses the Web2C-translated version for production runs. So I began today to look at those old programs and to remind myself about Pascal syntax. When TeX was being developed in the late 70s and early 80s, we chose Pascal for TeX82 because it was the most widely understood language. People told me that the Pascal versions of TeX and METAFONT were ported to more than 100 different platforms. I myself used Pascal-H on a TOPS10 machine, later Berkeley Pascal on an early version of SunOS, later a much better Sun Pascal that was developed I think in Russia. Since these programs were much larger than typical student-oriented Pascal source code, they tended to find at least one bug in every new Pascal compiler they faced. "New users find new bugs." Sure enough, it seems GNU Pascal is no exception... I believe your otherwise-admirable program is actually otherwise-flaky, in the sense that it fails to parse the "otherwise" keyword for case-statement defaults when the case statement in question includes another (nested) case statement. For example, gpc does not parse the following program: ---------- cut here for bug.p ------------------------------------- program bug(input,output); var x : integer; begin readln(x); case x mod 2 of 0 : begin case x mod 4 of 2 : writeln('oddly even'); 0 : writeln('evenly even'); end; { case } end; otherwise writeln('odd'); end; { case } end. ------------------------------------------------------------------- On the other hand it handles a similar program with ease: ---------- cut here for nobug.p ----------------------------------- program bug(input,output); var x : integer; begin readln(x); case x mod 2 of 0 : begin if (x mod 4)=2 then writeln('oddly even') else writeln('evenly even'); end; otherwise writeln('odd'); end; { case } end. -------------------------------------------------------------------- To work around this, I had to change nested case statements into programs that used only if-then-else. Another problem I had was a segmentation fault on F_Flush(Output) after defining procedure F_Flush(var aFile); asmname '_p_f_flush'; as recommended in your documentation. I didn't have time to pursue this to figure out what was failing, because it was easier for me just to say procedure Flushstdout; external; and then load the C routine void Flushstdout(){fflush(stdout)} with the compiled object code. With these two changes, I successfully got the TANGLE program to reproduce itself, so the first major hurdle towards generating retro-TeX has been passed! If I run into any more bugs, I'll let you know --- the TRIP and TRAP tests of TeX and METAFONT are pretty good test suites. But let's be optimistic and suppose that everything else works. Then I won't have to write you again. In any case when the new GNU-Pascal-based port of TeX is ready I will post the sources to the CTAN archives; they will be at labrea.stanford.edu in directory ~ftp/pub/tex/local. Best wishes on your important project! -- Don Knuth

2 1

RE: faq version 4
by Mason Ip 21 Apr '00

21 Apr '00

Russ Whitaker wrote: [snip] > 1.4 Which platforms are supported by GNU Pascal? > ================================================ > > GPC uses the GCC backend, so it should run on any system that is > supported by GNU CC. This includes a large variety of Unix systems, > MS-DOS, OS/2 and Win32. A full list of platforms supported by GCC can > be found in the file `INSTALL' of the GCC distribution. Not all of > these have actually been tested, but it is known to run on these > platforms: > > ix86-linux (Linux 2.x, ELF) > i486-linuxaout > i486-linuxoldld > i386-freebsd1.2.0 > djgpp V2 (msdos) > emx 0.9B (OS/2, msdos) > cygwin32 beta20 and higher ( Windows95, Windows NT) > Mingw32 (Windows95/98, Windows NT) > mips-sgi-irix5.3 > sun-sparc-sunos4.1.4 > > >>> Ok people - send us your success stories, with canonical machine > name! <<< > I used gpc on sun-sparc-solaris 2.5.1 before it was upgraded to 2.6, and 7. I'm sure a lot of people are running gpc on these later Solaris versions too. So, you may add to the list : sun-sparc-solaris 2.5.1 sun-sparc-solaris 2.6 sun-sparc-solaris 7 I'm still waiting for Solaris 8 to arrive. Someone may confirm that gpc will work on that too.

1 0

faq version 4
by Russ Whitaker 21 Apr '00

21 Apr '00

Hi OK, I think I got it now Let me know if anything wrong Thanks, Russ <russwhit(a)mind.net> ---------------------------------------------------------------------------- GNU Pascal Frequently-Asked Questions List, Edition 0.6, April 2000 by Russ Whitaker <russwhit(a)mind.net> based on GNU Pascal Frequently-Asked Questions List, Edition 0.4, for GPC version 2.0, November 1996 by J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> For up-to-date information, ask the GPC mailing list (see below). Index ***** 1.0 GNU Pascal - what, where and why 2.0 Installation 3.0 After the installation 4.0 Pascal on the djgpp platform 5.0 (reserved) 6.0 Getting Help 7.0 Miscellaneous 1.0 GNU Pascal *************** 1.1 What and why? ================= The purpose of the GNU Pascal project is to produce a Pascal compiler (called GNU Pascal or GPC) which * combines the clarity of Pascal with powerful tools suitable for real-life programming, * supports both the Pascal standard and the Extended Pascal standard as defined by ISO, ANSI and IEEE. (ISO 7185:1990, ISO/IEC 10206:1991, ANSI/IEEE 770X3.160-1989) * supports other Pascal standards (UCSD Pascal, Borland Pascal, Pascal-SC) in so far as this serves the goal of clarity and usability, * may be distributed under GNU license conditions * can generate code and run on any computer for which the GNU C compiler can generate code and run. Pascal was originally designed for teaching. GNU Pascal provides a smooth way to proceed to challenging programming tasks without learning a completely different language. 1.2 What is the current version? ================================ The latest release as of this writing is GPC-19991030. GPC requires GCC as a back-end. Patches for GCC 2.8.1 thru GCC 2.95.2 are provided but it is recommended that you use at least GCC 2.95. 1.3 Is it compatible with Turbo Pascal (R) ? ============================================ GPC is *not* a drop-in replacement for Borland's Turbo Pascal (R). Almost all BP language features are supported. Notable exceptions are the string format (as discussed below), or the 'Mem' and 'Port' pseudo arrays, though replacement functions for the latter on x86 platforms exist in the 'Ports' unit. Also, almost all of BP's run time library is supported in GPC (built-in or in units with the same names as their BP counterparts). Some notes: - A BP compatible graph unit exists but is distributed separately due to its license. - The OOP stuff (Turbo Vision etc.) is not yet completed, but work on several projects is underway. - Some exotic routines need an explicit `uses System' statement, or equivalently a `--uses=system' command line option. See the system unit for details. - A few unportable routines in the Dos unit are only supported under DJGPP if '__BP_UNPORTABLE_ROUTINES__' is defined (i.e., when com- piling with "-D__BP_UNPORTABLE_ROUTINES__'). ---Frank 1.4 Which platforms are supported by GNU Pascal? ================================================ GPC uses the GCC backend, so it should run on any system that is supported by GNU CC. This includes a large variety of Unix systems, MS-DOS, OS/2 and Win32. A full list of platforms supported by GCC can be found in the file `INSTALL' of the GCC distribution. Not all of these have actually been tested, but it is known to run on these platforms: ix86-linux (Linux 2.x, ELF) i486-linuxaout i486-linuxoldld i386-freebsd1.2.0 djgpp V2 (msdos) emx 0.9B (OS/2, msdos) cygwin32 beta20 and higher ( Windows95, Windows NT) Mingw32 (Windows95/98, Windows NT) mips-sgi-irix5.3 sun-sparc-sunos4.1.4 >>> Ok people - send us your success stories, with canonical machine name! <<< 2.0 Installation ***************** 2.1 How do I get and install GPC on my computer? ================================================ 1. The easiest way is is from a distribution - if you can find it. All the dependency files should be there, also. The downside is if the GPC release date is prior to Oct. 1999 you shuld plan on doing an update. 2. The recommended way is to build it yourself from the source listings. If you have everything you need to compile a kernel except the kernel source then all you need is the GPC source and a GCC source. The down- side is if you have a slow computer the build could take several hours. You can get the GPC source from ftp://agnes.dida.physik.uni-essen.de/ You can get the GCC source from http://gcc.gnu.org 3. You may not want to install a new distribution just to get GPC and the build project on a 386 can take several hours as well as some 50M of hard drive space. Then try one of the several pre-compiled binaries available. The downside is you need one that is compatible with your computer and C libruary. GNU Pascal Compiler binaries for Sun Solaris 7 (Sparc/x86) operating environment in native Solaris packages form are available at: Sparc: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/sparc http://math.uwb.edu.pl/download/solaris7/sparc x86: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/x86 http://math.uwb.edu.pl/download/solaris7/x86 For installation instructions read Readme.txt file on that site. GPC 19991030 was compiled based on GCC 2.95. Binaries for Solaris 8 (Sparc and Intel) are now available on: http://math.uwb.edu.pl/download/solaris8/ ftp://mizar.uwb.edu.pl/pub/misc/solaris8/ -- Mariusz Zynel Also, on Feb 9th, 2000 the following binaries were found in a FTP directory at agnes.dida.physik.uni-essen.de: Directory: /gnu-pascal/alpha/binary/ gpc-19990607-djgp.zip Directory: /gnu-pascal/beta/binary/ gpc-19990118-1.i386-pc-linux-gnu.rpm gpc-19990118-egcs-1.1.1.i386-linux-glibc2.tar.gz gpc-19990118-egcs-1.1.1.i386-pc-mingw32.zip gpc-19990118-egcs-1.1.1.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.alpha-unknown-linux-gnu.tar.gz gpc-19990118.alphaev56-dec-osf4.0d.tar.gz gpc-19990118.i386-pc-djgppv201.zip gpc-19990118.i386-pc-emx0.9d.zip gpc-19990118.i386-pc-mingw32.zip gpc-19990118.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.mips-sgi-irix6.2.tar.gz gpc-19990118.sparc-sun-solaris2.6.tar.gz gpc-19990430-i386-pc-djgppv202.zip gpc-extras-19990118-1.i386-pc-linux-gnu.rpm 2.2 How do I build a GPC compiler? ================================== CAUTION: There have been extensive changes in GCC from 2.8 to 2.95. The old GPC build instructions, for GCC-2.8 and earlier, will not work on GCC-2.95 and up. If you have a typical ix86 box the routine is fairly simple. Any other computer you should carefully read the documentation in GCC*/install. Assuming you have: 1. A working C compiler. 2. The usual tools: ar, awk, bash, bison, ld, make, patch, sed 3. The GPC and GCC tar.gz source in directory /usr/local/src Then here's a cookbook recipe: 1. Unpack the two sources: tar -xvzf gcc-2.95.2.tar.gz tar -xvzf gpc-19991030.tar.gz 2. Since GCC recommends building gcc in a separate directory, lets make one: we'll call it gcc-build. mkdir gcc-build 3. Now we need to move GPC into GCC: mv gpc/p gcc-2.95.2/gcc 4. Next is a patch to gcc: cd gcc-2.95.2/gcc patch -s -p1 < p/diffs/gcc-2.95.2.diff 5. Now GCC is ready to build several languages, including pascal. If you want to know what languages, grep language= */config-lang.in will give you a list. 6. So let's go do it: cd ../../gcc-build ../gcc-2.95.2/configure --enable-languages=pascal make bootstrap-lean With --enable-languages=pascal you get both GCC and GPC. The GCC won't interfere with your default compiler because it is installed in a different place. Without the --enable-languages option you get ALL the languages GCC can build. Bootstrap-lean is recommended instead of bootstrap because it removes files that are no longer needed. That "make bootstrap-lean" will take some time. If you want to know how much, you could date > /time1 ; make bootstrap-lean ; date > /time2 On my 400mhz i586 with 128m ram, no swap, it took 24 min 34 sec. 7. If all went well you can now install it: make install That's it. You can find some interesting demos in /usr/local/doc/gpc/demos and you can find the units directory with gpc --print-file-name=units after installation. If this doesn't give the correct directory (or just says 'units'), your installation is not quite right right yet. 3.0 After the Installation ************************** 3.1 What to do first? ===================== Stop right now and go read the file BUGS in directory /usr/local/doc/gpc While you're at it, you should take a look at the other files in that directory: README General Information about GPC AUTHORS List of GPC authors NEWS Changes since the last beta version COPYING GNU General Public License COPYING.LIB GNU Library Public License Another good article on submitting bug reports can be found at either: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html or: http://freshmeat.net/news/2000/02/26/951627540.html 3.2 What additional libraries should I have? ============================================ You will need certain additional libraries when you compile the units. These can be found in the directory ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs What follows is the contents of the README file found there: In this directory, you can find the libraries used by some of GPC's units. Currently, there are the following libraries: - gmp: Arithmetic for integers, rationals and real numbers with arbitrary size and precision. Used by the GMP unit. - rx: Regular expression matching and substitution. Used by the RegEx unit. - ncurses, PDCurses: Screen handling. Used by the CRT unit. Depending on your system, you have the following choices: Unix: You can compile terminal applications with ncurses and applications that run in an X11 window with PDCurses (though terminal applications can, of course, also run in an xterm under X11). ncurses is used by default. If you want to use PDCurses (a.k.a. XCurses), give the option `-DX11' when compiling CRT. Dos with DJGPP and MS-Windows with mingw: Only PDCurses is available and will be used by default. MS-Windows with Cygwin: PDCurses and ncurses are available. PDCurses is used by default. If you want to use ncurses, give the option `-DUSE_NCURSES' when compiling CRT. Other systems: Please see the `README's and installation instructions of PDCurses and ncurses to find out which one(s) can be built on your system. See the conditionals at the end of crt.inc and crtc.h (and change them if necessary) on which library is used by default. The source code of the libraries is available in this directory. Most libraries come with one or several patches which should be applied before compiling them. Binaries for some platforms are available in the `binary/<platform>' subdirectories. If you compile the libraries for other platforms, be invited to make the binaries available to us for distribution on this FTP site. There are also the following files: - terminfo-linux.tar.gz This is a patch to enable ncurses programs to make use of the ability of Linux 2.2 and newer kernels to produce a block cursor when needed. The present patch can be installed without recompiling anything, just by copying some files into place. More details can be found in the `README' file included in this archive. The patch will not do any harm on older kernels. Please note that *not* only on Linux machines it is useful to install the patch. Installing them on any other machine will allow users who telnet in from a Linux console to profit from the block cursor capability. Besides, some Unix systems have installed older Linux terminfo entries or none at all, so it's a good thing, anyway, to give them a current version. The patch is included in the terminfo database of ncurses 5.0, so if you install ncurses 5.0 (source or binary), you don't need to get the patch separately. But you can install it on a system with an older ncurses version if you don't feel like upgrading ncurses altogether. - tsort-2.9i.zip A little utility (extracted from util-linux-2.9i, but not Linux specific), needed for the configuration of the rx library. You need it only if you compile rx yourself (and if it's not already present on your system), not when using a rx binary. In addition to the above libraries there is a unit which you can use to interface Svgalib. As of this writing the current release is SvgaLib-GPC-20000216.tar.gz and you can get it from ftp://agnes.dida.physik.uni-essen.de/~nicola 3.3 Which components do I need to compile Pascal source code? ============================================================== A complete Pascal compiler system should at least have: 1. The actual compiler, GPC. While there are some binaries available you can build GPC yourself. You need a working C compiler, some tools: bash, ar, patch, make, the GCC source, and the GPC source. 2. An editor, Assembler, linker, librarian and friends. 3. A C library. If you have a working C compiler you already have this. 4. A debugger, if you want to debug your programs. For most people, the GNU binutils and GNU debugger (gdb) are a good choice, although some may prefer to use vendor specific tools. 3.4 How do I debug my Pascal programs? ======================================= To debug your programs, (a) GNU Pascal must be able to generate executables with debug info for your platform, and (b) you must have a debugger which understands this. * If `gpc -g -o hello hello.p' says: `gpc: -g not supported for this platform', then GPC is unable to generate debug info. Usually, installing GAS instead of your system's assembler can overcome this. When you configure the GCC used for GPC, specify `-with-gnu-as', and possibly `-with-gnu-ld' and/or `-with-stabs'. More information can be found in `INSTALL' file in the GNU CC source directory. * Your system's debugger may not understand the debug info generated by GNU tools. In this case, installing GDB may help. The bottom line: if you can debug GCC compiled programs, you should be able to do this with GPC too. The GNU debugger (GDB) currently does not have a "Pascal" mode, so it is unable to display certain Pascal structures etc. When debugging, please note that the Initial Letter In Each Identifier Is In Upper Case And The Rest Are In Lower Case. If you want to display variable `foo' in the debugger, type `show Foo' or `display Foo' instead. 3.5 Can you recommend an IDE? ============================== Users of Borland Pascal may wonder if there's a replacement for the IDE (Integrated Development Environment). Here's a few suggestions: * (X)Emacs. Some people think it's the answer to the question of Life, the Universe and Everything, others decide it's uGNUsable. Available from your friendly GNU mirror and most distributions. * XWPE is an imitation of the Borland IDE, so users of Borland Pascal may find it a good alternative. * RHIDE. djgpp users should definitely try RHIDE. The latest (beta) release is compatible with GNU Pascal and allows stepping, tracing and watching like Borland's IDE. RHIDE v0.6 beta can be downloaded from: http://www.tu-chemnitz.de/~sho/rho/rhide/rhide.html * PENG. It's not free software, but it was written with GPC. It's very similar to Borland's IDE, but with many extensions: http://fjf.gnu.de/peng.html 3.6 Debugger? ============== Although GDB is an excellent debugger, it's user interface is not very attractive. Refer to the comp.windows.x FAQ: "Where can I get an X-based debugger?" at: http:// www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.html Some useful frontends include: XXGDB, tGDB and XWPE. see: http://www.ee.ryerson.ca:8080/~elf/xapps/Q-IV.html Very nice, but resource consuming is the Motif based DDD: http://sol.ibr.cs.tu-bs.de/softech/ddd/ 4.0 GNU Pascal on the djgpp (MS-DOS) platform ********************************************* This chapter discusses some potential problems with GNU Pascal on MS-DOS, using djgpp. If you need more information ============================ GPC/djgpp is a djgpp V2 application, and most of the djgpp documentation applies for GPC too. A great source of information is the djgpp FAQ: http://www.delorie.com/djgpp/v2faq/faq202b.zip Another place to look for DJGPP documentation is the DJGPP Knowledge Base, at this URL: http://www.delorie.com/djgpp/doc/kb/ What do I download? =================== As discussed in section 2.2, other than GPC itself, you need an assembler, linker and friends, a C library and possibly a debugger. >From your local djgpp mirror, you can get these as: v2/djdev201.zip (C library) v2gnu/bnu270b.zip (assembler, ....) v2gnu/gdb416b.zip (debugger) The rest is up to you; `make' (v2gnu/mak375b.zip) can be useful, The latest RHIDE test release (an IDE with Borland-look) has support for GNU Pascal, and can be downloaded from: http://www.tu-chemnitz.de/~rho/rhidetest.html How do I install the compiler? ============================== If you don't have djgpp installed on your harddisk, create a directory for GNU pascal (`c:\gpc'), and unzip the archives. Make sure you preserve the directory structure (use `pkunzip -d'). Now, add the directory where `gpc.exe' lives (`c:\gpc\bin') to your path and set the DJGPP environment variable to point to your `djgpp.env' file: set DJGPP=c:\gpc\djgpp.env Then, add this to your `djgpp.env' file: --------------------------------------------------------- [gpcpp] C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/lang/pascal; %DJDIR%/include;%DJDIR%/contrib/grx20/include ( note: one line; but split here to fit page ) [gpc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib;%DJDIR%/contrib/grx20/lib --------------------------------------------------------- The binary distribution should come with a `djgpp.env' which is already modified, so you may not have to do this. The GPC online documentation is in GNU info format; you need the info reader (`txi390b.zip') to read it. To add the GPC documentation to the info directory file, edit the `c:\gpc\info\dir' file, and locate this section: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- To add GPC, change it to look like this: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GPC: (gpc.inf). The GNU Pascal Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- Specific information for low-memory conditions and more can be found in the djgpp FAQ and documentation. I cannot read the info pages! ============================= To read the info pages, you need the `info' program from `txi390b.zip'. GPC says: no DPMI ================= You don't have a DPMI server installed, and DJGPP v2 requires it to run. You can either use one of the commercial DPMI servers (e.g., run `gpc' in a DOS box under Windows) or download and install CWSDPMI (`csdpmi3b.zip') which is a free DPMI server written for DJGPP. I have troubles with assembly code ================================== The GNU Assembler (`as.exe'), or `gas', called by GCC accepts "AT&T" syntax which is different from "Intel" syntax. Differences are discussed in section 17.1 of the djgpp FAQ. A guide is available which was written by Brennan Mr. Wacko Underwood <brennan(a)mack.rt66.com> and describes how to use inline assembly programming with DJGPP, at this URL: http://www.rt66.com/~brennan/djgpp/djgpp_asm.html There's also a GPC assembler tutorial at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpcasm.zip Section 17.3 of the djgpp FAQ discusses some methods to convert "Intel" syntax to "AT&T". Tell me how to do DPMI, BIOS and other DOS related things. ========================================================== DPMI, BIOS and other functions are no different than other system functions. Refer to section 3.1 how to access your system's C-library. This small example shows how to use DPMI, copying some structures and function prototypes of `<dpmi.h>': --------------------------------------------------------- program dpmitest; {$X+} {`Byte' and `Word' are built-in, and `ShortInt' is 'short' in C.} type PDpmiVersionRet = ^TDpmiVersionRet; TDpmiVersionRet = record major : byte; minor : byte; flags : shortint; cpu : byte; master_pic : byte; slave_pic : byte; end; type PDpmiFreeMemInfo = ^TDpmiFreeMemInfo; TDpmiFreeMemInfo = record largest_available_free_block_in_bytes : word; maximum_unlocked_page_allocation_in_pages : word; maximum_locked_page_allocation_in_pages : word; linear_address_space_size_in_pages : word; total_number_of_unlocked_pages : word; total_number_of_free_pages : word; total_number_of_physical_pages : word; free_linear_address_space_in_pages : word; size_of_paging_file_partition_in_pages : word; reserved1 : byte; reserved2 : byte; reserved3 : byte; end; function DpmiGetVersion(ret: PDpmiVersionRet): integer; asmname '__dpmi_get_version'; function DpmiGetFreeMemoryInformation(info: PDpmiFreeMemInfo): integer; asmname '__dpmi_get_free_memory_information'; var version: TDpmiVersionRet; meminfo: TDpmiFreeMemInfo; begin DpmiGetVersion(@version); writeln('CPU type : ', version.cpu, '86'); writeln('DPMI major : ', version.major); writeln('DPMI minor : ', version.minor); DpmiGetFreeMemoryInformation(@meminfo); writeln('Free DPMI memory : ', meminfo.total_number_of_free_pages, ' pages.'); end. --------------------------------------------------------- I'm accessing an `array[1..4000000] of byte' and I got an exception. ==================================================================== Per default, the maximum stack size of a djgpp application is 256K. If you need more, you have to adjust it with the stubedit program, i.e.: stubedit your_app.exe minstack=5000K Still, it might be a good idea to use pointers for this kind of structures, and allocate the memory at runtime. 5.0 (reserved) *************** 6.0 STRINGS *********** What's this confusion about strings? ==================================== Turbo Pascal strings have a length byte in front. Since a byte has the range 0 - 255, this limits a string to 255 characters. However, the Pascal string schema, as defined in section 6.4.3.3.3 of the ISO-10206: 1990 Extended Pascal standard, is a schema record: type String (Capacity : integer) = record Length : 0 .. Capacity; String : packed array [1 .. Capacity + 1] of Char end; The `+ 1' is a GPC extension to make it feasible to automatically add the #0 terminator when passing or assigning them to CStrings. Thus at the expense of a little added complexity ( must declare capacity, don't use GetMem, and the additional space requiremnent ) you can now have very long strings. The following Q&A is also about strings: ======================================== Q: Should the different variants in a variant record overlay in the same memory? Previous Pascals I have used have guaranteed this, and I've got low-level code that relies on this. The variants are not the same length, and they are intended not to be. A: No, this is intentional so that the discriminants are not overwritten, and they can be properly initialized in the first place. Consider: record case Boolean of False: (s1 : String (42)); True: (s2 : String (99)); end; If the strings would overlay, in particular their discriminants would occupy the same place in memory. How should it be initialized? Either way, it would be wrong for at least one of the variants... So, after a discussion in comp.lang.pascal.ansi-iso where this topic came up concerning file variables (which also require some automatic initialization and finalization), we decided to do this in GPC for all types with automatic initialization and finalization (currently files and schemata, in the future this might also be Delphi compatible classes and user-defined initialized and finalized types), since the standard does not guarantee variants to overlay, anyway... There are two ways in GPC to get guaranteed overlaying (both non-standard, of course, since the standard does not assume anything about internal representations; both BP compatible), `absolute' declarations and variable type casts. E.g., in order to overlay a byte array to a variable v: var b: array [1 .. SizeOf (v)] of Byte absolute v; or type t = array [1 .. SizeOf (v)] of Byte; then `t (v)' can be used as a byte array overlayed to v. Q: In standard pascal you expect ic[1] to align with the first character position of s and thus one character to the left is the length of s. Thus ic[0] is the length of s. True? A: This holds for UCSD/BP strings (which GPC does not yet implement, but that's planned). The only strings Standard Pascal knows are arrays of char without any length value. Q: Two different kinds of strings with the same name - string - does make a bit of confusion. Perhaps the oldstyle strings could be renamed "short string" ? A: When we implement the short strings, we'll have to do such a distinction. Our current planning goes like this: string (n): string schema (EP compatible) string [n]: short string (UCSD/BP compatible, where n must be <= 255) string: dependent on flags, by default undiscriminated schema, but in BP mode (or with a special switch) short string of capacity 255 (UCSD/BP compatible). ---- Frank Q: So when will these short strings be available? A: It's been planned for over a year. The delay has been caused by more pressing problems. What about C strings? ===================== A C string (`char *') is an array of char, terminated with a `NULL' char. C library functions require C, not Pascal style string arguments. However, Pascal style strings are automatically converted to C style strings when passed to a routine that expects C style strings. This works only if the routine reads from the string, not if it modifies it. E.g., this is how you access the `system()' call in your C library (which is not necessary any more, since `Execute' is already built-in): --------------------------------------------------------- program SysCall; function system(name : CString): integer; C; var result : integer; begin result := system ('ls -l'); writeln('system() call returned : ', result); end. --------------------------------------------------------- There may be other ways to do the same thing; you could use a type `PChar' instead of `CString' and replace all references to `CString' with `PChar'. `PChar' is predefined now (though we recommend `CString' because it makes it clearer that we're talking about some kind of string rather than a single character), and a lot of library routines in Pascal for many applications (in the GPC unit and some other units) have been written (see above)... type PChar = ^char; Do *NOT* pass a "C" style string as a var-argument if the C prototype says `const char *' or you will get a coredump. 6.0 Getting Help **************** If you have never submitted a bug report before there's a good HOWTO article on Freshmeat. The URL is <http://freshmeat.net/news/2000/02/26/951627540.html> Please read the documentation (info files, readme's) that come with GPC, plus other docs that might help (the djgpp FAQ if you use djgpp, etc.) before you send email to the maintainers or mailing list. Help! The compiler crashed! =========================== If the compiler crashes, you have discovered a bug. A reliable compiler never crashes. To help the maintainers fix this bug, it is important that you send us a problem report. I think I found a bug - now what? ================================= Bugs are best reported to the GPC mailinglist <gpc(a)gnu.de>. That way, they always reach the maintainers. Try to give as much information as possible, plus a short code snippet that triggers the compiler bug. If you're on Unix, you can find out where the compiler crashed if you enable coredumps, then load the compiler (`gpc1') plus the core file in the debugger (`gdb /your_path_here/gpc1 core'), then type `backtrace' to get a stacktrace. Include this stacktrace in your bug report. Which newsgroup(s) are suited for GPC related problems? ======================================================= There are several Pascal related newsgroups, but none is dedicated just to GNU Pascal. This one may be useful: comp.lang.pascal.misc Pascal in general and ungrouped Pascals. Pascal syntax related questions may be appropriate in: comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO standards. The next newsgroup is a haven for beginers, answering questions that would apply to almost any pascal. However, if you have a GPC-specific question don't post there - use the GPC mailing list. And if in doubt use the GPC mailing list. comp.lang.pascal.borland Borland Pascal questions. Also, the mailing list archives are a good place to look. The URL is http://www.gnu.de/archive/wilma.cgi/gpc and http://www.gnu.de/archive/wilma.cgi/gpc-announce respectively. Now the pages also come in gpc signature colors. :-) Note: Currently, the search option is working fine. If you find it broken, please email me at <anja(a)drewitz.de>. Please don't mail a copy to the gpc list because I let procmail move all mails with To: gpc... and Cc: gpc... to a separate folder and would not see your mail for a long time. --- Anja How to post to the mailing list =============================== You can send a message to the GPC mailing list by sending email to the list address <gpc(a)gnu.de> as if it were a person. How to become a subscriber to the mailing list ============================================== You can join the mailing list by sending a message to <gpc-request(a)gnu.de> (NOT <gpc(a)gnu.de> !) with your request to be added to the list. How to unsubscribe from the mailing list ======================================== To leave the mailing list, send a message to <gpc-request(a)gnu.de>. 7.0 Miscellaneous ***************** I want to contribute; where do I start? ======================================= If you want to contribute, please write to the mailing list. Where is the GNU Pascal FTP site? WWW? ====================================== The master FTP site for GNU Pascal is `agnes.dida.physic.uni-essen.de'. GNU Pascal related files can be found in: http://agnes.dida.physik.uni-essen.de/~gnu-pascal ftp://agnes.dida.physik.uni-esssen.de/gnu-pascal This site is mirrored on: ftp://sunsite.doc.ic.ac.uk/gnu/pascal/ The latest developer releases can be downloaded from: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html Also, we have a homepage on the web: http://home.pages.de/~GNU-Pascal/ ---Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ For now, this same page appears at http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ About this FAQ. =============== Original Maintainer: J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> Current Maintainer: Russ Whitaker <russwhit(a)mind.net> This is the second incarnation of the GNU Pascal FAQ list. Comments about, suggestions for, or corrections to this FAQ list are welcome. Please make sure to include in your mail the version number of the document to which your comments apply (you can find the version at the beginning of this FAQ list). Many people have contributed to this FAQ, only some of them are acknowledged above. Much of the info in, and inspiration for this FAQ list was taken from the gpc mailing list traffic, so you may have (unbeknownst to you) contributed to this list.

1 0

unsubscribe
by Michael Monsour 20 Apr '00

20 Apr '00

unsubscribe ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup

1 0

Re: dpr suffix, now -x pascal
by Mariusz Zynel 19 Apr '00

19 Apr '00

Peter Gerwinski wrote: > > > > GPC does not automatically recognize the suffix `.dpr' for Pascal. > > No, you have to give GPC the `-x pascal' option. I tried it. Doesn't work for me. Here goes the output I've got: math% gpc -o tst -x pascal tst.dpr gpc: Internal GPC problem: internal option `--amtmpfile' not given math% gpc --delphi -o tst -x pascal tst.dpr gpc: Internal GPC problem: internal option `--amtmpfile' not given math% gpc -v Reading specs from /usr/local/lib/gcc-lib/i386-pc-solaris2.7/2.95/specs gpc version 19991030, based on 2.95 19990728 (release) Regards -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

2 2

About GCP developement
by Václav Haisman 19 Apr '00

19 Apr '00

Hi there, I have one question, Is GPC still being developed or did the developement stop? Vaclav Haisman Vaclav Haisman V.Haisman(a)sh.cvut.cz http://web.sh.cvut.cz/wilx/

3 2

Re: dpr suffix
by Frank Heckenbach 19 Apr '00

19 Apr '00

Dr A Olowofoyeku wrote: > On 18 Apr 2000, at 16:19, Peter Gerwinski wrote: > > > Mariusz Zynel wrote: > > > $ gpc -s --borland-pascal -DGPC -DSOLARIS --unit-path=../obj -o accom > > > accom.dpr > > > > $ gpc -s --delphi -DGPC -DSOLARIS --unit-path=../obj -o accom -x pascal > > accom.dpr > > > > GPC does not automatically recognize the suffix `.dpr' for Pascal. > [...] > > Any plans to support this (perhaps in Delphi mode)? OK, it will be in the next release (in any mode, don't think this should cause problems) as well as `.pp'. Hmm, perhaps we should invent 3 or 4 extensions of our own, seems like every Pascal compiler has to use different extensions... ;-) > Frank: Delphi supports 'AssignFile' and 'CloseFile' (as synonyms for > 'Assign' and 'Close'). Can we support these (again perhaps in Delphi > mode)? They are already there (in the GPC unit). 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

4 4

Re: Autoconf + Pascal projects
by Frank Heckenbach 19 Apr '00

19 Apr '00

Mariusz Zynel wrote: > > Hi All > > Is there anybody interested in automated dependency - Make rules > generation for Pascal projects? Yes. I'm currently(*) writing a utility to do this. Not as make rules because make is not completely suitable for Pascal projects (e.g., since in a unit, the interface and implementation parts are stored in the same file, make would have to assume the interface was changed when in fact only the implementation was changed, and therefore recompile everything that uses the unit; also, it's not well suited for cyclic unit dependencies). (*) Actually, my work got stuck because of a problem and other things to do. But I hope I can continue it soon... > or using Autoconf for Pascal projects? For feature tests, we try to avoid it, or rather, concentrate it in the RTS, so the RTS already provides a portable interface and not every project has to do the (mostly) same tests again and again. > BTW options -M as well as -MM and the like seem not to work with > GPC. They work... like they do in GCC, i.e., output the include dependencies which are, of course, not very important in most Pascal projects. 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

1 0

Autoconf + Pascal projects
by Mariusz Zynel 19 Apr '00

19 Apr '00

Hi All Is there anybody interested in automated dependency - Make rules generation for Pascal projects? or using Autoconf for Pascal projects? BTW options -M as well as -MM and the like seem not to work with GPC. Regards -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

1 0

Re: dpr suffix
by Frank Heckenbach 18 Apr '00

18 Apr '00

Mariusz Zynel wrote: > Peter Gerwinski wrote: > > > > Mariusz Zynel wrote: > > > > No, you have to give GPC the `-x pascal' option. > > > I could not find that in man page. What does it mean? > > > > It means: "Forget about the suffix; this file _is_ Pascal source." > > > > Yes, of course... man gcc. It's also in the GPC info documentation (under `Invoking GPC'). 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

1 0

Re: dpr suffix
by Mariusz Zynel 18 Apr '00

18 Apr '00

Peter Gerwinski wrote: > > Mariusz Zynel wrote: > > > No, you have to give GPC the `-x pascal' option. > > I could not find that in man page. What does it mean? > > It means: "Forget about the suffix; this file _is_ Pascal source." > Yes, of course... man gcc. Thanks -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

1 0

Re: dpr suffix
by Mariusz Zynel 18 Apr '00

18 Apr '00

Peter Gerwinski wrote: > > > > GPC does not automatically recognize the suffix `.dpr' for Pascal. > > > > So, I have to stay with copying to .pas than copying back to .dpr. > > No, you have to give GPC the `-x pascal' option. I could not find that in man page. What does it mean? > > > We use Delphi to build our system, but we use also Free Pascal and > > of course GPC. So we do not use Delphi extensions at all, we do not > > even use classes, but old-BP-fashioned objects. > > Then it should work. > > > > Better do not use all those `--foo-pascal' switches. They are > > > just for switching _off_ GPC extensions. > > > > Without that swicht I have problems with building our system. The > > code is simply BP code with changes forced by mentioned compilers, > > usually compiled conditionally. > > > > Do those --foo-pascal switches do more than switching off GPC > > extensions? > > Not really: They switch off warnings about some BP braindamage > and some reserved identifiers not present in BP, and they switch > on warnings about GPC extensions. > > > Are they safe? > > Yes, of course. In which sense are you afraid of them being > unsafe? They are only affecting warning behaviour. I was not sure what exactly those switches do. I see they are safe. Thank you Peter -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

1 0

dpr suffix
by Mariusz Zynel 18 Apr '00

18 Apr '00

Hi All When I try to compile a program which source has suffix .dpr I get an eror message from linker: $ gpc -s --borland-pascal -DGPC -DSOLARIS --unit-path=../obj -o accom accom.dpr ld: elf error: file accom.dpr: unknown type, unable to process using elf(3E) libraries ld: fatal: File processing errors. No output written to accom collect2: ld returned 1 exit status Even if I exchange --borland-pascal for --object-pascal which seems to be Delphi compatibility mode, the story repeats. Is it GPC problem? Any ideas? ...besides changing filenames. I'm using GPC dated 19991030 build on GCC 2.95.2 on Solaris 8 x86. Thanks in advance for responses -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

3 2

unsubscribe
by Manuel Gomes 18 Apr '00

18 Apr '00

------------------------------------------ Manuel Gomes VARIOGRAMA www.variograma.com mg(a)variograma.com icq: 9741968 ------------------------------------------ NEW ADDRESS: Largo do Corpo Santo, 6 - 1 1200-129 Lisboa PORTUGAL NEW PHONES: +351 21 3241090 - Phone +351 21 3241098 - VoiceMail +351 21 3241099 - FAX

1 0

Re: gpc missing program header
by Frank Heckenbach 14 Apr '00

14 Apr '00

Chris Karow wrote: > I am trying to use the compiler on an 32 bit SGI, v6.5 > operating system. I downloaded the binaries for both > the gcc (fw_gcc-2_8_1-sgipl2.tardist) and gpc > (gpc-19990118.mips-sgi-irix6.2.tar.gz). I installed > both, gcc in /usr/freeware and gpc in /usr/local. > I've run gcc and tested it and it works fine. When I > test gpc, I get a long message starting with This looks like the compiler is working, and complains about some problems in the code begin compiled. Apparently, the code was written for another Pascal compiler (SGI Pascal???) which predefines some non-standard identifiers. I can give you a few tips how to define them in GPC. Some of the errors are probably consequences of the missing identifiers. > "tabutil.pas:25: warning: missing program header According to the standard, a program requires a `program' line at the beginning. If it's missing, GPC will warn, but still compile the program. > tabutil.pas:30: type name expected, identifier > `String80' given > tabutil.pas:31: type name expected, identifier > `String20' given > tabutil.pas: In function `Readint': > tabutil.pas:60: type name expected, identifier > `String255' given type String80 = String (80); String20 = String (20); String255 = String (255); > tabutil.pas:68: undeclared identifier `Depend_err' > (first use this function) I don't know what this is (haven't seen this anywhere before). Perhaps it's define in some module which is supposed to be compiled with the given source (via `imports' or as an include file, ...). Otherwise, you'd have to figure out what this procedure(?) is supposed to do... > tabutil.pas:69: undeclared identifier `Str2int' (first > use this function) > tabutil.pas:86: undeclared identifier `Str2real' > (first use this function) GPC supports: ReadStr ( <source string>, <integer, real, string, char>... ) and Val ( <source string>, <integer or real>, <result> ) (result will be 0 if successful, >0 if not) Based on this, you can write Str2Int and Str2Real as needed by your code. Since this depends on whether they are supposed to be procedures or functions and on their parameter lists, I can't give you drop-in routines, but perhaps something like the following: function Str2Int (const s: String) = Res: Integer; begin ReadStr (s, Res) end; (However, it looks like your code has a `ReadStr' routine itself, so either do the above before the (re-)declaration of `ReadStr' or use `Val'.) > tabutil.pas:102: undeclared identifier `Strg' (first > use this function) I don't know what this means. On German keyboards, `Strg' is the `Ctrl' key, but I doubt that's meant here. ;-) It could be Str(ing)G(reater) or anything else, but I really don't know without seeing some context (or documentation of the original compiler). > tabutil.pas:128: undeclared identifier `Fopen' (first > use this function) Looks like the name of a C funcion (fopen()). If that's really what's meant here, you can probably use the normal file routines (`Reset', `Rewrite', `Extend')... > tabutil.pas:136: undeclared identifier `Indx' (first > use this function) GPC supports `Index' (find a substring in a string), in case that's what `Indx' is supposed to be... If these things are really built-in declarations of some Pascal compiler (and not part of some other modules), we could try to add them to GPC. We have done this for other dialects or other compilers' definitions (in particular, Borland Pascal), so it wouldn't be completely new to us. However, we'd need some reasonable documentation on this compiler's declarations (or better yet, free code to implement them :-). 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

1 0

gpc missing program header
by Chris Karow 14 Apr '00

14 Apr '00

Hi, I am new to this mailing list but I have done a lot of upfront work before writing for help. I am new to compilers but have to install GPC compiler for a user. I have read the Install and Readme for gpc and gcc. I have also gone through all of 12/99 mailing list archive and I still need help. I am trying to use the compiler on an 32 bit SGI, v6.5 operating system. I downloaded the binaries for both the gcc (fw_gcc-2_8_1-sgipl2.tardist) and gpc (gpc-19990118.mips-sgi-irix6.2.tar.gz). I installed both, gcc in /usr/freeware and gpc in /usr/local. I've run gcc and tested it and it works fine. When I test gpc, I get a long message starting with "tabutil.pas:25: warning: missing program header tabutil.pas:30: type name expected, identifier `String80' given tabutil.pas:31: type name expected, identifier `String20' given tabutil.pas: In function `Readint': tabutil.pas:60: type name expected, identifier `String255' given tabutil.pas:63: only Pascal string type, array of char, and char type tabutil.pas:63: are assignment compatible with a string tabutil.pas:68: undeclared identifier `Depend_err' (first use this function) tabutil.pas:68: (Each undeclared identifier is reported only once tabutil.pas:68: for each function it appears in.) tabutil.pas:69: undeclared identifier `Str2int' (first use this function) tabutil.pas: In function `Readreal': tabutil.pas:76: type name expected, identifier `String255' given tabutil.pas:80: only Pascal string type, array of char, and char type tabutil.pas:80: are assignment compatible with a string tabutil.pas:85: undeclared identifier `Depend_err' (first use this function) tabutil.pas:86: undeclared identifier `Str2real' (first use this function) tabutil.pas: In function `Readstr': tabutil.pas:102: undeclared identifier `Strg' (first use this function) tabutil.pas: At top level: tabutil.pas:120: type name expected, identifier `String255' given tabutil.pas: In function `Readmatrix': tabutil.pas:126: type name expected, identifier `String255' given tabutil.pas:128: undeclared identifier `Fopen' (first use this function) tabutil.pas:131: argument to `length' must be of string or char type tabutil.pas:131: only Pascal string type, array of char, and char type tabutil.pas:131: are assignment compatible with a string tabutil.pas:132: subscripted object is not an array or string tabutil.pas:134: argument to `length' must be of string or char type tabutil.pas:134: only Pascal string type, array of char, and char type tabutil.pas:134: are assignment compatible with a string tabutil.pas:136: undeclared identifier `Indx' (first use this function) tabutil.pas:145: incompatible type for argument 2 of `Readstr' tabutil.pas:145: too many arguments to function `Readstr' tabutil.pas:146: incompatible type for argument 2 of `Readstr' tabutil.pas:146: too many arguments to function `Readstr' tabutil.pas:147: incompatible type for argument 2 of `Readstr' tabutil.pas:147: too many arguments to function `Readstr' tabutil.pas: In function `Scalematrix': tabutil.pas:195: subscripted object is not an array or string tabutil.pas:196: undeclared identifier `Indx' (first use this function) tabutil.pas: In function `program_noname': tabutil.pas:212: parse error before `End' When this didn't work, I unpacked the source in /usr/local/src for both gcc (gcc-2_8_1_tar.gz) and gpc (gpc-19990118.tar.gz. I moved the p dir. from gpc to gcc dir. and ran the patch and ran configure. I then ran make LANGUAGES=pascal and received errors like missing cfe so copied into /usr/lib/cfe. Also, received errors for the inttypes.h, staarg.h and cccp.c and corrected paths. Gave up on this and removed both gcc and gpc source dir. and reinstalled the gpc and gcc binaries. Tested gcc OK. Same error mess. for gpc. If I run gpc -v, the output is gpc vers.19990118, based on gcc 2.8.1. If I run gcc -v, the output is reading specs from /usr/freeware/lib/gcc-lib/mips-sgi-irix6.2/2.8.1/specs gcc version 2.8.1. I think I have compatible gpc and gcc vers. When I run gpc -verbose, I get "Using builtin specs. gpc version 19990118, based on gcc-2.8.1 ld -call_shared -no_unresolved -init __do_global_ctors -fini __do_global_dtors -_SYSTYPE_SVR4 -n32 /usr/lib32/mips3/crt1.o crtbegin.o -L/usr/local/lib/gcc-lib/mips-sgi-irix6.2/2.8.1 -L/usr/local/lib/gcc-lib/mips-sgi-irix6.2/2.8.1 -L/usr/local/lib -lgpc -lm -dont_warn_unused -lgcc -warn_unused -L/usr/lib32/mips3 -L/usr/lib32 -dont_warn_unused -lc -warn_unused -dont_warn_unused -lgcc -warn_unused crtend.o /usr/lib32/mips3/crtn.o ld32: FATAL 9: I/O error (crtbegin.o): No such file or directory" I had found this file under /usr/freeware/lib/gcc-lib/mips-sgi-irix6.2/2.8.1 and had worked with this path as well but to no avail. Any help would be appreciated! Chris ===== __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com

1 0

None
by Chris Karow 14 Apr '00

14 Apr '00

index gpc compiler ===== __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com

1 0

None
by Chris Karow 14 Apr '00

14 Apr '00

info gpc compiler ===== __________________________________________________ Do You Yahoo!? Send online invitations with Yahoo! Invites. http://invites.yahoo.com

1 0

Re: Linux installation of gpc19991030 with 2.95.2
by Frank Heckenbach 14 Apr '00

14 Apr '00

=?iso-8859-1?Q?Klaus_Friis_=D8stergaard?= wrote: > To be able to acces the gpc compiler I have symlinked > > ln -s /usr/local/bin/gpc /usr/bin/gpc Isn't /usr/local/bin in your PATH? > but when I compile a pascal program with a unit, like crt the compiler > places alot of .o and .gpi files in the directory that I compile from, can > this be redirected so that it will come in the ..../units where the crt.pas > gpc.pas and all the other units are. --unit-destination-path=DIR 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

1 0

Linux installation of gpc19991030 with 2.95.2
by Klaus Friis Østergaard 14 Apr '00

14 Apr '00

Hi I have a redhat 6.0 installation with the standard egcs compiler, I have followed the instalation instruction and compiled the gcc 2.95.2 src along with the gpc19991030 and succed. The instruction sugest to use /usr/local/ for installation. I dont know if it is commen, but when configureing the compiler I need to specify configure --enable-languages=pascal "i386-pc-linux" I actually have a i686 pc is it because that I use the egcs compiler wich says it is compiled under "i386" that it would not accept "i686-pc-linux" To be able to acces the gpc compiler I have symlinked ln -s /usr/local/bin/gpc /usr/bin/gpc but when I compile a pascal program with a unit, like crt the compiler places alot of .o and .gpi files in the directory that I compile from, can this be redirected so that it will come in the ..../units where the crt.pas gpc.pas and all the other units are. Has any body succed in compiling the grx23 graphics lib with the 2.95.2 compiler so it can be used with the gpc19991030 ? klaus

1 0

under linux installation
by Nathalie Jarosz 14 Apr '00

14 Apr '00

Hi! I am new in using Linux and I'd like to install gnu pascal. I start with following the instructions but I felt at the step 2 of the install file. I've tried %./configure or ../gcc-2.8.1/configure but nothing happens... More exactely, a message appears but I don't remember the text at the moment. Either I forgot to do something or I need to download another file because I've just downloaded gpc-19990118.tar.gz, gcc-2.8.1.tar.gz and gcc-2.8.0-2.8.1.diff.gz? Maybe someone could help me, Thanks a lot in advance, Nathalie ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com

3 3

Re: under linux installation
by Frank Heckenbach 13 Apr '00

13 Apr '00

Khimenko Victor forwarded the message by Simon Tatham: > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html is the > definitive location. (This isn't quite the same as the Freshmeat > version, but the differences aren't important.) That's fine. So I think we should mention this URL prominently in the FAQ. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: under linux installation
by Frank Heckenbach 13 Apr '00

13 Apr '00

Khimenko Victor wrote: > P.S. To Frank & Peter: may be we should put BIG message with link to > http://freshmeat.net/news/2000/02/26/951627540.html > somewhere in FAQ ? > It's REALLY must be read by anyone who ask for help... I think it's a good idea to mention it prominently in the FAQ. Is this URL likely to remain permanently? I've written some of his points into test/README. This file will be installed as BUGS in the binary distributions in the doc directory (e.g. /usr/local/doc/gpc/) where also the FAQ will be installed. Russ, you might want to point to the BUGS file in the FAQ. BTW, the other files installed in that directory will be README (general information about GPC), AUTHORS (list of GPC authors), NEWS (changes since the last beta) and COPYING and COPYING.LIB (GNU GPL and LGPL). 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

3 2

re: case sensitive defines
by Russ Whitaker 11 Apr '00

11 Apr '00

Suggestion: define (all lower case letters) case insensitive Define (One or more upper case) case sensitive Thanks russ <russwhit(a)mind.net>

2 1

Re: faq-version 3
by Frank Heckenbach 11 Apr '00

11 Apr '00

Russ Whitaker wrote: > Frank Heckenbach wrote: > > > > > I'm wondering if we should suggest c.l.p.b at all. Is anyone > > monitoring it for GPC related questions regularly? (I'm not reading > > it anymore because of the high noise/signal ratio...) > > > Read the postings today. Looks like the faq should be changed to > > " comp.lang.pascal.borland ( It's mostly a haven for beginers )" > > Most of the questions would apply to any pascal and the answers came fairly > quickly. Probably. But I'm a bit worried, if we recommend the newsgroup in the FAQ and people send their GPC specific problems (like installation problems) there and no-one's reading it, that's not good (for the users and for the reputation of GPC). Therefore my question if anyone is reading it regularly and looking for GPC related questions... 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

1 0

Re: faq-version 3
by Russ Whitaker 11 Apr '00

11 Apr '00

Frank Heckenbach wrote: > > I'm wondering if we should suggest c.l.p.b at all. Is anyone > monitoring it for GPC related questions regularly? (I'm not reading > it anymore because of the high noise/signal ratio...) > Read the postings today. Looks like the faq should be changed to " comp.lang.pascal.borland ( It's mostly a haven for beginers )" Most of the questions would apply to any pascal and the answers came fairly quickly. Thanks Russ <russwhit(a)mind.net>

1 0

Re: Case-insensitive defines
by Frank Heckenbach 11 Apr '00

11 Apr '00

Maurice Lombardi wrote: > What about command line defines, as > > gpc -DPostScript ... > > would it be case sensitive ? I would prefer no, but is there any problem ? Oh right. I forgot to mention them, it's good you did... Well, I think the implicit defines (`__GPC__', `__FOO_PASCAL__', `DJGPP', etc.) should remain case-sensitive. For user-supplied options, we have the choice. Again, I see reasons to have case-sensitive ones, too. E.g., I have some programs which work alternatively with GMP (multi-presicion) or normal numbers, and I use `-DGMP' to select the GMP version. Since the unit is also called `GMP', it would conflict if it's case-insensitive (whereas now I can write `uses Gmp' to avoid a conflict). So, we could allow both on the command-line as well, we'd just need different option names. The problem is that `--define' in GCC is equivalent to `-D' and case-sensitive, and I think we shouldn't change this to keep interoperability with GCC as good as it is now. But we could add a new option for case-insensitive defines. J. David Bryan wrote: > > OTOH, something like {$define-case-sensitive} would make it clear, but > > it's very long. > > {$define-cs} would be OK (better than {$definecs} only because the "cs" > part stands out better with the hyphen). I'd vote against the hyphen because it's an acronym that follows. BTW, since the directive itself is case-insensitive, you could write it as {$DefineCS} to make it clearer... Dr A Olowofoyeku wrote: > On 7 Apr 00, at 0:53, Peter Gerwinski wrote: > > > Dr A Olowofoyeku wrote: > > > > > > Why not use {$define} for case insensitive and #define for case > > > sensitive ? Since case-sensitivity is a C thing, we might as well keep > > > #define (which is also a C thing) for that purpose. Advantage? It > > > avoids the introduction of new constructs. > > > > I see the advantages. But in fact we want to get rid of > > unpascalish things such as #define and promote alternatives > > like {$define}. > > I see. In this case I vote for {$csdefine} ('Case Sensitive Define') > or {$cdefine}. With the above consideration about the command line, I suggest perhaps `csdefine' and `cidefine' for case-sensitive/-insensitive defines. Both would work on the command-line and as compiler directives. Besides, `define' as a directive is case-insensitive (because of BP) and `--define' on the command line is case-sensitive (because of GCC). Or the same with `definecs', `defineci'. 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

4 4

Re: case sensitive defines
by Frank Heckenbach 10 Apr '00

10 Apr '00

Dr A Olowofoyeku wrote: > On 10 Apr 00, at 10:57, Frank Heckenbach wrote: > > [...] > > If there are no objections, I'm implementing: > > > > Case insensitive: > > > > {$define} > > {$cidefine} > > --cidefine > > > > Case sensitive: > > > > {$csdefine} > > -D > > --define > > --csdefine > > Seems as good as any other permutation. Probably. :-/ But at least once one has learned what ci/cs means, one can remember those ones without looking them up... And users of other Pascal compilers or of GCC will not encounter unpleasant surprises... 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

1 0

faq-version 3
by Russ Whitaker 10 Apr '00

10 Apr '00

At long last here's vers 3 of the proposed FAQ If you think it looks good will start making a HTML version russ <russwhit(a)mind.net> ======================================================= GNU Pascal Frequently-Asked Questions List, Edition 0.5, February 2000 by Russ Whitaker <russwhit(a)mind.net> based on GNU Pascal Frequently-Asked Questions List, Edition 0.4, for GPC version 2.0, November 1996 by J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> For up-to-date information, ask the GPC mailing list (see below). Index ***** 1.0 GNU Pascal - what, where and why 2.0 Installation 3.0 After the installation 4.0 Pascal on the djgpp platform 5.0 (reserved) 6.0 Getting Help 7.0 Miscellaneous 1.0 GNU Pascal *************** 1.1 What and why? ================= The purpose of the GNU Pascal project is to produce a Pascal compiler (called GNU Pascal or GPC) which * combines the clarity of Pascal with powerful tools suitable for real-life programming, * supports both the Pascal standard and the Extended Pascal standard as defined by ISO, ANSI and IEEE. (ISO 7185:1990, ISO/IEC 10206:1991, ANSI/IEEE 770X3.160-1989) * supports other Pascal standards (UCSD Pascal, Borland Pascal, Pascal-SC) in so far as this serves the goal of clarity and usability, * may be distributed under GNU license conditions * can generate code and run on any computer for which the GNU C compiler can generate code and run. Pascal was originally designed for teaching. GNU Pascal provides a smooth way to proceed to challenging programming tasks without learning a completely different language. 1.2 What is the current version? ================================ The latest release as of this writing is GPC-19991030. GPC requires GCC as a back-end. Patches for GCC 2.8.1 thru GCC 2.95.2 are provided but it is recommended that you use at least GCC 2.95. 1.3 Is it compatible with Turbo Pascal (R) ? ============================================ GPC is *not* a drop-in replacement for Borland's Turbo Pascal (R). Almost all BP language features are supported. Notable exceptions are the string format (as discussed below), or the 'Mem' and 'Port' pseudo arrays, though replacemnet functions for the latter on x86 platforms exist in the 'Ports' unit. Also, almost all of BP's run time library is supported in GPC (built-in or in units with the same names as their BP counterparts). Some notes: - A BP compatable graph unit exists but is distributed saparately due to its license. - The OOP stuff (Turbo Vision etc.) is not yet completed, but work on several projects is underway. - Some exotic routines need an explicit `uses System' statement, or equivalently a `--uses=system' command line option. See the system unit for details. - A few unportable routines are not supported in the Dos unit (see the comments there). I think there's an older, unportable, Dos unit which supports them (or else it's easy to write one) if you really need those routines... ---Frank (minor edited) 1.4 Which platforms are supported by GNU Pascal? ================================================ GPC uses the GCC backend, so it should run on any system that is supported by GNU CC. This includes a large variety of Unix systems, MS-DOS, OS/2 and Win32. A full list of platforms supported by GCC can be found in the file `INSTALL' of the GCC distribution. Not all of these have actually been tested, but it is known to run on these platforms: ix86-linux (Linux 2.x, ELF) i486-linuxaout i486-linuxoldld i386-freebsd1.2.0 djgpp V2 (msdos) emx 0.9B (OS/2, msdos) cygwin32 beta16 (Windows95, Windows NT) mips-sgi-irix5.3 sun-sparc-sunos4.1.4 >>> Ok people - send us your success stories, with canonical machine name! <<< 2.0 Installation ***************** 2.1 How do I get and install GPC on my computer? ================================================ 1. The easiest way is is from a distrubution - if you can find it. All the dependency files should be there, also. The downside is if the GPC release date is proir to Oct. 1999 you shuld plan on doing an update. 2. The recommended way is to build it yourself from the source listings. If you have everything you need to compile a kernal except the kernal source then all you need is the GPC source and a GCC source. The down- side is if you have a slow computer the build could take several hours. You can get the GPC source from ftp://agnes.dida.physik.uni-essen.de/ You can get the GCC source from http://gcc.gnu.org 3. You may not want to install a new distribution just to get GPC and the build project on a 386 can take several hours as well as some 50M of hard drive space. Then try one of the several pre-compiled binaries available. The downside is you need one that is compatable with your computer and C libruary. GNU Pascal Compiler binaries for Sun Solaris 7 (Sparc/x86) operating environment in native Solaris packages form are available at: Sparc: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/sparc http://math.uwb.edu.pl/download/solaris7/sparc x86: ftp://mizar.uwb.edu.pl/pub/misc/solaris7/x86 http://math.uwb.edu.pl/download/solaris7/x86 For installation instructions read Readme.txt file on that site. GPC 19991030 was compiled based on GCC 2.95. Binaries for Solaris 8 (Sparc and Intel) are now available on: http://math.uwb.edu.pl/download/solaris8/ ftp://mizar.uwb.edu.pl/pub/misc/solaris8/ -- Mariusz Zynel Also, on Feb 9th, 2000 the following binaries were found in a FTP directory at agnes.dida.physik.uni-essen.de: Directory: /gnu-pascal/alpha/binary/ gpc-19990607-djgp.zip Directory: /gnu-pascal/beta/binary/ gpc-19990118-1.i386-pc-linux-gnu.rpm gpc-19990118-egcs-1.1.1.i386-linux-glibc2.tar.gz gpc-19990118-egcs-1.1.1.i386-pc-mingw32.zip gpc-19990118-egcs-1.1.1.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.alpha-unknown-linux-gnu.tar.gz gpc-19990118.alphaev56-dec-osf4.0d.tar.gz gpc-19990118.i386-pc-djgppv201.zip gpc-19990118.i386-pc-emx0.9d.zip gpc-19990118.i386-pc-mingw32.zip gpc-19990118.i586-pc-linux-gnulibc1.tar.gz gpc-19990118.mips-sgi-irix6.2.tar.gz gpc-19990118.sparc-sun-solaris2.6.tar.gz gpc-19990430-i386-pc-djgppv202.zip gpc-extras-19990118-1.i386-pc-linux-gnu.rpm 2.2 How do I build a GPC compiler? ================================== CAUTION: There have been extensive changes in GCC from 2.8 to 2.95. The old GPC build instructions, for GCC-2.8 and earlier, will not work. If you have a typical ix86 box the routine is fairly simple. Any other computer you should carefully read the documentation in GCC*/install. Assuming you have: 1. A working C compiler. 2. The usual tools: ar, awk, bash, bison, ld, make, patch, sed 3. The GPC and GCC tar.gz source in directory /usr/local/src Then here's a cookbook recipe: 1. Unpack the two sources: tar -xvzf gcc-2.95.2.tar.gz tar -xvzf gpc-19991030.tar.gz 2. Since GCC recommends building gcc in a separate directory, lets make one: we'll call it gcc-build. mkdir gcc-build 3. Now we need to move GPC into GCC: mv gpc/p gcc-2.95.2/gcc 4. Next is a patch to gcc: cd gcc-2.95.2/gcc patch -s -p1 < p/diffs/gcc-2.95.2.diff 5. Now GCC is ready to build several languages, including pascal. If you want to know what languages, grep language= */config-lang.in will give you a list. 6. So let's go do it: cd ../../gcc-build ../gcc-2.95.2/configure --enable-languages=pascal make bootstrap-lean With --enable-languages=pascal you get both GCC and GPC. The GCC won't interfere with your default compiler because it is installed in a different place. Without the --enable-languages option you get ALL the languages GCC can build. Bootstrap-lean is recomended instead of bootstrap because it removes files that are no longer needed. That "make bootstrap-lean" will take some time. If you want to know how much, you could date > /time1 ; make bootstrap-lean ; date > /time2 On my 400mhz i586 with 128m ram, no swap, it took 24 min 34 sec. 7. If all went well you can now install it: make install That's it. You can find some interesting demos in /usr/local/doc/gpc/demos and you can find the units directory with find /usr/local/lib -name units 3.0 After the Installation ************************** 3.1 What additional libraries should I have? ============================================ You will need certain additional libraries when you compile the units. These can be found in the directory ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/libs What follows is the contents of the README file found there: In this directory, you can find the libraries used by some of GPC's units. Currently, there are the following libraries: - gmp: Arithmetic for integers, rationals and real numbers with arbitrary size and precision. Used by the GMP unit. - rx: Regular expression matching and substitution. Used by the RegEx unit. - ncurses, PDCurses: Screen handling. Used by the CRT unit. Depending on your system, you have the following choices: Unix: You can compile terminal applications with ncurses and applications that run in an X11 window with PDCurses (though terminal applications can, of course, also run in an xterm under X11). ncurses is used by default. If you want to use PDCurses (a.k.a. XCurses), give the option `-DX11' when compiling CRT. Dos with DJGPP and MS-Windows with mingw: Only PDCurses is available and will be used by default. MS-Windows with Cygwin: PDCurses and ncurses are available. PDCurses is used by default. If you want to use ncurses, give the option `-DUSE_NCURSES' when compiling CRT. Other systems: Please see the `README's and installation instructions of PDCurses and ncurses to find out which one(s) can be built on your system. See the conditionals at the end of crt.inc and crtc.h (and change them if necessary) on which library is used by default. The source code of the libraries is available in this directory. Most libraries come with one or several patches which should be applied before compiling them. Binaries for some platforms are available in the `binary/<platform>' subdirectories. If you compile the libraries for other platforms, be invited to make the binaries available to us for distribution on this FTP site. There are also the following files: - terminfo-linux.tar.gz This is a patch to enable ncurses programs to make use of the ability of Linux 2.2 and newer kernels to produce a block cursor when needed. The present patch can be installed without recompiling anything, just by copying some files into place. More details can be found in the `README' file included in this archive. The patch will not do any harm on older kernels. Please note that *not* only on Linux machines it is useful to install the patch. Installing them on any other machine will allow users who telnet in from a Linux console to profit from the block cursor capability. Besides, some Unix systems have installed older Linux terminfo entries or none at all, so it's a good thing, anyway, to give them a current version. The patch is included in the terminfo database of ncurses 5.0, so if you install ncurses 5.0 (source or binary), you don't need to get the patch separately. But you can install it on a system with an older ncurses version if you don't feel like upgrading ncurses altogether. - tsort-2.9i.zip A little utility (extracted from util-linux-2.9i, but not Linux specific), needed for the configuration of the rx library. You need it only if you compile rx yourself (and if it's not already present on your system), not when using a rx binary. In addition to the above libraries there is a unit which you can use to interface Svalib. As of this writing the current release is SvgaLib-GPC-20000216.tar.gz and you can get it from ftp://agnes.dida.physik.uni-essen.de/~nicola 3.2 Which components do I need to compile Pascal source code? ============================================================== A complete Pascal compiler system should at least have: 1. The actual compiler, GPC. While there are some binaries available you can build GPC yourself. You nee a working C compiler, some tools: bash, ar, patch, make, the GCC source, and the GPC source. 2. An editor, Assembler, linker, librarian and friends. 3. A C library. If you have a working C compiler you already have this. 4. A debugger, if you want to debug your programs. For most people, the GNU binutils and GNU debugger (gdb) are a good choice, although some may prefer to use vendor specific tools. 3.3 How do I debug my Pascal programs? ======================================= To debug your programs, (a) GNU Pascal must be able to generate executables with debug info for your platform, and (b) you must have a debugger which understands this. * If `gpc -g -o hello hello.p' says: `gpc: -g not supported for this platform', then GPC is unable to generate debug info. Usually, installing GAS instead of your system's assembler can overcome this. When you configure the GCC used for GPC, specify `-with-gnu-as', and possibly `-with-gnu-ld' and/or `-with-stabs'. More information can be found in `INSTALL' file in the GNU CC source directory. * Your system's debugger may not understand the debug info generated by GNU tools. In this case, installing GDB may help. The bottom line: if you can debug GCC compiled programs, you should be able to do this with GPC too. The GNU debugger (GDB) currently does not have a "Pascal" mode, so it is unable to display certain Pascal structures etc. When debugging, please note that the Initial Letter In Each Identifier Is In Upper Case And The Rest Are In Lower Case. If you want to display variable `foo' in the debugger, type `show Foo' or `display Foo' instead. 3.4 Can you recommend an IDE? ============================== Users of Borland Pascal may wonder if there's a replacement for the IDE (Integrated Development Environment). Here's a few suggestions: * (X)Emacs. Some people think it's the answer to the question of Life, the Universe and Everything, others decide it's uGNUsable. Available from your friendly GNU mirror and most distributions. * XWPE is an imitation of the Borland IDE, so users of Borland Pascal may find it a good alternative. * RHIDE. djgpp users should definately try RHIDE. The latest (beta) release is compatible with GNU Pascal and allows stepping, tracing and watching like Borland's IDE. RHIDE v0.6 beta can be downloaded from: http://www.tu-chemnitz.de/~sho/rho/rhide/rhide.html * PENG. It's not free software, but it was written with GPC. It's very similar to Borland's IDE, but with many extensions: http://fjf.gnu.de/peng.html 3.6 Debugger? ============== Although GDB is an excellent debugger, it's user interface is not very attractive. Refer to the comp.windows.x FAQ: "Where can I get an X-based debugger?" at: http:// www.cis.ohio-state.edu/hypertext/faq/usenet/x-faq/part6/faq-doc-2.html Some useful frontends include: XXGDB, tGDB and XWPE. see: http://www.ee.ryerson.ca:8080/~elf/xapps/Q-IV.html Very nice, but resource consuming is the Motif based DDD: http://sol.ibr.cs.tu-bs.de/softech/ddd/ 4.0 GNU Pascal on the djgpp (MS-DOS) platform ********************************************* This chapter discusses some potential problems with GNU Pascal on MS-DOS, using djgpp. If you need more information ============================ GPC/djgpp is a djgpp V2 application, and most of the djgpp documentation applies for GPC too. A great source of information is the djgpp FAQ: http://www.delorie.com/djgpp/v2faq/faq202b.zip Another place to look for DJGPP documentation is the DJGPP Knowledge Base, at this URL: http://www.delorie.com/djgpp/doc/kb/ What do I download? =================== As discussed in section 2.2, other than GPC itself, you need an assembler, linker and friends, a C library and possibly a debugger. >From your local djgpp mirror, you can get these as: v2/djdev201.zip (C library) v2gnu/bnu270b.zip (assembler, ....) v2gnu/gdb416b.zip (debugger) The rest is up to you; `make' (v2gnu/mak375b.zip) can be useful, The latest RHIDE test release (an IDE with Borland-look) has support for GNU Pascal, and can be downloaded from: http://www.tu-chemnitz.de/~rho/rhidetest.html How do I install the compiler? ============================== If you don't have djgpp installed on your harddisk, create a directory for GNU pascal (`c:\gpc'), and unzip the archives. Make sure you preserve the directory structure (use `pkunzip -d'). Now, add the directory where `gpc.exe' lives (`c:\gpc\bin') to your path and set the DJGPP environment variable to point to your `djgpp.env' file: set DJGPP=c:\gpc\djgpp.env Then, add this to your `djgpp.env' file: --------------------------------------------------------- [gpc-cpp] C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/lang/pascal;%DJDIR%/include;%DJDIR %/contrib/grx20/include [gpc] COMPILER_PATH=%/>;COMPILER_PATH%%DJDIR%/bin LIBRARY_PATH=%/>;LIBRARY_PATH%%DJDIR%/lib;%DJDIR%/contrib/grx20/lib --------------------------------------------------------- The binary distribution should come with a `djgpp.env' which is already modified, so you may not have to do this. The GPC online documentation is in GNU info format; you need the info reader (`txi390b.zip') to read it. To add the GPC documentation to the info directory file, edit the `c:\gpc\info\dir' file, and locate this section: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- To add GPC, change it to look like this: --------------------------------------------------------- * GCC: (gcc.inf). The GNU C, C++, and Objective-C Compiler * GPC: (gpc.inf). The GNU Pascal Compiler * GDB: (gdb.inf). The GNU Debugger (gdb and gdb-dpmi). --------------------------------------------------------- Specific information for low-memory conditions and more can be found in the djgpp FAQ and documentation. I cannot read the info pages! ============================= To read the info pages, you need the `info' program from `txi390b.zip'. GPC says: no DPMI ================= You don't have a DPMI server installed, and DJGPP v2 requires it to run. You can either use one of the commercial DPMI servers (e.g., run `gpc' in a DOS box under Windows) or download and install CWSDPMI (`csdpmi3b.zip') which is a free DPMI server written for DJGPP. I have troubles with assembly code ================================== The GNU Assembler (`as.exe'), or `gas', called by GCC accepts "AT&T" syntax which is different from "Intel" syntax. Differences are discussed in section 17.1 of the djgpp FAQ. A guide is available which was written by Brennan Mr. Wacko Underwood <brennan(a)mack.rt66.com> and describes how to use inline assembly programming with DJGPP, at this URL: http://www.rt66.com/~brennan/djgpp/djgpp_asm.html There's also a GPC assembler tutorial at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpcasm.zip Section 17.3 of the djgpp FAQ discusses some methods to convert "Intel" syntax to "AT&T". Tell me how to do DPMI, BIOS and other DOS related things. ========================================================== DPMI, BIOS and other functions are no different than other system functions. Refer to section 3.1 how to access your system's C-library. This small example shows how to use DPMI, copying some structures and function prototypes of `<dpmi.h>': --------------------------------------------------------- program dpmitest; {$X+} {`Byte' and `Word' are built-in, and `ShortInt' is 'short' in C.} type PDpmiVersionRet = ^TDpmiVersionRet; TDpmiVersionRet = record major : byte; minor : byte; flags : short; cpu : byte; master_pic : byte; slave_pic : byte; end; type PDpmiFreeMemInfo = ^TDpmiFreeMemInfo; TDpmiFreeMemInfo = record largest_available_free_block_in_bytes : word; maximum_unlocked_page_allocation_in_pages : word; maximum_locked_page_allocation_in_pages : word; linear_address_space_size_in_pages : word; total_number_of_unlocked_pages : word; total_number_of_free_pages : word; total_number_of_physical_pages : word; free_linear_address_space_in_pages : word; size_of_paging_file_partition_in_pages : word; reserved1 : byte; reserved2 : byte; reserved3 : byte; end; function DpmiGetVersion(ret: PDpmiVersionRet): integer; asmname '__dpmi_get_version'; function DpmiGetFreeMemoryInformation(info: PDpmiFreeMemInfo): integer; asmname '__dpmi_get_free_memory_information'; var version: TDpmiVersionRet; meminfo: TDpmiFreeMemInfo; begin DpmiGetVersion(@version); writeln('CPU type : ', version.cpu, '86'); writeln('DPMI major : ', version.major); writeln('DPMI minor : ', version.minor); DpmiGetFreeMemoryInformation(@meminfo); writeln('Free DPMI memory : ', meminfo.total_number_of_free_pages, ' pages.'); end. --------------------------------------------------------- I'm accessing an `array[1..4000000] of byte' and I got an exception. ==================================================================== Per default, the maximum stack size of a djgpp application is 256K. If you need more, you have to adjust it with the stubedit program, i.e.: stubedit your_app.exe minstack=5000K Still, it might be a good idea to use pointers for this kind of structures, and allocate the memory at runtime. 5.0 (reserved) *************** 6.0 STRINGS *********** What's this confusion about strings? ==================================== Turbo Pascal strings have a length byte in front. Since a byte has the range 0 - 255, this limits a string to 255 characters. However, the Pascal string schema, as defined in section 6.4.3.3.3 of the ISO-10206: 1990 Extended Pascal standard, is a schema record: type String (Capacity : integer) = record Length : 0 .. Capacity; String : packed array [1 .. Capacity + 1] of Char end; The `+ 1' is a GPC extension to make it feasible to automatically add the #0 terminator when passing or assigning them to CStrings. Thus at the expense of a little added complexity ( must declare capacity, don't use GetMem, and the additional space requiremnent ) you can now have very long strings. The following Q&A is also about strings: ======================================== Q: Should the different variants in a variant record overlay in the same memory? Previous Pascals I have used have guaranteed this, and I've got low-level code that relies on this. The variants are not the same length, and they are intended not to be. A: No, this is intentional so that the discriminants are not overwritten, and they can be properly initialized in the first place. Consider: record case Boolean of False: (s1 : String (42)); True: (s2 : String (99)); end; If the strings would overlay, in particular their disriminants would occupy the same place in memory. How should it be initialized? Either way, it would be wrong for at least one of the variants... So, after a discussion in comp.lang.pascal.ansi-iso where this topic came up concerning file variables (which also require some automatic initialization and finalization), we decided to do this in GPC for all types with automatic initialization and finalization (currently files and schemata, in the future this might also be Delphi compatible classes and user-defined initialized and finalized types), since the standard does not guarantee variants to overlay, anyway... There are two ways in GPC to get guaranteed overlaying (both non-standard, of course, since the standard does not assume anything about internal representations; both BP compatible), `absolute' declarations and variable type casts. E.g., in order to overlay a byte array to a variable v: var b: array [1 .. SizeOf (v)] of Byte absolute v; or type t = array [1 .. SizeOf (v)] of Byte; then `t (v)' can be used as a byte array overlayed to v. Q: In standard pascal you expect ic[1] to align with the first character position of s and thus one character to the left is the length of s. Thus ic[0] is the length of s. True? A: This holds for UCSD/BP strings (which GPC does not yet implement, but that's planned). The only strings Standard Pascal knows are arrays of char without any length value. Q: Two different kinds of strings with the same name - string - does make a bit of confusion. Perhaps the oldstyle strings could be renamed "short string" ? A: When we implement the short strings, we'll have to do such a distinction. Our current planning goes like this: string (n): string schema (EP compatible) string [n]: short string (UCSD/BP compatible, where n must be <= 255) string: dependent on flags, by default undiscriminated schema, but in BP mode (or with a special switch) short string of capacity 255 (UCSD/BP compatible). ---- Frank Q: So when will these short strings be available? A: It's been planned for over a year. The delay has been caused by more pressing problems. What about C strings? ===================== A C string (`char *') is an array of char, terminated with a `NULL' char. C library functions require C, not Pascal style string arguments. However, Pascal style strings are automatically converted to C style strings when passed to a routine that expects C style strings. This works only if the routine reads from the string, not if it modifies it. E.g., this is how you access the `system()' call in your C library (which is not necessary any more, since `Execute' is already built-in): --------------------------------------------------------- program SysCall; function system(name : CString): integer; C; var result : integer; begin result := system ('ls -l'); writeln('system() call returned : ', result); end. --------------------------------------------------------- There may be other ways to do the same thing; you could use a type `PChar' instead of `CString' and replace all references to `CString' with `PChar'. `PChar' is predefined now (though we recommend `CString' because it makes it clearer that we're talking about some kind of string rather than a single character), and a lot of library routines in Pascal for many applications (in the GPC unit and some other units) have been written (see above)... type PChar = ^char; Do *NOT* pass a "C" style string as a var-argument if the C prototype says `const char *' or you will get a coredump. 6.0 Getting Help **************** This section discusses ways to get help with GNU Pascal. Please read the documentation (info files, readme's) that come with GPC, plus other docs that might help (the djgpp FAQ if you use djgpp etc.) before you send email to the maintainers or mailing list. Help! The compiler crashed! =========================== If the compiler crashes, you have discovered a bug. A reliable compiler never crashes. To help the maintainers fix this bug, it is important that you send us a problem report. I think I found a bug - now what? ================================= Bugs are best reported to the GPC mailinglist <gpc(a)gnu.de>. That way, they always reach the maintainers. Try to give as much information as possible, plus a short code snippet that triggers the compiler bug. If you're on Unix, you can find out where the compiler crashed if you enable coredumps, then load the compiler (`gpc1') plus the core file in the debugger (`gdb /your_path_here/gpc1 core'), then type `backtrace' to get a stacktrace. Include this stacktrace in your bug report. Which newsgroup(s) are suited for GPC related problems? ======================================================= There are several Pascal related newsgroups, but none is dedicated just to GNU Pascal. This one may be useful: comp.lang.pascal.misc Pascal in general and ungrouped Pascals. Pascal syntax related questions may be appropriate in: comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO standards. comp.lang.pascal.borland Borland Pascal questions. Also, the mailing list archives are a good place to look. The URL is http://www.gnu.de/archive/wilma.cgi/gpc and http://www.gnu.de/archive/wilma.cgi/gpc-announce respectively. Now the pages also come in gpc signature colors. :-) Note: Currently, the search option is working fine. If you find it broken, please email me at <anja(a)drewitz.de>. Please don't mail a copy to the gpc list because I let procmail move all mails with To: gpc... and Cc: gpc... to a separate folder and would not see your mail for a long time. --- Anja How to post to the mailing list =============================== You can send a message to the GPC mailing list by sending email to the list address <gpc(a)gnu.de> as if it were a person. How to become a subscriber to the mailing list ============================================== You can join the mailing list by sending a message to <gpc-request(a)gnu.de> (NOT <gpc(a)gnu.de> !) with your request to be added to the list. How to unsubscribe from the mailing list ======================================== To leave the mailing list, send a message to <gpc-request(a)gnu.de>. 7.0 Miscellaneous ***************** I want to contribute; where do I start? ======================================= If you want to contribute, please write to the mailing list. Where is the GNU Pascal FTP site? WWW? ====================================== The master FTP site for GNU Pascal is `agnes.dida.physic.uni-essen.de'. GNU Pascal related files can be found in: http://agnes.dida.physik.uni-essen.de/~gnu-pascal ftp://agnes.dida.physik.uni-esssen.de/gnu-pascal This site is mirrored on: ftp://sunsite.doc.ic.ac.uk/gnu/pascal/ The latest developer releases can be downloaded from: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html Also, we have a homepage on the web: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ Or shorter: http://home.pages.de/~GNU-Pascal/ ---Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ About this FAQ. =============== Original Maintainer: J.J. van der Heijden <j.j.vanderheijden(a)student.utwente.nl> Current Maintainer: Russ Whitaker <russwhit(a)mind.net> This is the second incarnation of the GNU Pascal FAQ list. Comments about, suggestions for, or corrections to this FAQ list are welcome. Please make sure to include in your mail the version number of the document to which your comments apply (you can find the version at the beginning of this FAQ list). Many people have contributed to this FAQ, only some of them are acknowledged above. Much of the info in, and inspiration for this FAQ list was taken from the gpc mailing list traffic, so you may have (unbeknownst to you) contributed to this list.

3 3

Re: case sensitive defines
by Frank Heckenbach 10 Apr '00

10 Apr '00

Russ Whitaker wrote: > Suggestion: > > define (all lower case letters) case insensitive > > Define (One or more upper case) case sensitive I don't like this very much, I'm afraid. The other GPC directives are case-insensitive, so I think `$define' should also be. (Besides, it wouldn't be BP compatible...) If there are no objections, I'm implementing: Case insensitive: {$define} {$cidefine} --cidefine Case sensitive: {$csdefine} -D --define --csdefine 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: faq-version 3
by Frank Heckenbach 10 Apr '00

10 Apr '00

Russ Whitaker wrote: > At long last here's vers 3 of the proposed FAQ A few more typos: compatable -> compatible proir -> prior kernal -> kernel nee -> need > and you can find the units directory with > find /usr/local/lib -name units Better: and you can find the units directory with gpc --print-file-name=units after installation. If this doesn't give the correct directory (or just says `units'), your installation is not quite right yet. > flags : short; This should be ShortInt. > Pascal syntax related questions may be appropriate in: > > comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO > standards. > comp.lang.pascal.borland Borland Pascal questions. I'm wondering if we should suggest c.l.p.b at all. Is anyone monitoring it for GPC related questions regularly? (I'm not reading it anymore because of the high noise/signal ratio...) Also, the new gpc-doc mailing list could be mentioned here. It's still in the starting phase, but it will be the place for documentation related discussions (such as this FAQ :-). The last two changes apply to the upcoming release, due to some recent changes: > - A few unportable routines are not supported in the Dos unit (see > the comments there). I think there's an older, unportable, Dos > unit which supports them (or else it's easy to write one) if you > really need those routines... - A few unportable routines in the Dos unit are only supported under DJGPP if `__BP_UNPORTABLE_ROUTINES__' is defined (i.e., when compiling with `-D__BP_UNPORTABLE_ROUTINES__'). > Then, add this to your `djgpp.env' file: > > --------------------------------------------------------- > [gpc-cpp] We renamed the preprocessor to gpcpp, so this line should read then: [gpcpp] When the FAQ is complete so far, let us know so we can include it into the upcoming release distribution. 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

1 0

Re: faq-version 3
by Frank Heckenbach 10 Apr '00

10 Apr '00

Russ Whitaker wrote: > At long last here's vers 3 of the proposed FAQ A few more typos: compatable -> compatible proir -> prior kernal -> kernel nee -> need > and you can find the units directory with > find /usr/local/lib -name units Better: and you can find the units directory with gpc --print-file-name=units after installation. If this doesn't give the correct directory (or just says `units'), your installation is not quite right yet. > flags : short; This should be ShortInt. > Pascal syntax related questions may be appropriate in: > > comp.lang.pascal.ansi-iso Pascal according to ANSI and ISO > standards. > comp.lang.pascal.borland Borland Pascal questions. I'm wondering if we should suggest c.l.p.b at all. Is anyone monitoring it for GPC related questions regularly? (I'm not reading it anymore because of the high noise/signal ratio...) Also, the new gpc-doc mailing list could be mentioned here. It's still in the starting phase, but it will be the place for documentation related discussions (such as this FAQ :-). The last two changes apply to the upcoming release, due to some recent changes: > - A few unportable routines are not supported in the Dos unit (see > the comments there). I think there's an older, unportable, Dos > unit which supports them (or else it's easy to write one) if you > really need those routines... - A few unportable routines in the Dos unit are only supported under DJGPP if `__BP_UNPORTABLE_ROUTINES__' is defined (i.e., when compiling with `-D__BP_UNPORTABLE_ROUTINES__'). > Then, add this to your `djgpp.env' file: > > --------------------------------------------------------- > [gpc-cpp] We renamed the preprocessor to gpcpp, so this line should read then: [gpcpp] 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

1 0

Re: faq-version 3
by Russ Whitaker 10 Apr '00

10 Apr '00

That's 3 typos and 3 spelling errors Either way, wouldn't have found them without your help Thanks russ ---------- > From: Tom Schneider <toms(a)ncifcrf.gov> > To: russwhit(a)mind.net > Subject: Re: faq-version 3 > Date: Sunday, April 09, 2000 5:14 PM > > Russ: > > YEA!! A Faq!! > > A quick glance showed up some spelling errors (or more likely typos) ; so > here are my $0.02: > > definately -> definitely > disriminants -> discriminants > distrubution -> distribution > recomended -> recommended > replacemnet -> replacement > requiremnent -> requirement > saparately -> separately > > That's enough for a quick pass ... > > Tom > > Dr. Thomas D. Schneider > National Cancer Institute > Laboratory of Experimental and Computational Biology > Frederick, Maryland 21702-1201 > toms(a)ncifcrf.gov > permanent email: toms(a)alum.mit.edu > http://www.lecb.ncifcrf.gov/~toms/ >

1 0

Re: 6 MOD -90 Problem on Windows
by Mariusz Zynel 07 Apr '00

07 Apr '00

Peter Gerwinski <peter(a)gerwinski.de> wrote: > > What I'd like to have checked is whether GNU C's "mod" operation > produces different results on different platforms. If so, we > have detected a bug in the backend, otherwise in the frontend. My 0.02$ in this thread... Under Solaris 7 on both Intel and Sparc machines, GCC gives that 6 mod -90 is 6, while GPC gives -84. Regards -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

2 1

Re: GPC: how to patch gcc 2.95.2 ?
by Martin Maechler 07 Apr '00

07 Apr '00

>>>>> "Peter" == Peter Gerwinski <peter(a)gerwinski.de> writes: Peter> You can patch it with the same diff as 2.95.1. MM> MM> but there's no such diff in the gpc sources! Peter> --> get current (alpha) distribution, gpc-19991030. Peter> (the next one is in preparation) Okay, I got that one, I found the proper patch file in diffs/p applied and was able to "configure & make" successfully. Next step "install" does not work according to the documentation in gpc/p/INSTALL >> 8. When everything compiles, you can verify what the `make -n >> pascal.install' command does, and if you are satisfied run it >> without the `-n' option to install the compiler `gpc1', front end >> `gpc', run time system `libgpc.a' to the same place where `gcc' >> was installed. This installation process does *not* overwrite >> existing copies of `libgcc.a' or `specs', should they exist. >> >> You can also install GPC as part of the complete GNU compiler >> suite using "make install" as described in the GCC installation >> docs. ....% make pascal.install ------------------- make: *** No rule to make target `pascal.install'. Stop. Now there's really no "pascal.install" target in the Makefile. The corresponding section in the Makefile is >> INSTALL_MODULES = \ >> install-apache \ >> install-ash \ >> install-autoconf \ >> install-automake \ >> ......... (lots omitted) ........... >> install-tgas \ >> install-time \ >> install-uudecode \ >> install-wdiff \ >> install-zip \ >> $(EXTRA_TARGET_HOST_INSTALL_MODULES) and $(EXTRA_TARGET_HOST_INSTALL_MODULES) is empty >> # These can be overridden by config/mt-*. >> # The _TARGET_ is because they're specified in mt-foo. >> # The _HOST_ is because they're programs that run on the host. >> EXTRA_TARGET_HOST_ALL_MODULES = >> EXTRA_TARGET_HOST_INSTALL_MODULES = >> EXTRA_TARGET_HOST_CHECK_MODULES = I've used a build directory different from source, and written ../gpc-gcc-src/gcc-2.95.2/configure which gave Configuring for a i686-pc-linux-gnu host. Created "Makefile" in /usr/local/app/gcc-build using "mt-frag" Configuring libiberty... creating cache ../config.cache ................ What would have been the correct configure statement ? How do I (non-manually) install gpc now ? BTW: Tried "make check" also which ran quite a few things and ended in errors (but not within gpc testing I think). Should I report this somewhere ? ------------------------ Peter> A new version of the FAQ is in preparation. Please search the Peter> list archives for it. MM> MM> no url? Peter> http://www.gnu.de/archive/wilma.cgi/gpc. (also on homepage) not quite. The above is a "Search" interface to the gpc mailing lists, and the homepages has a link to a FAQ; but that FAQ is more than three years old. Thanks again

3 3

Case-insensitive defines
by Frank Heckenbach 07 Apr '00

07 Apr '00

Hi, as you might know, GPC supports "defines" for two purposes, as conditionals for `ifdef' etc. (like some other Pascal compilers do), and as macros (like the C preprocessor). However, currently they're case-sensitive (like in C) which is different from other Pascal compilers (e.g., Borland Pascal) and generally not very "Pascalish", so I want to introduce case-insensitive defines. But there are also a few valid uses for case-sensitive defines, so I'd like to keep both. Actually, I've already done most of the work. The question that remains is about the syntax. Currently, GPC understands: #define foo -- inherited from the C preprocessor, but not recommended {$d foo} -- we plan to change this. More precisely, we want to drop all the one-letter directives except those compatible to BP as well as $M (not the same as in BP, but no problem as it will only write a harmless message for the BP memory directives which are unnecessary in GPC) and $W (warnings -- quite widely used). {$define foo} -- this is what BP uses. So for BP compatibility, we should probably make {$define} case-insensitive, and rename {$d} to something longer and leave it case-sensitive. Any suggestions? I thought of maybe {$def}, but this wouldn't make the difference to {$define} very clear. OTOH, something like {$define-case-sensitive} would make it clear, but it's very long. Peter has suggested {$cdefine} (c for `C' or for `case'). We're not very fond of either of them, perhaps someone has got a better idea... 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

7 8

Vs: building GPC compiler + FAQ
by Pernille Bech & Klaus F. Østergaard 07 Apr '00

07 Apr '00

The new FAQ is hard to find, only through mailing archive. Should it not be at the ftp site? and on the GPC homepage? regarding building a GPC compiler, on a redhat 6.0, I followed the instructions from the new FAQ: I have installed a gcc-2.95.2.i686.rpm which is working using gcc-2.95.2.tar.gz and gpc-19991030.tar.gz unpacked them in /usr/local/src moved /p to /gcc applied the patch and when I come to configure it does not work and I get this: I use this command : ../gcc-2.95.2/configure --enable-languages=pascal "i686" it returns this: Created "Makefile" in /usr/local/src/gcc-build /usr/bin/ld: cannot open crt1.o: No such file or directory collect2: ld returned 1 exit status *** The command 'gcc -o conftest -g -O2 conftest.c' failded. *** You must set the enviroment variable CC to a working compiler. What is wrong? kind regards, klaus

3 2

Re: GPC: how to patch gcc 2.95.2 ?
by Frank Heckenbach 07 Apr '00

07 Apr '00

Peter Gerwinski wrote: > > BTW: Tried "make check" also which ran quite a few things and ended in > > errors (but not within gpc testing I think). > > Should I report this somewhere ? > > There "should" be four (IIRC) known bugs in the GPC test suite > (tests not ending up in "TEST foo.pas OK"). If there are > significantly more failures, then something went wrong, and you > should report it here. But `make check' doesn't run the "real" test suite, but the old dejagnu stuff. Try `make check2-gpc' instead. 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

1 0

6 MOD -90 Problem on Windows
by Tim Kaulmann 06 Apr '00

06 Apr '00

Hello ! I found out that the result of 6 MOD -90 in my little Pascal Program on Windows is -84 and on Solaris is 6 (in my opinion the right one). Whats up there ? BTW : My Calculator HP48 says that -84 was right ??? A matter of definition ? Hope you can help me. Tim

5 11

Using a unit as a record name...
by Orlando Llanes 06 Apr '00

06 Apr '00

I don't know what else to call the subject, but here's a fragment of code that will show what I want to do: type TEDFileIO = object Handle : File; destructor Close; virtual; end; destructor TEDFileIO.Close; begin System.Close(Handle); end; I'm having slight trouble compiling the latest version (I just started to use Linux on a regular basis). The last binary version of GPC did not allow me to do this. If the above does not work, is there a way around it in which I would not have to change the name of the method? See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 1

Re: Byte Order checking without {$ifdef}'s...
by Frank Heckenbach 06 Apr '00

06 Apr '00

Marco van de Voort wrote: > > The above code should compile, I translated it from the BP code. The > > only difference is in the type declarations; mByteOrder must always be > > 32-bits, and mByte must always be an array of 4 elements with 8-bits each, > > hence the use of Cardinal(x). > > The way it works is simple, and the code does not depend on any > > compiler specific syntax (except for type declarations) so it should > > compile correctly in the long run. AFAIK, constants are compiled in the > > native byte order of the target architecture. By comparing the long value > > as bytes, one-by-one, the byte order can be determined, hence the > > endianess can also be determined. > > I have tested this code on a Macintosh computer (which is the only > > big-endian machine I currently have access to), and have of course tested > > this on a PC. The results displayed are correct in both architectures. > > This is very nice, but will require runtime testing (and checking of the bigendian > flag *each* time) True. Of course, you could do the test once per program and save the result in a static variable, but still I don't quite see the need for runtime endianness checking... > Maybe it is smarter to let the above program output something to an includefile. > > The makefile should then always compile the above program prior to the actual > compilation. > > This way one would have the flexibility AND the compiletime decision between > little and big endian? This would make the build process more complicated and, worse, wouldn't work at all for cross-compiles where you usually can't run a program on the target machine (Linux->Dos with DosEmu perhaps being an exception ;-). But fortunately this isn't necessary because GPC also provides the information, both as pre-defines and as constants -- look for `endianness' in gpc.pas. I'd recommend to use the constants when possible and the defines only when necessary (e.g., when type declarations depend on them) because `ifdef' etc. is generally unsafer (e.g., you won't even detect syntax errors in the version of the code not for your current working system). BTW, that's also how I wrote the endian conversion routines, to answer Orlando's question. 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

1 0

Byte Order checking without {$ifdef}'s...
by Orlando Llanes 05 Apr '00

05 Apr '00

This is something that is prolly considered "common-sense" but I'm posting anyway just in case someone can benefit from it. I might've gotten the idea from Frank's code posted a while back, I don't remember how he implemented Endian conversion routines. Here's the code: program Test_Endian; const ByteOrder = $01020304; function LittleEndianCPU: Boolean; var mByteOrder : Cardinal(32); mByte : array[ 1..4 ] of Cardinal(8); begin mByteOrder := ByteOrder; Move(mByteOrder, mByte, 4); LittleEndianCPU := (mByte[1] = 4) and (mByte[2] = 3) and (mByte[3] = 2) and (mByte[4] = 1); end; function BigEndianCPU: Boolean; var mByteOrder : Cardinal(32); mByte : array[ 1..4 ] of Cardinal(8); begin mByteOrder := ByteOrder; Move(mByteOrder, mByte, 4); BigEndianCPU := (mByte[1] = 1) and (mByte[2] = 2) and (mByte[3] = 3) and (mByte[4] = 4); end; begin WriteLn( 'Little Endian CPU present -> ', LittleEndianCPU ); WriteLn( ' Big Endian CPU present -> ', BigEndianCPU ); end. The above code should compile, I translated it from the BP code. The only difference is in the type declarations; mByteOrder must always be 32-bits, and mByte must always be an array of 4 elements with 8-bits each, hence the use of Cardinal(x). The way it works is simple, and the code does not depend on any compiler specific syntax (except for type declarations) so it should compile correctly in the long run. AFAIK, constants are compiled in the native byte order of the target architecture. By comparing the long value as bytes, one-by-one, the byte order can be determined, hence the endianess can also be determined. I have tested this code on a Macintosh computer (which is the only big-endian machine I currently have access to), and have of course tested this on a PC. The results displayed are correct in both architectures. See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 2

Re: 6 MOD -90 Problem on Windows
by Frank Heckenbach 05 Apr '00

05 Apr '00

Tim Kaulmann wrote: > I found out that the result of 6 MOD -90 in my little Pascal Program on > Windows is -84 and on Solaris is 6 (in my opinion the right one). > Whats up there ? > BTW : My Calculator HP48 says that -84 was right ??? > A matter of definition ? Actually, it's defined as an error when the right operand is <=0. So probably we should implement such a check in GPC (perhaps together with other kinds of range or overflow checking). If in your program the right operand is a variabls which might be negative, I suggest to use `Abs' (i.e., `a mod Abs (b)'), since a mod b = a mod (-b), according to "your" definition. 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

1 0

Re: librares for GPC and (or) GCC
by Frank Heckenbach 28 Mar '00

28 Mar '00

Robson wrote: > On 14 Mar 00, at 20:45, Robson Ferreira wrote: > > > I want to know if you help me to resolve some > > problems in to compile programs in the linux. > > I am using the compiler GPC for to compile programs > > in Pascal and my problem is that some libraries not > > compile (crt.h,dos.h,io.h) " how to resolve this?"; > > and I am using GCC to compile programs in C > > an has the equal problem (conio.h,...). Some > > commands not execute (fgets,getch,delay, > > clsrcr, gets) in the LINUX... > > Help me, please... > > GPC cannot use the C headers directly. You have to convert them > into Pascal. For more information about GPC programming under > Linux, post your questions to "gpc(a)gnu.de". You will have people > who use Linux all the time and who will be able to answer your > questions there. Some functions in these DJGPP headers headers are not portable (some are, e.g. fgets, but others like clrscr aren't), so you can't use them under Linux directly. Furthermore, as The Chief said, you can't use C headers directly... However, recent releases of GPC come with a set of units which are both portable and written in Pascal, so that's probably what you need. For the headers mentioned, you probably want to look into the GPC, CRT and maybe Dos units. (The Dos unit, despite its name, is portable as well.) 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

1 0

Re: librares for GPC and (or) GCC
by Robson 28 Mar '00

28 Mar '00

-----Mensagem original----- De: Dr A Olowofoyeku <laa12(a)law.keele.ac.uk> Para: Robson Ferreira <ferreira(a)ufu.br> Data: Sexta-feira, 24 de MarÃ§o de 2000 5:34 Assunto: Re: librares for GPC and (or) GCC On 14 Mar 00, at 20:45, Robson Ferreira wrote: > I want to know if you help me to resolve some > problems in to compile programs in the linux. > I am using the compiler GPC for to compile programs > in Pascal and my problem is that some libraries not > compile (crt.h,dos.h,io.h) " how to resolve this?"; > and I am using GCC to compile programs in C > an has the equal problem (conio.h,...). Some > commands not execute (fgets,getch,delay, > clsrcr, gets) in the LINUX... > Help me, please... GPC cannot use the C headers directly. You have to convert them into Pascal. For more information about GPC programming under Linux, post your questions to "gpc(a)gnu.de". You will have people who use Linux all the time and who will be able to answer your questions there. Best regards, The Chief ----- Dr Abimbola A Olowofoyeku (The African Chief) Email: African_Chief(a)bigfoot.com Author of Chief's Installer Pro v5.22 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm

1 0

Re: Probably build RTFM issue.
by Frank Heckenbach 26 Mar '00

26 Mar '00

Mariusz Zynel wrote: > > Neither GNU make, patch nor (I think) install should be required. > > ... but GNU patch is necessary. GNU make and install are optional, > at least for me. I'm using Solaris 7 and 8 on Sparc and x86. Strange, since we use context diffs which should be most portable. But anyway, sometime soon, GPC will not need any GCC patches at all, and this problem will be gone automatically... 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: gpc on Sun
by Mason Ip 22 Mar '00

22 Mar '00

I have no problem with the (more-or-less) latest gcc and gpc. gpc -v Reading specs from /opt/GCC2951/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/specs gpc version 19991030, based on 2.95.1 19990816 (release) gpc --borland-pascal -O -o xx xx.pas <-- compilation OK; executable OK ---------- From: Veselic [SMTP:veselic@zagreb.FernUni-Hagen.de] Sent: Wednesday, March 22, 2000 6:26 AM To: gpc(a)gnu.de Subject: gpc on Sun Dear gpc-ers, just hearing on problems with gpc on Sun my Sun Solaris has binary-loaded gpc as follows GNU Pascal version 19990118, based on gcc-2.8.1, compiled Jan 18 1999 18:50:47. Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. However, a lot (not all) of sources compiling smoothly under PC-Linux now halt compiling with the message gpc --borland-pascal -O -o sj sj.p gpc: Internal compiler error: program gpc1 got fatal signal 6 Sometimes there is 'fatal signal 11'. Can anybody help? Thanks, K. Veselic.

1 0

Re: Probably build RTFM issue.
by Frank Heckenbach 22 Mar '00

22 Mar '00

Mariusz Zynel wrote: > > Build platform: Sun Solaris 2.7 > > GNU 'make' version: 3.78.1 > > GNU 'patch' version: 2.5.4 > > > > There is a newer alpha GPC release, which builds less painfull on > Solaris. I had problems due to bash extensions used in Makefile-s. > > Besides, there are Solaris binaries in pkgadd form to download at: > > http://math.uwb.edu.pl/download > ftp://mizar.uwb.edu.pl/pub/misc > > Hope this helps The `if ! [ ... ]' Makefile problem will be solved in the next release. Were there any more problems left in the last release? Neither GNU make, patch nor (I think) install should be required. 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

gpc on Sun
by Veselic 22 Mar '00

22 Mar '00

Dear gpc-ers, just hearing on problems with gpc on Sun my Sun Solaris has binary-loaded gpc as follows GNU Pascal version 19990118, based on gcc-2.8.1, compiled Jan 18 1999 18:50:47. Copyright (C) 1987, 89, 92-97, 1998 Free Software Foundation, Inc. However, a lot (not all) of sources compiling smoothly under PC-Linux now halt compiling with the message gpc --borland-pascal -O -o sj sj.p gpc: Internal compiler error: program gpc1 got fatal signal 6 Sometimes there is 'fatal signal 11'. Can anybody help? Thanks, K. Veselic.

1 0

Probably build RTFM issue.
by Randy Latimer 21 Mar '00

21 Mar '00

Hi. I've just built your package and have a possible bug report. Of course, this may be a RTFM isuue, but I felt I should offer this report none the less. Synopsis: When installing the package, the install of the units, docs, and demos causes fatal make errors. Detailed descripion: Download date: 20 Mar 2000 Download site: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/current/ Package: gpc-19990118.tar.gz Build platform: Sun Solaris 2.7 GNU 'make' version: 3.78.1 GNU 'patch' version: 2.5.4 (Note: I also built this package on a RedHat Linux v6.0 system without this error occurring. 'INSTALL_DATA', which is set to the same value as 'INSTALL' appears to have been configured with the value '/usr/bin/install -c'.) The configure script appears to have set the values of both INSTALL and INSTALL_DATA to './install.sh -c'. This causes the installation of units, demos, and docs to fail. The makefile which is generated, performs a change of directory prior to calling 'INSTALL_DATA'. I modified the Makefile and added '../../' prior to the $(INSTALL_DATA) in the offending lines (three of them). These lines appeared in the 'pascal.install-*' rules. The changes were as follows. pascal.install-units: pascal.install-dir $(srcdir)/p/units/crtc.h . . . cd $(srcdir)/p/units; \ for file in *.pas *.inc *.c *.h; do \ ../../$(INSTALL_DATA) $$file $(unitsubdir)/$$file; \ chmod a-x $(unitsubdir)/$$file; \ done pascal.install-demos: pascal.install-dir cd $(srcdir)/p/demos; \ for file in *; do \ ../../$(INSTALL_DATA) $$file $(demodir)/$$file; \ chmod a-x $(demodir)/$$file; \ done pascal.install-info: pascal.info -rm -f $(infodir)/gpc.info* ; if [ -f p/doc/gpc.info ]; then \ cd p/doc; \ else \ cd $(srcdir)/p/doc; \ fi; \ for f in gpc.info*; do \ ../../$(INSTALL_DATA) $$f $(infodir)/$$f; \ done Further investigation shows that the Linux box (which installed just fine) has the GNU version of 'install' and the 'install' on the Sun is the version that ships from Sun. Your configure script may want to use GNU 'install' and chooses to use your 'install.sh' script in place of 'install' if GNU 'install' is not found. This appears to be the case. Conclusion: This entire situation may be a RTFM issue. However, I read the README and INSTALL file and no mention was made of needing to install GNU versions of make, patch, or install. The fact that I needed to install GNU make and GNU patch were SWAG's (Scientific Wild A$$ Guess's) on my part and only during the composition of this email have I realized that there is a GNU version of install as well. Thank you for the product and sorry for this email if it's an RTFM issue. -- Randy Latimer ______|___________________ Program in Human Genetics | | || || NS | | Department of Physiology & Biophysics | | [ ] ||[ ]|| [ ] | | Vanderbilt University School of Medicine |__|_____||____||_____|__| Nashville, Tennessee, USA O<=>O O<=>O ------------------------------------------------------------------------ "A man's mind, stretched by new ideas, can never go back to its original dimensions." Oliver Wendell Holmes

2 1

Newbie question about cygwin
by Matze Braun 19 Mar '00

19 Mar '00

Hello, I'm using GPC for DJGPP at the moment, which works perfect. Now I wanted to try the cygwin port of GPC. I've installed the cygwin b20 and then the version from "the Chief". I can compile C programms, but every time I compile .PAS programms I got the message, that gpc-cpp can't be executed. I think, it's because the cygwin b20 is still an egcs version and the gpc version is 2.95.1 Is it possible to mix 2 versions, if not can someone give me a hint how to compile the cvs snapshots of cygwin? Thanks in advance Matze

2 1

Re: SetTextBuf
by Frank Heckenbach 18 Mar '00

18 Mar '00

Mariusz Zynel wrote: > I'm porting some software written in BP to GPC. How to simulate > SetTextBuf which takes two or optionaly three arguments? Grmpf. Another of these pseudo-overloaded BP routines... :-( > There > is SetTextBuf in GPC System unit, but this takes two arguments. > > Should I drop using the buffer size - third argument? Possibilities are: - Drop the buffer size, as you said. - We add a 3rd parameter in the system unit (but then every program which uses only 2 parameters would "suffer"). - We make it dependent on an ifdef, like the type sizes etc., but I don't like this (and still programs that use both versions will have problems). - Use the following dirty trick to ignore the 3rd (and any following) parameters. Note that macros are case-sensitive and don't work across units (so you have to put it in each program/unit that does this). {$define SetTextBuf(a,b,c...) SetTextBuf(a,b)} - Put two versions of the procedure under slightly different names in the unit. (I'll do this for now. SetTextBuf3 will be in the next release.) - Build SetTextBuf into the compiler and use compiler magic. (I don't like this, either, because actually we want to reduce the number of magic routines in the compiler.) - Implement procedure overloading in GPC. That's, of course, the right solution, but too much work for us to do right now (but if you'd like to volunteer to implement it in GPC... ;-). > Thanks in advance for any suggestion I hope these were enough for today... ;-) 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

Install problem - cannot exec cpp
by Mark Taylor 17 Mar '00

17 Mar '00

Another novice question - I'm afraid. When trying to compile a program which USES GPC,CRT; I'm getting an error... GPC installation problemm cannot exec cpp - no such file module/unit CRT could not be compiled I tried both the DJGPP port & Dr Olowofoyeku's Mingw port & got the same message from both, so I think I must be making a silly mistake somewhere - sorry. Mark. -- Mark Taylor, Department of Corporate Information & Computing Services, Extension 21145. (0114) 222 1145 http://www.shef.ac.uk/misc/personal/ad1mt The opinions expressed in this email are mine and not those of the University of Sheffield.

3 4

GPC for Mingw32
by Dr A Olowofoyeku 17 Mar '00

17 Mar '00

Hi all A new snapshot of GPC (Mingw32) has been uploaded to Agnes. This is based on Peter's recent native Mingw32 build (based on gcc 2.95.1). The file is: ftp://agnes.dida.physik.uni-essen.de/home/chief/ gpc-20000202-i586-mingw32.zip If you unzip (with an unzip program that understands long filenames) into 'c:\usr\', reproducing the directory structure in the zip file, you should have a ready-to-run and stable Win32 snapshot of GPC (you just need to add 'c:\usr\local\bin' to the PATH). Best regards, The Chief ----- Dr Abimbola A Olowofoyeku (The African Chief) Email: African_Chief(a)bigfoot.com Author of Chief's Installer Pro v5.22 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm

1 0

variable := zero;
by Wren Lee 17 Mar '00

17 Mar '00

I am currently converting an OpenVMS DEC-PASCAL model into GPC (v.19991030 based on 2.95.2 19991024) on a LINUX PC. Part of this task is to, where ever possible, maintain a common source between the two systems. The model initialises many variables using the DEC-PASCAL function "ZERO", is there an equivalent within GPC that works with any variable, or record, type. VAR i : INTEGER; r : REAL; d : ARRAY[1..5] OF DOUBLE; BEGIN i := zero; r := zero; d := zero; END. I've searched the documentation but cannot find anything, the closest I've come is to pass an untyped parameter and its size to a function, then use pointers to set the memory to zero (0x00). This works OK for GPC, but DEC-PASCAL doesn't seem to like untyped parameters. Any help would be appreciated, as would any comments from people who have undertaken a similar task. Thanks, in advance Lee. -- The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful.

2 1

Re: Mingw GPC bug - was cannot exec cpp
by Mark Taylor 17 Mar '00

17 Mar '00

Subject: Re: Mingw GPC bug - was cannot exec cpp > have you done that ? it is not done by default. Many thanks. No - had not done any except the first. Is this documented anywhere or did you figure it out for yourself? While desperate to avoid C for a new programming project I am going to start soon, I am getting very disheartened with GPC, and am thinking of reverting to GNU C. Mark. -- Mark Taylor, Department of Corporate Information & Computing Services, Extension 21145. (0114) 222 1145 http://www.shef.ac.uk/misc/personal/ad1mt The opinions expressed in this email are mine and not those of the University of Sheffield.

3 2

gpc macht nich, was er soll
by da_worm＠gmx.li 17 Mar '00

17 Mar '00

ich nutze den gpc der suse 6.2 linux distribution bereits seit einem halben jahr. funktionierte gut! nchdem ich jetzt mandrake 7.02 installierte, mich wieder dagegen entschied und erneut suse 6.2 aufzog, meldet mir der gpc beim compilieren das die functionen & proceduren meines programmes 'first use in GNU/??/??/lib/blah' haben. das tut er mit allen funktionen & proceduren. teilweise werden die zu compilierenden quelltexte durch die option (die bisher immer ihren dienst tat!) gelÃ¶scht (!!!), was zum teil sehr fatal sein kann... bitte um antwort. thx alot Da Worm -- Sent through GMX FreeMail - http://www.gmx.net

2 1

SetTextBuf
by Mariusz Zynel 17 Mar '00

17 Mar '00

Hi, I'm porting some software written in BP to GPC. How to simulate SetTextBuf which takes two or optionaly three arguments? There is SetTextBuf in GPC System unit, but this takes two arguments. Should I drop using the buffer size - third argument? Thanks in advance for any suggestion -- . Mariusz Zynel Institute of Mathematics | phone: +48 (85) 745 75 52 University of Bialystok | Akademicka 2 St | mailto:mariusz@math.uwb.edu.pl 15-267 Bialystok | Poland | http://math.uwb.edu.pl/~mariusz/

1 0

GPC: Win32 API import units
by Dr A Olowofoyeku 17 Mar '00

17 Mar '00

Hi all You can get the latest version of my ongoing work of translating the GCC WinAPI headers to GPC import units from agnes (in the directory: ftp://agnes.dida.physik.uni-essen.de/home/chief/). The sources (messages.pas, wintypes.pas and winprocs.pas) are in: ftp://agnes.dida.physik.uni-essen.de/home/chief/winapi-src.zip The precompiled units are in: ftp://agnes.dida.physik.uni-essen.de/home/chief/winapi-bin.zip. I suggest that you put the precompiled units in your GPC 'units' directory, and keep the sources elsewhere (where they won't be located automatically by the compiler). That way you will get much faster compiles and links (two of the units are quite huge, and until automake is fixed, you don't want GPC to try and compile them all the time). Since the original GCC headers are LGPL, I guess that this makes my Pascal translations LGPL as well. If anyone wishes to help to debug/test/develop/complete these units, please feel free to jump in! I have been working on this for about a year, and it is quite clear that it is way beyond the capacity of one person to complete. Best regards, The Chief ----- Dr Abimbola A Olowofoyeku (The African Chief) Email: African_Chief(a)bigfoot.com Author of Chief's Installer Pro v5.22 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm

1 0

Documentation list
by Peter Gerwinski 17 Mar '00

17 Mar '00

Hello, we now have a separate list for documenting GPC. Everyone who wants to contribute to the GPC documentation project is invited to join. We have splitted this list from the main GPC list because some documentation issues are not of interest for users of GPC. (For instance, spelling wars are off-topic on the ordinary GPC list, but they can be on-topic on the GPC documentation list.:-) The GPC documentation list is <gpc-doc(a)gnu.de>. To subscribe to the list, write a message containing "subscribe gpc-doc" in the body to <majordomo(a)gnu.de>. (The subject will be ignored.) Happy hacking, Peter -- http://home.pages.de/~Peter.Gerwinski/ - G-N-U GmbH: http://www.g-n-u.de Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 GnuPG key fingerprint: 9E7C 0FC4 8A62 5536 1730 A932 9834 65DB 2143 9422 keys: ftp://ftp.gerwinski.de/pub/keys/ - AntiSpam: http://spam.abuse.net

1 0

RE: Obscure features of GPC
by J Blakeney 16 Mar '00

16 Mar '00

Does anyone know how to access "ellipsis" parameters for that define variable argument lists for precedures on a Pentium linux system. e.g. Procedure A_Procedure ( a: Integer; ... ); The GNU pascal documentation says the access method is implementation dependent, but as far as I can see doesn't give any methods [I've tried accessing via pointers and successfully crashed my computer] Thanks John Blakeney

2 1

Re: How to compile hello.pas for win32
by Frank Heckenbach 12 Mar '00

12 Mar '00

Dr A Olowofoyeku wrote: > > Presumably these get fed through to the back-end c-preprocessor? > > Presumably. I believe that this is one of those things that GPC > inherits from GCC. Yes (though it's not exaclty back-end, but rather a pre-front-end, but that's nitpicking). Since the GCC preprocessor already supports include files and ifdefs (which GPC needs for compatibility to BP and other compilers), it was easiest to just take it and allow the `{$foo}' syntax in addition to `#foo'. And the additional features (mainly macros) are certainly not a disadvantge ;-). Most uses of macros in C are not necessary in Pascal where we have constants and inline functions(1), and also not recommended in GPC, but there are some situations where they come handy, like the one discussed here. (1) Yes, modern C compilers have that, too ("enum" and GCC's inline), but C programmers seem reluctant to use them... > > Are there any other obscure "features" like this in GPC that I might > > need to know about? > > Many (e.g., I guess you could do something like 'Var x : integer > (40)' to declare a 40-bit integer (if such a thing exists) - but I am not > sure how it will be handled by the compiler). That's right, though this feature doesn't come from GCC. (C doesn't have such a feature, except in "struct"s, which sometimes causes C programmers some headaches... ;-) They are handled mostly like subranges (e.g. Integer (6) = -32 .. 31) and are most often used to get types with a guaranteed size on any system (e.g. for compatibility with other compilers, or binary file compatibility, or when the requirements demand a fixed size, e.g. MD5 values are always 128 bit), since the size of plain `Integer' etc. can vary from system to system. > I am not sure where > they are all documented though. I obtain a lot of my information from > the GPC source code. Yes, the GPC documentation is lacking, that's perhaps the most urgent problem. However, the `Integer (40)' feature in particular is documented there under Reference/Integer. 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

8 14

Re: Documentation formatting languages (was: Obscure features of GPC)
by tov are jacobsen 12 Mar '00

12 Mar '00

On Sat, 11 Mar 2000, Peter Gerwinski wrote: [...] > One could consider moving to DocBook (SGML) which can produce > GNU Texinfo (and TeX and HTML and whatever). > > Opinions? > DocBook is very nice for technical documentation, and it appears to be the standard for a lot of free software projects such as Linux, GNOME and KDE. Currently GNOME is using the SGML version, but they have standardized on not using the SGML shorthands like </> so that migration to XML will be painless. I think an upcomming version of the Help browser will support on-the-fly formating of DocBook documents. Information on the GNOME documentation project complete with a really nice getting started manual can be found here: http://www.gnome.org/gdp/ -- Tov Are Jacobsen

1 0

About gcc compatibility (again)
by Khimenko Victor 11 Mar '00

11 Mar '00

I catch this mail in lklm few minutes ago. It touches old subject: is it safe to use old libgcc.a or you need to use only proper version. Looks like I was right after all :-) At least for ARM. Note last paragraph from following mail. As I have no ARM I can not comment on it, but... -- cut -- 11-Mar-00 16:26 you wrote: >From sch57!vger.rutgers.edu!owner-linux-kernel-outgoing Sat Mar 11 19:57:25 2000 Received: by khim.sch57.msk.ru (UUPC/@ v7.00, 06Mar97) with UUCP id AA02326; Sat, 11 Mar 2000 19:57:25 +0300 (MSK) Received: from nic.funet.fi (nic.funet.fi [193.166.0.145]) by dell.sch57.msk.ru (8.8.8/8.8.8) with ESMTP id TAA10429 for <linux-kernel(a)khim.sch57.msk.ru>; Sat, 11 Mar 2000 19:29:52 +0300 Received: from vger.rutgers.edu ([128.6.190.2]:13428 "EHLO vger.rutgers.edu" ident: "NO-IDENT-SERVICE[2]" smtp-auth: <none> TLS-CIPHER: <none>) by nic.funet.fi with ESMTP id <S5956AbQCKQgQ>; Sat, 11 Mar 2000 18:36:16 +0200 Received: by vger.rutgers.edu via listexpand id <S157604AbQCKM2o>; Sat, 11 Mar 2000 07:28:44 -0500 Received: by vger.rutgers.edu id <S160078AbQCKM1t>; Sat, 11 Mar 2000 07:27:49 -0500 Received: from p27-magpie-gui.tch.enablis.net ([194.168.180.27]:4470 "EHLO caramon.arm.linux.org.uk") by vger.rutgers.edu with ESMTP id <S157686AbQCKMYL>; Sat, 11 Mar 2000 07:24:11 -0500 Received: from raistlin.arm.linux.org.uk (root@raistlin [192.168.0.3]) by caramon.arm.linux.org.uk (8.9.3/8.9.3) with ESMTP id QAA18879; Sat, 11 Mar 2000 16:27:11 GMT From: Russell King <rmk(a)arm.linux.org.uk> Received: (from rmk@localhost) by raistlin.arm.linux.org.uk (8.7.4/8.7.3) id QAA07865; Sat, 11 Mar 2000 16:26:21 GMT Message-Id: <200003111626.QAA07865(a)raistlin.arm.linux.org.uk> Subject: Re: ADFS -> undefined reference to __cmpdi2 (2.3.51) To: matti.aarnio(a)sonera.fi (Matti Aarnio) Date: Sat, 11 Mar 2000 16:26:21 +0000 (GMT) Cc: Philip.Blundell(a)pobox.com (Philip Blundell), arjan(a)fenrus.demon.nl (Arjan van de Ven), linux-kernel(a)vger.rutgers.edu In-Reply-To: <20000311180544.E13396(a)mea.tmt.tele.fi> from "Matti Aarnio" at Mar 11, 2000 06:05:44 PM X-Location: london.england.earth.mulky-way.universe X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Sender: owner-linux-kernel(a)vger.rutgers.edu Precedence: bulk X-Loop: majordomo(a)vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig Lines: 35 Content-Type: text/plain; charset=us-ascii Content-Length: 1585 Matti Aarnio writes: > As Linus hasn't put it into i386 (nor Alpha), he has > some good reason. Ask him for guidance. That is probably because libgcc contained some stuff which was unsuitable for the kernel on x86. > Mainly I think we should NEVER use slow 64/* division routines > in fast paths. Ah, are you saying that the only thing that libgcc.a is used for is supposidly slow division routines? Some architectures need it for much much more than that. > As an end-result you will get your system free of need for > libgcc.a, and possible dangers lurking in it. No. libgcc.a is dependent on the compiler. I do know that code generated with one ARM gcc compiler does not work with the libgcc.a of a later compiler, suggesting that there is a difference in the API between the two versions of GCC. Hence, the only real way to get the correct behaviour in this case is to use libgcc.a for ARM. _____ |_____| ------------------------------------------------- ---+---+- | | Russell King rmk(a)arm.linux.org.uk --- --- | | | | http://www.arm.linux.org.uk/~rmk/aboutme.html / / | | +-+-+ --- -+- / | THE developer of ARM Linux |+| /|\ / | | | --- | +-+-+ ------------------------------------------------- /\\\ | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/ -- cut --

1 0

Re: FreeVision port to GPC: helpers needed
by Frank Heckenbach 10 Mar '00

10 Mar '00

Marco van de Voort wrote: > > > I mean that changing the TYPE of both methods will cause other procedures to > > > fail, causing an incompability with FV. > > > > > > Keeping the argument a untyped pointer, and then typecasting to a proctype will > > > probably not work, [...] > > > > It does work. > > How does it work effectively? So something like: > > procedure proc1(x:longint); > > procedure proc2(x:longint); > > begin > end; > > begin > end; > > type myproctype=procedure(x:longint); > > procedure proc3(x:pointer); > > begin > myproctype(x); (Missing argument here.) > end; > > begin > proc3(@proc1); > proc3(@proc2); > end; Like this, it won't work since proc2 isn't even visible to the main program. But you can call `proc3(@proc2);' from proc1 (if you declare proc3 before proc1, of course). 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

1 0

FreeVision port to GPC: helpers needed
by Dr A Olowofoyeku 10 Mar '00

10 Mar '00

Hi all I have been having discussions with Leon de Boer who is writing most of the FreeVision (FV) stuff. The project is being done to dispense with all copyright issues, and it seems that this has largely been achieved. I have ported the Objects unit to GPC, along with a few other units. The sticking point now is a number of the base units (drivers.pas, dialogs.pas and views.pas), which contain some assembler code. Some of these are in x86 assembler and some (determined by some IFDEFs) are in FPC assembler (which looks to me like the AT&T syntax). Since I understand neither of these, I can't proceed with the porting. If you would like to help with porting these units, then do please get in touch. It would seem better to recode these assembler routines in Pascal than to convert the FPC assembler to something that GPC can understand (if it isn't already in that form). In my opinion, if we can port these three units to GPC, then a working class library for GPC (which also supports several other Pascal compilers) is within reach. Best regards, The Chief ----- Dr Abimbola A Olowofoyeku (The African Chief) Email: African_Chief(a)bigfoot.com Author of Chief's Installer Pro v5.22 for Win32 http://www.bigfoot.com/~African_Chief/chief32.htm

4 11

Re: Obscure features of GPC
by Frank Heckenbach 10 Mar '00

10 Mar '00

Dr A Olowofoyeku wrote: > On 10 Mar 00, at 10:22, Mark Taylor wrote: > > > > Yes, the GPC documentation is lacking, that's perhaps the most > > > urgent problem. However, the `Integer (40)' feature in particular is > > > documented there under Reference/Integer. > > > > Do you mean the info database? Or the source code? > > I think he means the info database. Yes (though the same manual is also available in html, dvi and PostScript formats)... > > Can anyone recommend a list of documentation apart from the info > > database (I know about this), to help me having to pester people on > > this list with "novice" questions. > > > > I am trying to get myself "up to speed" with GPC and am finding it a > > bit problematic (I am a novice with GPC but not a novice programmer). > > Like Frank said, up-to-date documentation on GPC is currently a > major issue. Until one is produced, it seems that you have to find > any information you want from a variety of sources. This mailing list > and its archives is a good place to look. I have also found the stuff in > Frank's 'to do' pages (http://fjf.gnu.de/gpc-todo_toc.html) to be > informative. Thanks. ;-) Currently, it's often ahead of the actual releases (so check the dates on the new features and fixed bugs), but this will change with a CVS server... > Then the source code (especially the sources in the > 'units' directory). For the supplied units, this is recommended. For the RTS (i.e., libgpc), all public declarations can be found in gpc.pas -- except those routines that are called with compiler magic (mostly the predefined routines in the various language dialects). Frank PS (to all of you): No need to CC me personally. -- 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

1 0

Re: GC & GPC question.
by Frank Heckenbach 10 Mar '00

10 Mar '00

Khimenko Victor wrote: > > The relevant hooks are GetMemPtr etc., declared in the GPC unit. You > > need them if you want to switch between different allocators. > > Hmm. It'll require locks in multithreaded program and will be not very > convenient. I see. BTW, are the normal malloc()/free() routines and Boehm's GC thread-safe, do they do their own locking? I can't guarantee that GPC's heap handling routines are thread-safe as I haven't used threads. At first sight, I'd say they are as long as you don't use Mark/Release, but if you want to check them (or other RTS routines) more throughly, you have the source... > Perhaps we can hide it over clever #define ? Let's try: > > -- cut -- > uses gpc; > #define gc_alloc(x) (begin var res:^x; save_ptr:GetMemType; save_ptr:=GetMemPtr; GetMemPtr:=GC_alloc; res:=new(x); GetMemPtr:=save_ptr; end) Since the variables are declared within a statement part, you'd need a second `var' before save_ptr. Also, Pascal's `New' is syntactically different from C's malloc(). `New' is only meant for typed pointers (simple types, schemata, objects), while `GetMem' takes a memory size, but will not initialize any fields of the structure. The correspondence is `p = malloc (n)' -> `GetMem (p, n)'. > Oops. Is it possible to use compound statement as expression in GPC somehow ? Not AFAIK. Only as an inline function. The following should work, but as I said, it will not initialize any fields, so it won't work for strings, schemata, files and other types that require initialization (but you could write a second routine specialized for strings, as shown). inline function GCAlloc (x : SizeType) = Res : Pointer; var save_ptr : GetMemType; begin save_ptr := GetMemPtr; GetMemPtr := @GC_alloc; GetMem (Res, x); GetMemPtr := save_ptr end; function GCAllocString (const s : String) = Res : PString; var save_ptr : GetMemType; begin save_ptr := GetMemPtr; GetMemPtr := @GC_alloc; New (Res, Length (s)); Res^ := s; GetMemPtr := save_ptr end; var i : ^Integer; s : PString; begin i := GCAlloc (SizeOf (Integer)); s := GCAllocString ('foo'); Writeln (s^); end. Of course, you could then hide then `SizeOf' in a macro with something like: {$define gc_alloc(x) GCAlloc (SizeOf (x))} > And BTW how I can continue #define on next line (C's \ in the end of line does > not work). {$define ...} can span multiple lines without any `\'. Peter Gerwinski wrote: > Khimenko Victor wrote: > > Hmm. It'll require locks in multithreaded program and will be not very > > convenient. Perhaps we can hide it over clever #define ? Let's try: > > [...] > > You need to EXPLICITLY change new strategy every time :-(( > > Especially annoying since you want to use GC_malloc_atomic for plain strings... > > [...] > > What about introducing a second `New' that allows the user to > pass an additional parameter to the allocator? Might be a solution. (Not that the syntax of `New' isn't already complicated enough... :-/) 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

3 7

How to compile hello.pas for win32
by Mark Taylor 09 Mar '00

09 Mar '00

I tried converting this win32 hello.c program to pascal without success... #include <windows.h> int STDCALL WinMain (HINSTANCE hInst, HINSTANCE hPrev, LPSTR lpCmd, int nShow) { MessageBox (NULL, "Hello, Windows!", "Hello", MB_OK); return 0; } I was getting undefined references to messagebox at the linking stage. To compile I did... gpc -mno_cygwin -mwindows whello.pas -o whello.exe Thanks, Mark. -- Mark Taylor, Department of Corporate Information & Computing Services, Extension 21145. (0114) 222 1145 http://www.shef.ac.uk/misc/personal/ad1mt The opinions expressed in this email are mine and not those of the University of Sheffield.

3 4

Re: GC & GPC question.
by Frank Heckenbach 09 Mar '00

09 Mar '00

Khimenko Victor wrote: > This is NOT what you usually want. GC ALWAYS has penatly over "normal" > malloc/free way. Yes, there are benefits as well but when you are using > third-party library where malloc/free already used then with GC's replacement > you'll get slowdown and nothing more. In case of C it's all simple: just > use malloc/free and gc_alloc as desired. In case of C++ overloaded new can > be used for this purpose. In case of GPC you can have GC-enabled new (with > GC's malloc) or non GC-enabled new bot not both :-/ You can not just use > gc_alloc(sizeof(record)) since if record has embedded strings or files > you need to initialize it first (and if record has virtual part then new > can allocate less then gc_alloc(sizeof(record)) -- or is this Pascal's feature > not implemented yet?). So the question is: is it possible to use another > allocator (and deallocator) in GPC's new ? Something akin to > field:=new(malloc,OldNormalNonGcClass); > ptr:=new(gc_alloc,TestClass); > dispose(free,field); > > Something like this was discussed when shred memory allocation problem was > discussed but I can not find it :-/ The relevant hooks are GetMemPtr etc., declared in the GPC unit. You need them if you want to switch between different allocators. By default, AIUI, Boehm's GC, when linked in, will be used for all allocations without further action on the Pascal side. 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

3 3

Re: GC & GPC question.
by Frank Heckenbach 09 Mar '00

09 Mar '00

Khimenko Victor wrote: > 7-Mar-00 18:57 you wrote: > > One of the things that steers me away from Borland Pascal is its lack > > of a runtime garbage collector. > > > Does GNU Pascal have a runtime garbage collector? > > No. To All: perhaps something can be done here ? Boehm's GC will work just fine > with GPC in simple cases but if you'll try to use strings or some other complex > structures it'll be less great :-/ In C++ it's done with "class's new" but I > know of no such mechanism in GPC ... At least low-level allocation functions > needed (now many bytes GC should allocate to put this structure there? how > really put it there?)... I haven't used it yet, but I don't see the problem. AFAIUI, Boehm's GC <http://reality.sgi.com/boehm/gc.html> provides a drop-in replacement for malloc() (and a dummy replacement for free()). Since GPC's memory management uses malloc()/free() by default (it can be overwritten on the Pascal level, but this doesn't seem necessary here), it should work, however simple or complex the structures (malloc() doesn't care, it just gets a number of bytes and allocates that much memory). 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

3 5

Re: GC & GPC question.
by Frank Heckenbach 09 Mar '00

09 Mar '00

Khimenko Victor wrote: > Perhaps. If I'll be able to understood how to use GC at all (and no, NOT as > replacement for normal new/free functions!). As I've never used it so far, I can't tell you, but there must be a way to use it without replacing malloc/free. > P.S. If you are just replacing malloc with GC_alloc then you asking for > troubles (nasty DoS attacks). Depends on the kind of program, doesn't it? If it isn't a server (or run by one), the worst it could do is eat up memory and CPU time. But a malicious user who can run a program on a system can do this, anyway. Am I missing something? Of course, using GC_malloc_atomic can have its advantages, and you can use it with the hooks mentioned in my previous mail. 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

enumerated types problem
by miller＠otago.ac.nz 08 Mar '00

08 Mar '00

Greetings from New Zealand, It appears to me that in some situations gpc refuses to compile because it loses information about enumerated types defined in units. I'm using gpc version 19990118, based on gcc-2.8.1, under linux. (I gave up on using gpc under OS/2). Below is a minimal example--about 50 lines of source code divided across 2 units and a main program, all in separate files. Please tell me if I've done something wrong or if you know of a work-around. Thanks, Jeff Miller miller(a)otago.ac.nz http://psy.otago.ac.nz/miller Unit gnutstb1; { this unit is in file gnutstb1.pas } Interface Type MyType = (eenie, meenie, minie, mo, eenie2, meenie2, minie2, mo2, eenie3, meenie3, minie3, mo3, eenie4, meenie4, minie4, mo4, eenie5, meenie5, minie5, mo5, eenie6, meenie6, minie6, mo6, eenie7, meenie7, minie7, mo7, eenie8, meenie8, minie8, mo8, eenie9, meenie9, minie9, mo9 ); Basic = Object BoolArr : Array[MyType] of Boolean; Constructor Construct; End; Implementation Constructor Basic.Construct; Begin BoolArr[eenie] := True; BoolArr[meenie] := False; BoolArr[minie] := False; BoolArr[mo] := False; End; End. { end of file gnutstb1.pas } Unit gnutstb2; { this unit is in file gnutstb2.pas } Interface Uses gnutstb1; Type Derived1 = Object(Basic) Unused : Char; Constructor Construct; End; Implementation Constructor Derived1.Construct; Begin Basic.Construct; BoolArr[meenie] := True; End; End. { end of file gnutstb2.pas } Program GnuTstB3; { This main program is in file gnutstb3.pas } Uses gnutstb1, gnutstb2; Type Derived2 = Object(Derived1) Unused2 : Char; Constructor Construct; End; Constructor Derived2.Construct; Begin Derived1.Construct; BoolArr[minie] := True; { gpc says "type mismatch in array index" } End; Var D2 : Derived2; Begin D2.Construct; If D2.BoolArr[minie] { gpc again says "type mismatch in array index" } Then Writeln('True') Else Writeln('False'); End. { end of file gnutstb3.pas } When I issue the command gpc gnutstb3.pas --automake --borland-pascal I get the output gnutstb3.pas: In function `Derived2_Construct': gnutstb3.pas:17: type mismatch in array index gnutstb3.pas: In function `program_Gnutstb3': gnutstb3.pas:24: type mismatch in array index These files were made OK (as far as I can tell): gnutstb1.o gnutstb2.gpi gnutstb1.gpi gnutstb2.o

2 1

GC & GPC question.
by Joe Blask 08 Mar '00

08 Mar '00

One of the things that steers me away from Borland Pascal is its lack of a runtime garbage collector. Does GNU Pascal have a runtime garbage collector? Sincerely, ==Joe Blask==

4 6

RE: Mingw version of GPC based on latest GCC 2.95?
by Mason Ip 08 Mar '00

08 Mar '00

It is very nice of you, Dr A Olowofoyeku, to provide such a binary. But why is it labelled as gpc-19991111-etc? The latest source I could find was gpc-19991030, from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/. BTW, could gpc provide a CVS source, so that we can fetch the latest snapshot? > ---------- > From: Dr A Olowofoyeku[SMTP:laa12@law.keele.ac.uk] > Sent: Wednesday, March 08, 2000 4:22 AM > To: Mark Taylor; gpc(a)gnu.de > Subject: Re: Mingw version of GPC based on latest GCC 2.95? > > On 8 Mar 00, at 9:58, Mark Taylor wrote: > > > > > Has anyone built the Cygwin or Mingw version of GPC based on the > > latest GCC 2.95? > > > > Does anyone plan to do this? > > I have built a Cygwin compiler (which is also able to produce Mingw > programs), for gcc 2.95.2. You can download it from: > ftp://agnes.dida.physik.uni-essen.de/home/chief/ > > > > If not, I will have a go myself, but this might be a big effort as I > > have never built GCC or GPC before. If anyone can offer pointers I > > would be most gratefull. > > It is relatively straightforward to build a Cygwin compiler, as long as > you have the full and latest Cygwin distribution. I am due to write > some notes for building GPC on Cygwin, but I don't have the time > yet. If you can understand bash scripts, I can send you the > (commented) bash script that I use to automate all the steps. You > should be able to work from that. > > > If successfull, I would then be in a position > > to offer my services in helping with further development of the > > compiler. Something I would be interested in would be recoding GPC in > > Pascal (I am sure this would make it easier for more people to > > contribute their help) - would this be feasible, or does GPC *have* to > > be coded in C for some reason? > > Yes. AFAIK all GNU compilers *have* to be coded in C. Large parts > of the GPC runtime library are of course coded in Pascal. > > Best regards, The Chief > ----- > Dr Abimbola A Olowofoyeku (The African Chief) > Email: African_Chief(a)bigfoot.com > Author of Chief's Installer Pro v5.22 for Win32 > http://www.bigfoot.com/~African_Chief/chief32.htm >

2 1

Mingw version of GPC based on latest GCC 2.95?
by Mark Taylor 08 Mar '00

08 Mar '00

Has anyone built the Cygwin or Mingw version of GPC based on the latest GCC 2.95? Does anyone plan to do this? If not, I will have a go myself, but this might be a big effort as I have never built GCC or GPC before. If anyone can offer pointers I would be most gratefull. If successfull, I would then be in a position to offer my services in helping with further development of the compiler. Something I would be interested in would be recoding GPC in Pascal (I am sure this would make it easier for more people to contribute their help) - would this be feasible, or does GPC *have* to be coded in C for some reason? Mark. -- Mark Taylor, Department of Corporate Information & Computing Services, Extension 21145. (0114) 222 1145 http://www.shef.ac.uk/misc/personal/ad1mt The opinions expressed in this email are mine and not those of the University of Sheffield.

3 2

GPC and X-Windows
by ROMANIUK ALEŠ 08 Mar '00

08 Mar '00

Hi ! I have been using GPC on Sun/Solaris for a while, and at this point I want to know, If there exist X-Windows programing library, and If so, where can I get it. Regards Alex ============================ Alex Romaniuk, External Computer Systems (Technical Departement) Tel.+386 61 1722543 (Fax. 1722590) http://www.mobitel.si, Slovenia ===========================

3 2

Re: Cannot produce executable
by Russ Whitaker 02 Mar '00

02 Mar '00

Using gpc version 19991030, based on 2.95.2 19991024 (release) output is: HELLO yes Hope this helps Russ <russwhit(a)mind.net> ---------- > From: miller(a)otago.ac.nz > To: gpc(a)gnu.de > Cc: miller(a)psy.otago.ac.nz > Subject: Cannot produce executable > Date: Wednesday, March 01, 2000 2:55 PM > > Greetings, > > I have some statistical programs that I would like to release under GPL. > They were originally written in Borland Pascal and Speed Pascal (the latter > is a borland-like pascal for OS/2), and all the code compiles and runs fine > using those two compilers. Now I am trying to get everything to > compile and run under gpc, so that the code will be useful to more > people. It looks like I'll have a lot of questions along the way, > and I'd appreciate any help that can be provided. > > I'm using a version of gpc that I installed as a binary from the file > gpc-19990118_i386-pc-emx0_9d.zip > > I can compile and run little test programs that use no units, > or that use only type definitions from units, but I get "undefined symbol" > messages if the main program refers to any variables or procedures > defined in the interface part of the unit. > > Here is a small example, adapted from one posted recently. > > The file def.pas has the following unit: > > UNIT modul; > INTERFACE > > TYPE > CARDINAL = 0..65535; > LONGBITSET = SET OF 0..63; > > Var ModS : Integer; > > PROCEDURE HELLO; > > IMPLEMENTATION > > PROCEDURE HELLO; > BEGIN > WRITELN('HELLO'); > END; > > END. > > The file test.pas has this test program. > > program test; > USES modul; > var > i:CARDINAL; > c:LONGBITSET; > begin > ModS := 0; > Hello; > c:=[1]; > i:=1; > if (i in c) then writeln('yes'); > end. > > gpc -c def.pas works fine, but > gpc test.pas > yields the messages > d:\tcpip\tmp\ccc00799: Undefined symbol _Mods referenced from text segment > d:\tcpip\tmp\ccc00799: Undefined symbol _Hello referenced from text segment > > d:\tcpip\tmp is my temp directory, and I noticed that running gpc leaves > a lot lot of small files called cca000*.exe in the temp directory. > > Can anyone tell me what I'm doing wrong? > > Thank you for your time, > > Jeff Miller > Dept of Psychology > University of Otago > Dunedin, New Zealand > miller(a)otago.ac.nz > http://psy.otago.ac.nz/miller >

1 0

Cannot produce executable
by miller＠otago.ac.nz 02 Mar '00

02 Mar '00

Greetings, I have some statistical programs that I would like to release under GPL. They were originally written in Borland Pascal and Speed Pascal (the latter is a borland-like pascal for OS/2), and all the code compiles and runs fine using those two compilers. Now I am trying to get everything to compile and run under gpc, so that the code will be useful to more people. It looks like I'll have a lot of questions along the way, and I'd appreciate any help that can be provided. I'm using a version of gpc that I installed as a binary from the file gpc-19990118_i386-pc-emx0_9d.zip I can compile and run little test programs that use no units, or that use only type definitions from units, but I get "undefined symbol" messages if the main program refers to any variables or procedures defined in the interface part of the unit. Here is a small example, adapted from one posted recently. The file def.pas has the following unit: UNIT modul; INTERFACE TYPE CARDINAL = 0..65535; LONGBITSET = SET OF 0..63; Var ModS : Integer; PROCEDURE HELLO; IMPLEMENTATION PROCEDURE HELLO; BEGIN WRITELN('HELLO'); END; END. The file test.pas has this test program. program test; USES modul; var i:CARDINAL; c:LONGBITSET; begin ModS := 0; Hello; c:=[1]; i:=1; if (i in c) then writeln('yes'); end. gpc -c def.pas works fine, but gpc test.pas yields the messages d:\tcpip\tmp\ccc00799: Undefined symbol _Mods referenced from text segment d:\tcpip\tmp\ccc00799: Undefined symbol _Hello referenced from text segment d:\tcpip\tmp is my temp directory, and I noticed that running gpc leaves a lot lot of small files called cca000*.exe in the temp directory. Can anyone tell me what I'm doing wrong? Thank you for your time, Jeff Miller Dept of Psychology University of Otago Dunedin, New Zealand miller(a)otago.ac.nz http://psy.otago.ac.nz/miller

2 1

Re: install gpc
by Frank Heckenbach 02 Mar '00

02 Mar '00

Ronald Bianchin wrote: > I've a problem with install gpc. > After unpack gpc-19990118 I've move the files > to /opt/gpc, copy /p/* to gcc/p/* and > execute patch -s -p1 < p/diffs/gcc-2.8.1.diff. You have to unpack the sources of GCC in a matching version before. There are several possible versions as shown in the diff file names. 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

1 0

Re: Cannot produce executable
by Frank Heckenbach 02 Mar '00

02 Mar '00

miller(a)otago.ac.nz wrote: > I have some statistical programs that I would like to release under GPL. > They were originally written in Borland Pascal and Speed Pascal (the latter > is a borland-like pascal for OS/2), and all the code compiles and runs fine > using those two compilers. Now I am trying to get everything to > compile and run under gpc, so that the code will be useful to more > people. It looks like I'll have a lot of questions along the way, > and I'd appreciate any help that can be provided. > > I'm using a version of gpc that I installed as a binary from the file > gpc-19990118_i386-pc-emx0_9d.zip > > I can compile and run little test programs that use no units, > or that use only type definitions from units, but I get "undefined symbol" > messages if the main program refers to any variables or procedures > defined in the interface part of the unit. Try compiling with `--automake' which also compiles units automatically, so don't have to compile them with `-c' before. If this doesn't work (automake is a bit buggy under Dos), try `--autobuild' instead. 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

1 0

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