Gpc January 1998

gpc@gnu.de

23 participants
48 discussions

[Fwd: Re: GPC 971001 problems on redhat linux 4.2]
by Ken Linder (KC7RAD) 22 Jan '98

22 Jan '98

... >> I remember hearing it proposed somewhere that this problem might be a >> result of an old libc, but I haven't heard this confirmed by anybody. I >> think this was proposed in the gpc 1997 mailing list archive, but I never >> heard if it was resolved, and I don't subscribe to the list... > >The conditions under which the error occured had been there, >but I did not get the confirmation that recompiling GPC really >solved the problem. Ken, if you are reading this, did it? > Hi All, Well, I was able to make it work once, quite a while ago (November I think) by recompiling. Having an older libc was not the direct problem. Since then, as life insists, priorities change. I have not been able to do much with the newer releases due to time constraints. HOWEVER, Tom Dye was much more successful than I with the more recent ones. If you are there Tom, have you had success compiling the more recent GPCs and using them? Later, Ken Linder kc7rad(a)vegasnet.net http://www.vegasnet.net/~kc7rad

1 0

Re: Question on Debugging
by Peter Gerwinski 22 Jan '98

22 Jan '98

According to Thomas Tan: > > Okay, can you tell me EXACTLY what you typed in gdb to access the members of > the pointer to a record? Was it like "print ptr->word"? "print *Ptr" - just what you wrote in your first mail. Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

1 0

Re: Question on Debugging
by Peter Gerwinski 22 Jan '98

22 Jan '98

According to Thomas Tan: > I was debugging the following linked list program with a record under gdb, but > when I tried to see what one of the members of the record was, I get "void, > void, void." Do any of you know what's wrong? Strange: This works fine for me :-(with my current development GPC, of course;-). > string10 = packed array[1..10] of char; Perhaps it helps to drop the `packed'? It does not make any difference anyway unless you have specified `--standard-pascal', `--extended-pascal', or similar. Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

2 1

Re: GPC compiler error "file Assign Syntax"
by Peter Gerwinski 22 Jan '98

22 Jan '98

According to Jim Pouliopoulos: > The GPC compiler > sees the assign syntax as an "undeclared identifier". Version 2.0 of GPC has no built-in `Assign' procedure. > [...] Is there a patch for GPC or another > way around this problem? You can * upgrade your GPC to a more recent (beta or alpha) version that understands `Assign', see ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ /alpha/ or * use a self-written `Assign', either that from the GPC Info documentation, chapter `Borland Pascal', or that from the `BPcompat' package at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/ Hope this helps, Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

1 0

Re: GPC 971001 problems on redhat linux 4.2
by Peter Gerwinski 22 Jan '98

22 Jan '98

According to George Brewster: > > I am having trouble with GPC 971001 on my RedHat linux box. It doesn't > compile _anything_, but always gives the following error, regardless > of what I try to compile: > [...] > I did not compile it myself, but used the binary package available. Doing just that might help - and enables you to upgrade to an even more recent alpha version of GPC (see ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/). It is not that difficult to compile GPC on a Linux box. > I remember hearing it proposed somewhere that this problem might be a > result of an old libc, but I haven't heard this confirmed by anybody. I > think this was proposed in the gpc 1997 mailing list archive, but I never > heard if it was resolved, and I don't subscribe to the list... The conditions under which the error occured had been there, but I did not get the confirmation that recompiling GPC really solved the problem. Ken, if you are reading this, did it? Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

1 0

GPC compiler error "file Assign Syntax"
by Jim Pouliopoulos 21 Jan '98

21 Jan '98

I beleive I have come accross a minor problem which may point my code or the GPC compiler itself. This code compiles and runs under my Borland Pascal 7.0 (Win), Borland Pascal 7.0 (Dos) and Turbo Pascal 7.1 (Dos) compilers.� The GPC compiler sees the assign syntax as an "undeclared identifier". I have included a 'Code Snippet' of my unimplemented but functional code and 'Compiler Error Message' (bellow) . Is there a patch for GPC or another way around this problem? � � --------------------------------------------------------------------------------------------- Code Snippet --------------------------------------------------------------------------------------------- {*----------------------------------------------------*} {*�� pTriplEx Vector Sequence Reomover�� *} {*----------------------------------------------------*} {*�� By: Jim Pouliopoulos�� *} {*�� Written for the CSIRO Div. of Animal Production� *} {*�� , Australia�� *} {*----------------------------------------------------*} {*� This program scans a *.seq.1 sequence file for�� *} {*� a sequnce match with the pTriplEx vector sequence *} {*� according to percent homology at both the 5' and� *} {*� 3' ends. It will then excise the vector from the� *} {*� sequence and rewrite the file�� *} {*----------------------------------------------------*} {* Implementation :�� } {�� - Reads File� to Array�� } {�� - Writes Array� to disk (Formatted)�� } {* Not implemented:�� } {�� - Homology Testing�� } {�� - Configuration File Input�� } Program RemVec; {Uses} �� {CRT;} Type �� WrkArray = Array[ 1 .. 1000 ] of Char; �� LetterRange = 'A'..'Z'; �� BaseSet = SET OF LetterRange; �� Vector_String = Packed Array[1..30] of Char;� {Array setup for Vector Sequence} Var �� InChar�� : Char; �� InFile�� : Text; �� OutFile�� : Text; �� DatFile�� : Text; �� TempArray�� : WrkArray; �� i�� : Integer; {counter} �� j�� : Integer; {counter} �� Bases�� : BaseSet; �� LineCtr�� : Integer; {For Counting Chars on line for output} �� pXXX_Seq1�� : Vector_String;� {Sequence #1 for homology searching } �� pXXX_Seq2�� : Vector_String;� {Sequence #2 for homology searching } � � Begin {main} �� {ClrScr;} �� Assign (InFile, 'temp.seq'); �� Reset (InFile); �� Assign (OutFile, 'temp.fix'); �� Rewrite (OutFile); �� Read (InFile, InChar); �� Bases := ['A','G','C','T','N'];�� { N = Wildcard } �� {--------------------------------------------------------------------------} �� {�� Read File Into the Array�� } �� {--------------------------------------------------------------------------} �� While NOT EOF (InFile) do �� Begin {while} �� While (InChar <> Char (10)) and (InChar <> Char(26)) do �� Begin {while} �� Write (InChar); �� Inc (i); �� TempArray[i] := InChar; �� Read (InFile, InChar); �� End; {while} �� Read (Infile, InChar); �� End; {while} �� {---------------------------------------------------------------------------} �� {�� Read Data file into Array�� } �� {---------------------------------------------------------------------------} �� Assign (DatFile, 'g:\temp\test\14-01-98\seq\vector.dat'); �� Reset (DatFile); �� While NOT EOF (DatFile) do �� Begin {while} �� Readln (DatFile); �� Readln (DatFile); �� Readln (DatFile); �� End; {while} �� {---------------------------------------------------------------------------} �� {�� Match the Vector Sequences at the 5' end�� } �� {---------------------------------------------------------------------------} � �� {---------------------------------------------------------------------------} �� {�� Writes Array To Disk with formatted output�� } �� {---------------------------------------------------------------------------} �� i := 1; �� LineCtr := 1; �� While TempArray[i] IN Bases do �� Begin {While} �� Write (OutFile, TempArray[i]); �� inc(i); �� inc(LineCtr); �� If LineCtr = 62 then �� Begin {if} �� Writeln(OutFile); �� LineCtr := 1; �� End; {if} �� End; {While} �� Write (OutFile, TempArray[i]); �� Writeln; �� Close (InFile); �� Close (OutFile); End. {main} --------------------------------------------------------------------------------------------- Compiler Output ---------------------------------------------------------------------------------------------- nugget{jimp}52: gpc -v -o remvec06 remvec06.p --borland-pascal Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/specs gpc version 2.0(2.7.2.1) �/usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/gpc-cpp -lang-pascal -v -noci GNU CPP version 2.0(2.7.2.1) (sparc) #include "..." search starts here: #include <...> search starts here: �/usr/local/include �/usr/local/sparc-sun-sunos4.1/include �/usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/include �/usr/include End of search list. �/usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/gpc1 /usr/tmp/cc026176.i -qus GNU Pascal version 2.0(2.7.2.1) (sparc) compiled by GNU C version 2.7.2.1. remvec06.p: In function `program_Remvec': remvec06.p:46: undeclared identifier `Assign' (first use this function) remvec06.p:46: (Each undeclared identifier is reported only once remvec06.p:46: for each function it appears in.) ------------------------------------------------------------------------------------------- pTriplEx Partial Seqence Data File SEQUENCES TO SEARCH: 1. GAATTC 1 - 100 2. GAAATTC 1 - 100 3. 4. 5. 6. {*----------------------------------------------------*} {* pTriplEx Vector Sequence Reomover *} {*----------------------------------------------------*} {* By: Jim Pouliopoulos *} {* Written for the CSIRO Div. of Animal Production *} {* , Australia *} {*----------------------------------------------------*} {* This program scans a *.seq.1 sequence file for *} {* a sequnce match with the pTriplEx vector sequence *} {* according to percent homology at both the 5' and *} {* 3' ends. It will then excise the vector from the *} {* sequence and rewrite the file *} {*----------------------------------------------------*} {* Implementation : } { - Reads File to Array } { - Writes Array to disk (Formatted) } Program RemVec; {Uses} {CRT;} Type WrkArray = Array[ 1 .. 1000 ] of Char; LetterRange = 'A'..'Z'; BaseSet = SET OF LetterRange; Vector_String = Packed Array[1..30] of Char; {Array setup for Vector Sequence} Var InChar : Char; InFile : Text; OutFile : Text; DatFile : Text; TempArray : WrkArray; i : Integer; {counter} j : Integer; {counter} Bases : BaseSet; LineCtr : Integer; {For Counting Chars on line for output} pXXX_Seq1 : Vector_String; {Sequence #1 for homology searching } pXXX_Seq2 : Vector_String; {Sequence #2 for homology searching } Begin {main} {ClrScr;} Assign (InFile, 'temp.seq'); Reset (InFile); Assign (OutFile, 'temp.fix'); Rewrite (OutFile); Read (InFile, InChar); Bases := ['A','G','C','T','N']; { N = Wildcard } {--------------------------------------------------------------------------} { Read File Into the Array } {--------------------------------------------------------------------------} While NOT EOF (InFile) do Begin {while} While (InChar <> Char (10)) and (InChar <> Char(26)) do Begin {while} Write (InChar); Inc (i); TempArray[i] := InChar; Read (InFile, InChar); End; {while} Read (Infile, InChar); End; {while} {---------------------------------------------------------------------------} { Read Data file into Array } {---------------------------------------------------------------------------} Assign (DatFile, 'g:\temp\test\14-01-98\seq\vector.dat'); Reset (DatFile); While NOT EOF (DatFile) do Begin {while} Readln (DatFile); Readln (DatFile); Readln (DatFile); End; {while} {---------------------------------------------------------------------------} { Match the Vector Sequences at the 5' end } {---------------------------------------------------------------------------} {---------------------------------------------------------------------------} { Writes Array To Disk with formatted output } {---------------------------------------------------------------------------} i := 1; LineCtr := 1; While TempArray[i] IN Bases do Begin {While} Write (OutFile, TempArray[i]); inc(i); inc(LineCtr); If LineCtr = 62 then Begin {if} Writeln(OutFile); LineCtr := 1; End; {if} End; {While} Write (OutFile, TempArray[i]); Writeln; Close (InFile); Close (OutFile); End. {main}

1 0

Re: function pointers
by Peter Gerwinski 21 Jan '98

21 Jan '98

Hallo, Gerd! Hi, everybody! (* Ich antworte mal nur ueber die Liste, damit alle etwas davon haben und ich nicht alles zweimal schreiben muss. :*) > I want to write some examples in gnu pascal but I have not > enough experience in gnu pascal. I want test how powerful the > actual version under Win32 is. So I would use some C - > functions wellknown in the system. You can use either the CygWin or the mingw32 port of GNU tools to Win32 - or you can use DJGPP or EMX in a DOS session. Which one are you using? > But I need a special type. A pointer of a function. How to do > that? Or is that not implemented yet? All versions of GPC I know support pointers to functions; recent beta versions also support references to functions (for BP compatibility). > Something like that: > > type > Pfunc = function( arglist: PVoid ): DWord; This should work (provided that you support the types `PVoid' which is `Pointer' or `^Void' in GPC, and `DWord' is `Word' in GPC) and yields a *reference* to a function (just like BP). If you write Type pFunc = ^Function ( ArgList: Pointer ): Word; you define a pointer type to a function that gets a single untyped pointer as a value parameter and returns an unsigned 32-bit integer. All pointers in GPC are 32-bit "near" pointers. When using function from the Win32-API, you need to declare them `attribute ( stdcall )'. Hope this helps, Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

1 0

Re: GNU Pascal for gcc 2.8.0
by Peter Gerwinski 21 Jan '98

21 Jan '98

According to John Gotts: > Is there a release of GNU Pascal corresponding to gcc 2.8.0 or can I just use > one of the alpha or beta releases? Not yet, but we are working hard on bringing such a thing into existence ASAP. Peter -- Peter Gerwinski, Essen, Germany, free physicist and programmer Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - 1 Oct 1997 PGP key fingerprint: AC 6C 94 45 BE 28 A4 96 0E CC E9 12 47 25 82 75 Fight the SPAM! - http://maps.vix.com/

1 0

Question on Debugging
by Thomas_Tan＠fc.choate.edu 20 Jan '98

20 Jan '98

Hi All, I was debugging the following linked list program with a record under gdb, but when I tried to see what one of the members of the record was, I get "void, void, void." Do any of you know what's wrong? Source File of Program: program Test; type pointer = ^cell; string10 = packed array[1..10] of char; cell = record word : string10; next : pointer; end; var ptr:pointer; begin new(ptr); ptr^.word := "Hello"; writeln(ptr^.word); end. Futile debugging attempt under gdb: (gdb) run Starting program: c:/emacs/my/pointers/test Breakpoint 1, program_Test () at test.pas:14 14 writeln(ptr^.word); (gdb) print *Ptr $1 = {Word = {void, void, void, void, void, void, void, void, void, void, void}, Next = 0x0} (gdb) print Ptr->Word $2 = {void, void, void, void, void, void, void, void, void, void, void} (gdb) The program works fine, writing out "Hello" ------------------------------------------------------ This message sent using the FirstClass SMTP/NNTP Gateway. From: Choate Rosemary Hall 333 Christian St. Wallingford, CT. 06492

1 0

Re: Question to GNU Pascal FAQ list
by Jan-Jaap van der Heijden 19 Jan '98

19 Jan '98

On Mon, 19 Jan 1998, Super-User wrote: > Hello there, > > Is there a way to compile and build gpc-2.0 with gcc-2.7.2.3 > or gcc-2.8.0 instead of the outdated gcc-2.7.2.1? > > Alex Schmidt > LANA/CCNE/UFSM > Santa Maria, RS - Brazil > Compiling gpc-2.0 with any GCC 2.7.2.x is trivial: Just edit Makefile.in in the gpc-2.0 directory, and, near the top, locate the line that says GCCVERSION = 2.7.2.1 Just change the number to 2.7.2.3 (or whatever 2.7.2.x) BTW: I believe the only difference between GCC 2.7.2.1 and 2.7.2.2 or 2.7.2.3 was the added support for Linux/glibc2 As for 2.8: that's a non-trivial exercise. It requires rather big changes to the GPC sources. I know -- I'm busy doing just this :-) Good luck, JanJaap --- With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC1925.

1 0

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 January 1998