- Gpc - gnu.de

Passing strings by value
by Kevin A. Foss 02 Feb '98

02 Feb '98

Hello, Is there something special that needs to be done to pass strings by value? The code below seems to mangle any strings I pass pretty well, when I would assume it would only mangle the local copy in the function: program testfunc(output); var aline : string (20) VALUE 'foo|bar|baz'; function countfields(line : string; axis : char) : integer; var count : integer VALUE 0; begin if length(line) > 0 then count := 1; while index(line, axis) > 0 do begin count := count + 1; line := substr(line, index(line, axis) + 1); end; countfields := count; end; begin writeln(aline); writeln(countfields(aline, '|'), ' field(s)'); writeln(aline); end. Under either 971001, or the 980106 alpha I get the following output: foo|bar|baz 3 field(s) baz which is what I would expect if countfields() accepted 'line' as a VARiable parameter. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

gpc installation problems on Digital Unix
by Gary Narayanan USG 02 Feb '98

02 Feb '98

Ladies and Gentlemen, I installed gpc-2.0 on Digital Unix (Alpha) V4.0A and I saw the following problems. 1. The compiler (I think is gcc 2.7.2.1 compiles this and not /usr/bin/cc) could not compile the file "gpc-decl.c" . The error was in line 2962 TREE_CODE (TREE_VALUE (tail)) = code; The compile said it was not an l-value. I worked around by eliminating the conditional, and typing return NULL_TREE; for both cases. Will this break the compiler functionality? 2. The file "gpc-module.c" has several '#define' statements and not starting at first character of the line. The link editor failed because of this, eg ld: unreolved STORE_SPECIAL 3. The rts/Makefile generated needed some editiong, ie adding a "../" for the gcc path name. Regards Gary Narayanan gsn(a)zk3.dec.com

1 0

Pointer to Method...
by Orlando Llanes 02 Feb '98

02 Feb '98

Ok, this is a tricky one. I need to know how to get a pointer to a method from an object. I've tried a million and one different things, but was not able to do so. Is it even possible? The reason I need this is because I'm toying with the idea of making an object method an interrupt routine. Thanks in advance! 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

1 0

Re: Char type...
by Peter Gerwinski 26 Jan '98

26 Jan '98

According to Orlando Llanes: > Is there a Char type that is guaranteed to be 16-bits from now until > infinity? > Is there a Char type that is guaranteed to be 8-bits from now until > infinity? > Does GPC/DJGPP support the Unicode character type? No(t yet). You can work around this by using 8-bit and 16-bit integers: Type Char8bit = Cardinal ( 8 ); Char16bit = Cardinal ( 16 ); These are guaranteed to be 8/16-bit from now until "infinity" - whenever that will be. ;-) Some "wide char" (Unicode) fragments already exist in GPC. If somebody wants to take part in implementing such things (and others), be welcome. 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: ASMName...
by Peter Gerwinski 26 Jan '98

26 Jan '98

According to Orlando Llanes: > I was wondering if there was any overhead in calling a function > declared in the GPC with the ASMName. There isn't. Nor there is with the `C' directive. > [...] > Would PFunc run faster than CFunc? No. Exactly the same. > The reason I ask is because I remember Peter saying a long time ago > that the C; keyword added overhead to a function and I wonder if the same > is true for the ASMNames keyword. There is no overhead in functions declared with any of these directives. However there *is* overhead in the compiler who has to deal with all those different directives - and in the programmer who has to remember them. ;-) 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

ASMName...
by Orlando Llanes 26 Jan '98

26 Jan '98

I was wondering if there was any overhead in calling a function declared in the GPC with the ASMName. In other words, if I had the following code... ---------- DJGPP: ---------- void cfunc() { // Do something } ---------- GPC: ---------- PROCEDURE CFunc; ASMName 'cfunc'; PROCEDURE PFunc; BEGIN { Do something } END; ...and invoked them as follows... BEGIN CFunc; PFunc; END; Would PFunc run faster than CFunc? The reason I ask is because I remember Peter saying a long time ago that the C; keyword added overhead to a function and I wonder if the same is true for the ASMNames keyword. Thanks in advance! See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Char type...
by Orlando Llanes 26 Jan '98

26 Jan '98

I have a couple of Char type questions: Is there a Char type that is guaranteed to be 16-bits from now until infinity? Is there a Char type that is guaranteed to be 8-bits from now until infinity? Does GPC/DJGPP support the Unicode character type? Thanks in advance! See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: coff file structure
by Peter Gerwinski 26 Jan '98

26 Jan '98

Hi, Omar! Hi, all! According to Omar Abu Al-Haija: > Another question could you please tell me where I can get more > information about coff files , I would like to know more about the > structure of these files and i would like to look on the differance > between coff and MS obj files. Section 17.5 of the DJGPP FAQ list has some pointers that might help you. In particular, they mention a conversion tool: `OBJ2COFF' is available from the Oulu repository, e.g. ftp://x2ftp.oulu.fi/pub/msdos/programming/convert/o2cv10.arj and from DJ Delorie's ftp server, e.g. ftp://ftp.delorie.com/pub/djgpp/contrib/o2cv06.arj. If that tools comes with source (I don't know), you can probably extract anything about COFF from it. > Ps. this time I put subject , hope that could make beter gnu pascal :-) Thanks! :-) Yours, 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

coff file structure
by OHMH＠nets.com.jo 25 Jan '98

25 Jan '98

Thanks Peter Another question could you please tell me where I can get more information about coff files , I would like to know more about the structure of these files and i would like to look on the differance between coff and MS obj files. Ps. this time I put subject , hope that could make beter gnu pascal :-) Yours :omer ___________________________________________ Omer H. Abu Elhaijaa , Ohmh(a)nets.com.jo system programing , Games development pascal / asm , OOP . Flash Team : Games Development Team I beleave that programming is a way of thinking . well is hacking a way of programming ?? __________________________________________ peter(a)agnes.dida.physik.uni-essen.de,Internet writes: >>>According to Omar Abu Al-Haija: >>>>> >>>>> What is the latest Versions from GCC, GPC and where to get them . > >>>>GCC: gcc-2.8.0, available at any GNU mirror. > >>>>GPC: The latest official release is gpc-2.0, available from > >>>> ftp://kampi.hut.fi/jtv/gnu-pascal/ >>>> ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ > >>>>The latest beta is gpc-971001, available from > >>>> ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ > >>>>The latest alpha is gpc-980106, available (in source code only) from > >>>> ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/ > >>>>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: your mail without subject :-(
by Peter Gerwinski 24 Jan '98

24 Jan '98

According to Omar Abu Al-Haija: > > What is the latest Versions from GCC, GPC and where to get them . GCC: gcc-2.8.0, available at any GNU mirror. GPC: The latest official release is gpc-2.0, available from ftp://kampi.hut.fi/jtv/gnu-pascal/ ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ The latest beta is gpc-971001, available from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ The latest alpha is gpc-980106, available (in source code only) from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/ 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

None
by OHMH＠nets.com.jo 24 Jan '98

24 Jan '98

Hi all, What is the latest Versions from GCC, GPC and where to get them . yours : Omer

1 0

[Fwd: Re: GPC 971001 problems on redhat linux 4.2] (fwd)
by Tom Dye 22 Jan '98

22 Jan '98

Hello all, Ken is kind to describe my efforts as successful. Initially, I set out to test the idea that an old libc was to blame, but I soon realized that tinkering with gcc is not trivial and that it was very easy to break things. With regards to the bug mentioned, this is fixed by a patch that Peter posted to the list in November. In my experience, however, the patch exposed other apparent bugs having to do with parameter passing that I was not able to investigate fully. Like Ken, I've had other things come up and haven't been able to get back to 971001. My advice, which is influenced very heavily by the small amount of time I can spend writing Pascal programs and might not be useful for someone with more time and an inclination to get deeply involved with gpc, is to resist the urge to tinker with the alpha releases and wait for a beta release. On the other hand, it would be interesting to know why 971001 gave so many of us problems. Tom Thomas S. Dye, Ph.D. Home: 813 16th Avenue, Honolulu, Hawaii 96816. Voice (808) 734-2087. Work: International Archaeological Research Institute, Inc., 949 McCully St., Suite 5, Honolulu, Hawaii 96826. Voice (808) 946-2548; Fax 943-0716. ---------- Forwarded message ---------- Date: Thu, 22 Jan 1998 09:30:01 -0800 From: "Ken Linder (KC7RAD)" <kc7rad(a)vegasnet.net> To: gpc(a)hut.fi Subject: [Fwd: Re: GPC 971001 problems on redhat linux 4.2] ... >> 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

[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

GPC 971001 problems on redhat linux 4.2
by George Brewster 19 Jan '98

19 Jan '98

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: /tmp/cca00834.i:1: numeric constant with no digits /tmp/cca00834.i:1: numeric constant with no digits /tmp/cca00834.i:1: invalid #line /tmp/cca00834.i:2: warning: missing program header /tmp/cca00834.i:2: parse error at null character the output of gpc 'trig.pas -v' is: Reading specs from /usr/lib/gcc-lib/i586-unknown-linux/2.7.2.1/specs gpc version 971001(2.7.2.1) /usr/lib/gcc-lib/i586-unknown-linux/2.7.2.1/gpc-cpp -lang-pascal -v -nocharescape -undef -D__GNUC__=2 -D__GPC__=2 -D__GNUC_MINOR__=7 -D__ELF__ -Dunix -Di386 -Dlinux -D__ELF__ -D__unix__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux -Asystem(unix) -Asystem(posix) -Acpu(i386) -Amachine(i386) -D__i486__ trig.pas /tmp/cca00815.i GNU CPP version 971001(2.7.2.1) (i386 Linux/ELF) #include "..." search starts here: #include <...> search starts here: /usr/local/include /usr/i586-unknown-linux/include /usr/lib/gcc-lib/i586-unknown-linux/2.7.2.1/include /usr/include End of search list. /usr/lib/gcc-lib/i586-unknown-linux/2.7.2.1/gpc1 /tmp/cca00815.i -quiet -dumpbase trig.pas -version -famtmpfile=trig.gpc -o /tmp/cca00815.s GNU Pascal version 971001(2.7.2.1) (i386 Linux/ELF) compiled by GNU C version 2.7.2.1. /tmp/cca00815.i:1: numeric constant with no digits /tmp/cca00815.i:1: numeric constant with no digits /tmp/cca00815.i:1: invalid #line /tmp/cca00815.i:2: warning: missing program header /tmp/cca00815.i:2: parse error at null character what else can I say?? I did not compile it myself, but used the binary package available. I use a 486 gpc v2.0 worked, but not with the -g flag (that's a whole different problem) I have libc version 5.3.12 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... Currently, I have switched back to gpc 2.0, which seems to work fine... I appreciate any help, George Brewster

1 0

function pointers
by Gerd Balzuweit 19 Jan '98

19 Jan '98

Hi, 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. But I need a special type. A pointer of a function. How to do that? Or is that not implemented yet? Something like that: type Pfunc = function( arglist: PVoid ): DWord; May be anyone can help? -- Gerd Balzuweit iXOS Anwendungs-Software GmbH Leipzig E-mail: mailto:gerd.balzuweit@ixos-leipzig.de www : http://www.ixos-leipzig.de/ Phone : +49 341 48503-0 Fax : +49 341 48503-99

1 0

RE: <Autofrwd>NEWS: gcc-2.8.0 released?
by Berend de Boer 19 Jan '98

19 Jan '98

On Saturday, January 17, 1998 4:00 PM, Peter Gerwinski [SMTP:peter@agnes.dida.physik.uni-essen.de] wrote: > Of course, this plan implies that we must upgrade from gcc-2.7.2.x to > gcc-2.8.0 ASAP. I think it is reasonable to continue support for > gcc-2.7.2.x as long as this works without too much effort. The problem is: I use gpc on FreeBSD machines which are on gcc 2.7.2.x. I don't want to upgrade these machines to a gcc different than used to compile the other sources (just to avoid problems). This means I cannot compile gpc sources unless you still support gcc or supply a binary each time. So try to support gcc 2.7.x as long as possible. Groetjes, Berend.

1 0

Re: Interfacing with C!
by Peter Gerwinski 19 Jan '98

19 Jan '98

According to Bernhard Tschirren: > > Are there any ways of calling procedures written in GPC from GCC. Now, > heres the clinch: The pascal source is object oriented!! That's not a real problem. :-) > Now, I have a pointer to the object (in C). The object contains both data There is an implicit `vmt' field, a pointer, in each object. Apart from that, it is just an ordinary `record' (or `struct' for that matter). > and ONLY virtual methods (That makes things simpler!) So, I could easily > get the address of the function that I want to call. Non-virtual methods are even easier: They are called `Myobject_Mymethod' internally and differ from ordinary procedures only by the additional implicit `Self' parameter. To call a virtual method from C you must dig it out: The `vmt' field in the object points to a structure which contains * the size of the object (a `size_type' variable in C), * its negative (another `size_type' variable), * and pointers to the methods in the same order as they appeared in the declaration of the object. To initialize an object, it is not enough to call the constructor, but you must explicitly assign the correct value to the `vmt' field, i.e. let it point to the correct VMT structure. (GPC does this "inline" when a constructor is called.) When you call a method, don't forget to pass the implicit `self' parameter. > So, the question is: How does GPC handle virtual methods? Looking at > numerous assembly listing I have deduced the following: > > GPC passes a pointer to the parent object Why "parent"??? No - that's a pointer to the object itself! > (@Self) NOT on the stack, but > in ECX. Is that true, and how is it implemented on other platforms? This is just by chance and depends on the optimization level. If you declare the `self' parameter as an ordinary (pointer) parameter, it should work just fine because this is exactly what GPC does internally. Good luck, 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

GNU Pascal for gcc 2.8.0
by John Gotts 19 Jan '98

19 Jan '98

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? John -- John GOTTS <jgotts(a)engin.umich.edu> http://www-personal.engin.umich.edu/~jgotts

1 0

Re: Compability C++ - GPC
by Peter Gerwinski 18 Jan '98

18 Jan '98

According to Hans Ecke: > > Would it be possible to just translate the header files to units and > simple compile the program? [...] Unfortunately not. I thought about planning this for the future, but this would mean that GPC would have to copy multiple inheritance with all its ugly implications from C++; some discussion in this list convinced me that it will be much better to implement "Interfaces" (like in Java) into GPC. > Do the mechanisms of polymorphie, inheritance etc work between a library > written in C++ and an unit written in GPC? They don't. To work around this, you can write a C-style interface that lives without objects for the C++ library and then make a Pascal Unit use these inter- face functions to implement Pascal objects: C++: class foo // the thing we want to use { void bar ( int baz ); } C: /* This non-OOP interface we must write because OOP information * does not survive transport through an `.o' or an `.a' file. */ void foo_bar ( struct class_foo *self, int baz ) { /* call the object's method */ } Pascal: (* This unit implements a `FooObj' that implements a Pascal *) (* OOP interface for the C++ `foo' class. The implementation *) (* uses a non-OOP function written in C. *) Type FooPtr = ^Foo; FooObj = object; cppClass: Pointer; (* holds a pointer to the C++ instance *) Procedure Bar ( Baz: Integer ); end (* FooObj *); Procedure C_foo_bar ( Self: Pointer; Baz: Integer ); AsmName 'foo_bar'; Procedure FooObj.Bar ( Baz: Integer ); begin (* FooObj.Bar *) C_foo_bar ( cppClass, Baz ); end (* FooObj.Bar *); BTW, what about writing Pascal libraries that provide the same functionality? I am myself working on such a thing (BO5); the EFLIB library (http://ftp.sunet.se/EFLIB/) is another approach (I do not know whether it supports X11), and I am sure that many readers of this list have their own libraries waiting to be ported to GNU Pascal. Greetings, 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

Interfacing with C!
by Bernhard Tschirren 18 Jan '98

18 Jan '98

Are there any ways of calling procedures written in GPC from GCC. Now, heres the clinch: The pascal source is object oriented!! Now, I have a pointer to the object (in C). The object contains both data and ONLY virtual methods (That makes things simpler!) So, I could easily get the address of the function that I want to call. So, the question is: How does GPC handle virtual methods? Looking at numerous assembly listing I have deduced the following: GPC passes a pointer to the parent object (@Self) NOT on the stack, but in ECX. Is that true, and how is it implemented on other platforms? Thanks Bernie ________________________ e-mail: bernie(a)icenet.com.au | _) | | ptschirrenb(a)curtin.edu.au |___)ernhard |_|schirren tschirre(a)cs.curtin.edu.au www: www.geocities.com/CollegePark/Quad/8070/

1 0

Compability C++ - GPC
by Hans Ecke 18 Jan '98

18 Jan '98

Hi all! This message asks about writing bindings for a library which is written in C++. I have to write an X-Windows application. I have never done this, but have read about various widgets. The most exciting commentares I read about were about QT from TrollTech. Its written in C++ (I love objects) and there are also quite a bit examples on the net. Of course I would love to write the app in GPC, too. Now my question : Would it be possible to just translate the header files to units and simple compile the program? I.e. something like $> cat test_app.pas programm test_app; uses qtmain; ...body end. $> gpc test_app.pas -lqt $> test_app Do the mechanisms of polymorphie, inheritance etc work between a library written in C++ and an unit written in GPC? I consider this a topic almost as critic as the writing of bindings for a library written in plain C. Hans

1 0

NEWS: gcc-2.8.0 released?
by Peter Gerwinski 18 Jan '98

18 Jan '98

Hi, everybody! I just found this in gnu.misc.discuss (*not* in gnu.announce/gnu.gcc.announc): > From: Paul Eggert <eggert(a)twinsun.com> > Subject: gcc 2.8.0, libstdc++ 2.8.0 released > Newsgroups: gnu.misc.discuss > > ftp://prep.ai.mit.edu/pub/gnu/gcc-2.8.0.tar.gz > ftp://prep.ai.mit.edu/pub/gnu/libstdc++-2.8.0.tar.gz > > More details and an official announcement will appear soon. > Please send bug reports for GNU C to `bug-gcc(a)prep.ai.mit.edu'. > Please send bug reports for GNU C++ to `bug-g++(a)prep.ai.mit.edu'. Even if this was not the official release of gcc-2.8.0, I suggest to let gpc-2.1 follow as soon as possible even if not all bugs are fixed. My current development GPC passes all PVS conformance tests for ISO-7185 Standard Pascal level 0 and (NEW!) level 1 but two minor ones. My idea is to fix these, make the final beta and release gpc-2.1 even if there are some remaining known bugs. (An incomplete list of those bugs that have prevented me from releasing gpc-2.1 up to now follows below.) Of course, this plan implies that we must upgrade from gcc-2.7.2.x to gcc-2.8.0 ASAP. I think it is reasonable to continue support for gcc-2.7.2.x as long as this works without too much effort. Any comments? 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/ 8< ---- remaining bugs in current GPC --------------------------------------- The two ISO-7185-related bugs I want to fix before releaseing gpc-2.1: * GPC barfs on type checking with Boolean values in `case' statements. * Nested packed conformant arrays do not yet work in all cases. Major bugs I am planning to postpone (unless, of course, I have an idea how to fix them without too much effort;-)-: * The "AutoMake" mechanism needs a complete rewrite. It's too slow and does not always decide correctly whether something must be recompiled or not. * GPC still fails some (few) ISO conformance tests when compiled with optimization on the DEC Alpha. * `Seek' and `SeekRead' etc. do not yet work in all situations (frank95b.pas). * Comparisons of integers of different size sometimes fail (frank118.pas). * String `Var' parameters accept constant values (frank123.pas). * "Procedure Foo ( x: String )" has in fact a `Var' parameter (frank125.pas). * `New' on pointers to discriminated strings doesn't work (frank128.pas). * There is no `--uses="System"' option for full BP compatibility yet. * The `--field-width' switch does not handle `LongInt's etc. * Inside `New', all methods of an object become visible and may cause name clashes.

3 3

Source code released for PROTOTYPE 5.1;
by Johan Larsson 16 Jan '98

16 Jan '98

Hi Everyone, Though prototype 5.1 is an early working model with an incompatible design, I have decided to release source code together with that release. The source code can be downloaded at: http://ftp.sunet.se/EFLIB/Download/ 1,2 MB kernel source code. You are not adviced to use this release of EFLIB in developing since prototype 6 is entirely redesigner. However, you are encouraged to participate in discussions regarding the design chosen in EFLIB prototype 5.1 toward more knowledge about good and bad object-oriented designs. The 6th prototype is scheduled for April 30, 1998 and will include a cross-platform GUI as well as Linux support. Contact me if you want to join the team or want to help a little! Best Regards, Johan Larsson URL: http://www.acc.umu.se/~jola/ MAIL: jola(a)acc.umu.se Also, REMEMBER to check out EFLIB, the free object-oriented framework for EVERY Pascal programmer, at http://ftp.sunet.se/EFLIB/. Simply SOPHISTICATED!

1 0

Near pointers...
by Orlando Llanes 16 Jan '98

16 Jan '98

I came across some DJGPP code and tried it in Pascal and it works! 3 lines and you can set pointers directly and use them without crashing. Works great especially for graphics since you won't need to set the segment registers :) The C code was written by Emmanuel Lagare with help by Brennan Underwood. Here's the GPC code: TYPE TDWord = Cardinal(32); TWord = Cardinal(16); PByte = ^TByte; TByte = Cardinal(8); TDPMIRegs = RECORD EDI, ESI, EBP, Rsvd, EBX, EDX, ECX, EAX : TDWord; Flags, ES, DS, FS, GS, IP, CS, SP, SS : TWord; END; VAR Foo : PByte; DJBase : ASMName '__djgpp_base_address' TDWord; PROCEDURE djgpp_nearptr_enable; ASMName '__djgpp_nearptr_enable'; PROCEDURE djgpp_nearptr_disable; ASMName '__djgpp_nearptr_disable'; PROCEDURE SimRMI( aInt : TWord; VAR aRegs : TDPMIRegs ); ASMName '__dpmi_int'; VAR Regs : TDPMIRegs; PROCEDURE SetMode( aMode : TWord ); BEGIN Regs.EAX := aMode; SimRMI( $10, Regs ); END; BEGIN djgpp_nearptr_enable; TDWord( Foo ) := $A0000 + (-DJBase); SetMode( $13 ); asm( 'movl $0x0F0F0F0F, %eax' ); asm( 'movl %0, %%edi' : '=m' (Duh) ); asm( 'addl $4000, %edi' ); asm( 'movl %eax, (%edi)' ); ReadLn; SetMode( 3 ); djgpp_nearptr_disable; END. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 1

Re: gpc on a floppy
by Peter Gerwinski 16 Jan '98

16 Jan '98

Hi! According to Paolo M. Pumilia: > Hi pascal-experts, > I would like to put the essential files of gpc for dos > on a single floppy disk. Is it possible? Which files to pick up? For what system? On a generic UNIX system, type `make pascal.bindist' after having compiled GPC. This will create a binary distribution `.tar.gz' archive with all the essential files of GPC. On DOS or OS/2 with DJGPP or EMX, the binary distribution of the Pascal compiler itself fits on a single floppy. However, you also need the DJGPP or EMX development environment. If you already have that installed - fine, then the GPC binary distribution fits your needs. Otherwise you will need 6-10 floppies to carry all important development tools. (See the GPC FAQ list and the DJGPP FAQ list for information which parts are needed for Pascal.) 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

gpc on a floppy
by Paolo M. Pumilia 15 Jan '98

15 Jan '98

Hi pascal-experts, I would like to put the essential files of gpc for dos on a single floppy disk. Is it possible? Which files to pick up? Thank you Paolo Pumilia Since i did not subscribe to the list, please reply also to pumilia(a)mbox.est.it -- --- CSTC - -- --- CSTC -

1 0

Just had to say so...
by Orlando Llanes 15 Jan '98

15 Jan '98

I LOVE THE GPC COMPILER!!!! I know some of you already know this, but I just have to say that GPC is an extremely powerful compiler!!!! :) Keep up the great work GPC Team!!! See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: gpc 2.0 Failing
by Peter Gerwinski 14 Jan '98

14 Jan '98

Hi! According to Phillip Bruce: > [...] > do gcc -c -o $i -g -O -D`basename $i .o` -I../../gcc-2.7.2.3 > -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3/config -I. ./rts-zmath.c;\ > done > gcc: Internal compiler error: program cc1 got fatal signal 6 This is a problem with GCC, not with GPC. To work around this, try to compile `libgpc.a' without debugging information and/or without optimization: make CFLAGS="-O" libgpc.a make CFLAGS="" libgpc.a Good luck, 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

GCC 2.8.0 has been released
by Richard Kenner 14 Jan '98

14 Jan '98

gcc-2.8.0.tar.gz, 8,477,747 bytes, is now available on prep.ai.mit.edu and all the usual mirror sites. [snip snip] New features for Intel x86 family: Add scheduling parameters for Pentium and Pentium Pro. Support stabs on Solaris-x86. Intel x86 processors running the SCO OpenServer 5 family. Intel x86 processors running DG/UX. Intel x86 using Cygwin32 or Mingw32 on Windows 95 and Windows NT. ^^^^^^^ Yeah! :-) -------------------------------------- > My current development GPC passes all PVS conformance tests for ISO-7185 > Standard Pascal level 0 and (NEW!) level 1 but two minor ones. My idea > is to fix these, make the final beta and release gpc-2.1 even if there > are some remaining known bugs. (An incomplete list of those bugs that > have prevented me from releasing gpc-2.1 up to now follows below.) > > Of course, this plan implies that we must upgrade from gcc-2.7.2.x to > gcc-2.8.0 ASAP. I think it is reasonable to continue support for > gcc-2.7.2.x as long as this works without too much effort. > > Any comments? > 1. We did GPC ports based on cygwin32/b18 sources and EGCS before; but failed to maintain them (and never publicly announced them). 2. In an attempt to build win32 GPC's, I tried two routes: extract win32 support from gcc-2.8 betas, plug that in gcc-2.7.2.x sources and build GPC based on that, and port GPC to pre-gcc-2.8. I never fixed the segfaults in the 2.7.2.x based win32 compilers at higher optimization levels, so they were never made public. I have not done (pre)-2.8 based GPC's for the last six months or so. I am willing to do the 2.8 port once more, but only if we do maintain it this time. I am finishing up a new series of mingw32 GCC-2.8 based tools as we speak; the www pages will be updated this weekend. By now I'm pretty familiar with GCC2 sources; and if we are cautious, this GPC could run on top of EGCS just as well. Greetings, 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

gpc 2.0 Failing
by Phillip Bruce 14 Jan '98

14 Jan '98

Hi, I like to know is anyone else getting the same problem I am. I'm running gcc-2.7.2.3 on Solaris 2.6 on PC platform. rts-bind.c for i in p_ARCTAN.o p_SQRT.o p_LN.o p_EXP.o p_SIN.o p_COS.o p_POW.o p_EXPON.o; \ do gcc -c -o $i -g -O -D`basename $i .o` -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3/config -I. ./rts-math.c;\ done touch math-stamp for i in z_ARCTAN.o z_SQRT.o z_LN.o z_EXP.o z_SIN.o z_COS.o z_POW.o z_EXPON.o p_POLAR.o p_ARG.o; \ do gcc -c -o $i -g -O -D`basename $i .o` -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3/config -I. ./rts-zmath.c;\ done gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 make[1]: *** [zmath-stamp] Error 1 make[1]: Leaving directory `/usr/local/gpc-2.0/rts' make: *** [rts/libgpc.a] Error 2 -- ************************************************************************** **** Phillip B. Bruce This is who I am! ***** **** http://www.jps.net/pbbruce My Web Site ***** **** pbbruce(a)jps.net My personal Email Address ***** **************************************************************************

1 0

Re: Frac/Int problem - patch for GPC
by Peter Gerwinski 12 Jan '98

12 Jan '98

According to Kevin A. Foss: > I was trying the latest alpha and trying to get the new > int/frac functions to work, however the first piece of code I tried > caused gpc to dump core :( Sorry - my fault! A patch to the latest alpha GPC which fixes this problem (and another one related to operators defined in Units) follows below. 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/ 8< -------------------------------------------------------------------- Changes for gpc from gpc-980106. Changes in files you can reconstruct with Bison, etags, makeinfo, and TeX have been omitted. Some of these files are updated just by building the compiler. You can update the rest of these files by executing this command make TAGS info dvi -f Makefile.in in the directory of GPC sources, provided the necessary tools (etags, makeinfo, TeX and texi2dvi) are installed. To apply these diffs, go to the directory gpc-980106 and use the command patch -p1 feeding it the following diffs as input. Then rename the directory to gpc. diff -r -U3 -N -x *.o -x *.log -x *.old -x Makefile -x config.cache -x config.status -x gpc-version.c -x *parse.c -x *parse.h -x gpc-gperf.h -x TAGS -x gpc.?? -x gpc.??s -x gpc.aux -x g?c.info* -x gpc*.html -x *.dvi -x *.toc -x *.html -x INSTALL -x FPKvsGNU -x specs -x core -x version -x rts-version.c -x rts-config.h -x gpc -x gpc-cpp -x gpc1 -x libgpc.a -x config.h -x b[i,c]-* -x hconfig.h -x tconfig.h -x insn-*.[c,h] -x options.h -x specs.h -x stamp* -x tm.h -x gen* -x stage[1-4] -x include -x ?++* -x cc1 -x cccp -x cpp -x enquire -x float.h* -x gfloat.h* -x multilib.h -x lib*.a -x underscore.c -x xg?c -x xlimits.h -x site.exp -x *.bak -x *.swp -x gcc-2.7.2.2.patch -x *.aux -x *.cp -x *.cps -x *.ky -x *.kys -x *.gdt -x *.gpr -x *.gpi -x gpc-config.h -x *.orig gpc-980106/p/ChangeLog gpc/p/ChangeLog --- gpc-980106/p/ChangeLog Tue Jan 6 20:50:55 1998 +++ gpc/p/ChangeLog Mon Jan 12 14:17:50 1998 @@ -1,3 +1,14 @@ +Mon 12 Jan 1998 12:15 Peter Gerwinski <peter.gerwinski(a)uni-essen.de> + + * rts.c: rts[], build_rts_call(): case ucsd_INT, bp_FRAC: + make `int' and `frac' use Frank's RTS functions rather than + converting the argument to `Integer' and back. + +Sat 10 Jan 1998 12:15 Peter Gerwinski <peter.gerwinski(a)uni-essen.de> + + * module.c: load_tree(): case TYPE_DECL: remember the name of + the type in the *_TYPE node. + Tue 6 Jan 1998 20:00:00 Peter Gerwinski <peter.gerwinski(a)uni-essen.de> * rts.c: rts-read(): pass correct string capacity for diff -r -U3 -N -x *.o -x *.log -x *.old -x Makefile -x config.cache -x config.status -x gpc-version.c -x *parse.c -x *parse.h -x gpc-gperf.h -x TAGS -x gpc.?? -x gpc.??s -x gpc.aux -x g?c.info* -x gpc*.html -x *.dvi -x *.toc -x *.html -x INSTALL -x FPKvsGNU -x specs -x core -x version -x rts-version.c -x rts-config.h -x gpc -x gpc-cpp -x gpc1 -x libgpc.a -x config.h -x b[i,c]-* -x hconfig.h -x tconfig.h -x insn-*.[c,h] -x options.h -x specs.h -x stamp* -x tm.h -x gen* -x stage[1-4] -x include -x ?++* -x cc1 -x cccp -x cpp -x enquire -x float.h* -x gfloat.h* -x multilib.h -x lib*.a -x underscore.c -x xg?c -x xlimits.h -x site.exp -x *.bak -x *.swp -x gcc-2.7.2.2.patch -x *.aux -x *.cp -x *.cps -x *.ky -x *.kys -x *.gdt -x *.gpr -x *.gpi -x gpc-config.h -x *.orig gpc-980106/p/module.c gpc/p/module.c --- gpc-980106/p/module.c Tue Jan 6 20:44:36 1998 +++ gpc/p/module.c Sat Jan 10 12:04:38 1998 @@ -1881,6 +1881,8 @@ #endif DECL_NAME (t) = load_tree (s, depth + 1); TREE_TYPE (t) = load_tree (s, depth + 1); + if (code == TYPE_DECL) + TYPE_NAME (TREE_TYPE (t)) = DECL_NAME (t); DECL_INITIAL (t) = load_tree (s, depth + 1); DECL_CONTEXT (t) = current_function_decl; break; diff -r -U3 -N -x *.o -x *.log -x *.old -x Makefile -x config.cache -x config.status -x gpc-version.c -x *parse.c -x *parse.h -x gpc-gperf.h -x TAGS -x gpc.?? -x gpc.??s -x gpc.aux -x g?c.info* -x gpc*.html -x *.dvi -x *.toc -x *.html -x INSTALL -x FPKvsGNU -x specs -x core -x version -x rts-version.c -x rts-config.h -x gpc -x gpc-cpp -x gpc1 -x libgpc.a -x config.h -x b[i,c]-* -x hconfig.h -x tconfig.h -x insn-*.[c,h] -x options.h -x specs.h -x stamp* -x tm.h -x gen* -x stage[1-4] -x include -x ?++* -x cc1 -x cccp -x cpp -x enquire -x float.h* -x gfloat.h* -x multilib.h -x lib*.a -x underscore.c -x xg?c -x xlimits.h -x site.exp -x *.bak -x *.swp -x gcc-2.7.2.2.patch -x *.aux -x *.cp -x *.cps -x *.ky -x *.kys -x *.gdt -x *.gpr -x *.gpi -x gpc-config.h -x *.orig gpc-980106/p/rts.c gpc/p/rts.c --- gpc-980106/p/rts.c Tue Jan 6 20:44:36 1998 +++ gpc/p/rts.c Mon Jan 12 12:08:06 1998 @@ -82,6 +82,9 @@ { pp_SIN, "sinl", NULL_RTX, NULL_TREE}, { pp_SQRT, "_pp_sqrt", NULL_RTX, NULL_TREE}, + { ucsd_INT, "_p_int", NULL_RTX, NULL_TREE}, + { bp_FRAC, "_p_frac", NULL_RTX, NULL_TREE}, + { p_DISPOSE,"_p_dispose", NULL_RTX, NULL_TREE}, { p_EOF, "_p_eof", NULL_RTX, NULL_TREE}, { p_EOLN, "_p_eoln", NULL_RTX, NULL_TREE}, @@ -1754,67 +1757,6 @@ break; } - case ucsd_INT: - { - /* Calculate the integer part of a real number by converting it - * to the largest possible integer type and back. - * - * If the number is too big to fit in an integer and has a - * precision not bigger than that of the integer, we know that - * it does not have a fractional part. - * - * If the number is too big to fit in an integer but has a - * precision not than that of the integer, we are hosed. - * Maybe we should do a loop then ... - * - * This code is suboptimal anyway, since at least the i386 has - * a single instruction which calculates `int'. @@@@ - */ - INLINE_RTS_LENGTH ("int", 1); - if (code == REAL_TYPE) - { - if (TYPE_PRECISION (type) <= TYPE_PRECISION (long_long_integer_type_node)) - { - tree abs_val = build_unary_op (ABS_EXPR, val, 0); - tree condition = build_binary_op (GT_EXPR, abs_val, - convert (type, TYPE_MAX_VALUE (long_long_integer_type_node)), 0); - retval = convert (type, convert (long_long_integer_type_node, val)); - retval = build (COND_EXPR, type, condition, - val, retval); - } - else - abort (); - } - else - errstr = "argument to `int' must be of real type"; - break; - } - - case bp_FRAC: - { - /* frac ( foo ) = foo - int ( foo ). - */ - INLINE_RTS_LENGTH ("frac", 1); - if (code == REAL_TYPE) - { - if (TYPE_PRECISION (type) <= TYPE_PRECISION (long_long_integer_type_node)) - { - tree abs_val = build_unary_op (ABS_EXPR, val, 0); - tree condition = build_binary_op (GT_EXPR, abs_val, - convert (type, TYPE_MAX_VALUE (long_long_integer_type_node)), 0); - retval = convert (type, convert (long_long_integer_type_node, val)); - retval = build (COND_EXPR, type, condition, - val, retval); - } - else - abort (); - retval = build_pascal_binary_op (MINUS_EXPR, val, retval); - } - else - errstr = "argument to `frac' must be of real type"; - break; - } - case p_SUCC: { /* rts_inline */ @@ -3027,6 +2969,14 @@ rval = double_type_node; fpar = ptype_double; } + break; + } + + case ucsd_INT: + case bp_FRAC: + { + rval = long_double_type_node; + fpar = ptype_long_double; break; }

1 0

Re: gpc linker problems
by Peter Gerwinski 11 Jan '98

11 Jan '98

Hello! According to Rod Evans: > If anyone can help with this, would you please email me direct since I'm > not subscribed to the mailing list. > > The problem: general linker problems in gpc 2.0. > eg. > gpc -v -o fibonacci fibonacci.pas > Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/specs > gcc version 2.0(2.7.2.1) > [...] This looks as if your `gcc.c' were not patched for GPC but the original GCC version. Thus your `gpc' does not recognize the extension `.pas' as Pascal source but takes it as linker input. > 1) The first 'make' had a VPATH problem which caused it to fail for target > gpc1; following the FAQ, I removed those '.o' files from the gcc object > directory. I then got a clean make. Maybe still something went wrong with this - at least for the `gpc' driver program, not for the actual compiler `gpc1'. To solve the problem, recompile `gcc.c' to `gcc.o' and watch whether the `-DGPC' switch is given. For a general solution to the VPATH problem it might help to upgrade to a recent beta version of GPC; see ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ 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

Frac/Int problem
by Kevin A. Foss 09 Jan '98

09 Jan '98

Hello again, I was trying the latest alpha and trying to get the new int/frac functions to work, however the first piece of code I tried caused gpc to dump core :( program test(output); begin writeln(frac(3.14)); end. As does running frac on a declared const: const r = 3.14; begin writeln(frac(r)); end. It works fine if I run frac across a variable real tho: var r : real VALUE 3.14; begin writeln(frac(r)); end. Similiar results with int(). -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Problem compiling 2.0 of gpc
by Phillip Bruce 09 Jan '98

09 Jan '98

Hi, I need to know if anybody is experiencing the same thing here. I have a gcc compiler 2.7.2.3 and the compilation for the gpc-2.0 aborted with a signal 6. Simply the cc1 just aborted. Below is what really happen. cd rts && make RTSFLAGS="" make[1]: Entering directory `/usr/local/gpc-2.0/rts' for i in z_ARCTAN.o z_SQRT.o z_LN.o z_EXP.o z_SIN.o z_COS.o z_POW.o z_EXPON.o p_POLAR.o p_ARG.o; \ do gcc -c -o $i -g -O -D`basename $i .o` -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3 -I../../gcc-2.7.2.3/config -I. ./rts-zmath.c;\ done gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 gcc: Internal compiler error: program cc1 got fatal signal 6 make[1]: *** [zmath-stamp] Error 1 make[1]: Leaving directory `/usr/local/gpc-2.0/rts' make: *** [rts/libgpc.a] Error 2 I would appreciate any help with this. Thanks. -- ************************************************************************** **** Phillip B. Bruce This is who I am! ***** **** http://www.jps.net/pbbruce My Web Site ***** **** pbbruce(a)jps.net My personal Email Address ****** **************************************************************************

2 1

Some patches uploaded ...
by Peter Gerwinski 07 Jan '98

07 Jan '98

Hi, folks! For those who are curious how the next beta will look like I just uploaded two files gpc-971216-971229.diff.gz gpc-971229-980106.diff.gz to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/. Thanks to Frank and Kevin. (-: No further comments on the changes; see ChangeLog. ;-) Have fun, 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 2.0 on linux redhat 5.0
by yan wong 07 Jan '98

07 Jan '98

has anyone got this to work. I keep on getting problems with the debugger (gnu) ld. After installing the linux (ELF) binaries, It complains that it can't find crtbegin.o or crtend.o if I move these from the directory /usr/lib/gcc-lib/i386-redhat-linux/2.7.2.3 where they reside in the standard distribution, gpc produces an executable which immediately segfaults. What should I be doing here? Can I recompile gpc for a newer version of ld (if that is the problem)? trying to compile gcc 2.7.2.1 with the new ld halts with errors too. I've spent a fair bit of time fiddling around, so if anyone has some hints, I would be grateful if they could e-mail me back. thanks a lot yan wong

2 1

Re: GRAPH unit
by Peter Gerwinski 05 Jan '98

05 Jan '98

Hi, Fabrice! Hi, all! According to Fabrice Laussy: > > I do need the graph.tpu file (if it is actually a file... I even don't know > what the hell it can be). > > 1) I know it's not the topic of the mailing list... Really I apologize. If you mean *Borland's* `graph.tpu', this is indeed off-topic and forbidden by law. But since GNU Pascal has its own Graph-compatible unit, be welcome if you mean that! (-: > 2) I know it's quite not very very legal, please the list, say you can't, > that it's forbiden by law and ethic, and please contact me by email. GPC's "Graph" Unit is called "BGI2GRX". It is distributed as a `.pas' file according to a combination of the GNU Library General Public License (GNU-LGPL; for the underlying GRX library) and some other conditions specified in the file. It is perfectly legal to distribute it. Be welcome to download it from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib > I am > working with gpc on code for university's purpose, and when the code is > near its end, I translate some part of code to make it run with MS > standard. It's holiday, I would like to finish job at home... So I ask! What's the problem? Just install GPC at home! It works perfectly on the PC under DOS (including Windows 95), OS/2, or Linux. 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

GRAPH unit
by Fabrice Laussy 05 Jan '98

05 Jan '98

Hi, I do need the graph.tpu file (if it is actually a file... I even don't know what the hell it can be). 1) I know it's not the topic of the mailing list... Really I apologize. 2) I know it's quite not very very legal, please the list, say you can't, that it's forbiden by law and ethic, and please contact me by email. I am working with gpc on code for university's purpose, and when the code is near its end, I translate some part of code to make it run with MS standard. It's holiday, I would like to finish job at home... So I ask! 3) gnu, gnu, gnu. Thx.

1 0

gpc linker problems
by Rod Evans 05 Jan '98

05 Jan '98

If anyone can help with this, would you please email me direct since I'm not subscribed to the mailing list. The problem: general linker problems in gpc 2.0. eg. gpc -v -o fibonacci fibonacci.pas Reading specs from /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/specs gcc version 2.0(2.7.2.1) /usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1/ld -e start -dc -dp -o fibonacci /lib/crt0.o -L/usr/local/lib/gcc-lib/sparc-sun-sunos4.1/2.7.2.1 -L/usr/local/lib fibonacci.pas -lgcc -lc -lgcc collect2: ld returned 4 exit status ld: fibonacci.pas: bad magic number The system: gpc 2.0 on Sunos 4.1.3 (gcc 2.7.2.1 already installed and working OK). Some background: 1) The first 'make' had a VPATH problem which caused it to fail for target gpc1; following the FAQ, I removed those '.o' files from the gcc object directory. I then got a clean make. 2) copying 'collect2' from the gcc directory to the gpc1 directory (suggested by the FAQ) did not solve the problem. Can anyone help with this or at least tell me how I can get more info on it? Thanks, Rod. |===========================================================================| | Rod Evans Divisional Manager CSIRO Division of Animal Production | | (Networks/Computing) Locked Bag 1, Delivery Centre | | Blacktown, NSW 2148 | | Internet: AUSTRALIA | | R.Evans(a)prospect.anprod.csiro.au Tel: (61) (02) 9840 2700 | | Fax: 9840 2940 | |===========================================================================|

1 0

GCC on the Mac...
by Orlando Llanes 04 Jan '98

04 Jan '98

I just did a search on DJ Delorie's site through the mail archives, and I was searching about Mac stuff. What I found out was that there's a GCC for the Macintosh, but the catch is that it's for the MkLinux OS. With that in mind, since GCC is available on that platform and as long as I code for Linux, could GPC generate code for MkLinux? If there's not presently a binary for it (which I doubt, but I haven't checked), I'll compile one provided that my Mac supports MkLinux. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 1

Re: ANNOUNCEMENT : TP Lex/Yacc 4.0
by Berend de Boer 02 Jan '98

02 Jan '98

Peter Gerwinski wrote: >> I have uploaded TP Lex/Yacc 4.0 to (see above). Its a Version from October >> Maybe somebody has time enough to port it to GPC... >I agree that this would be a good thing. And here is Berend, finally reading the last two months of messages from this list... I've tried to port Lex/Yacc to gpc for a few years (I ported Lex to Extended Pascal already), but since gpc didn't have initialized arrays I didn't get very far (and I didn't want to rewrite much). GPC has it now, and I'm slowly compiling module by module, but because of bugs I encounter I have to wait for new versions, so it doesn't proceed very fast, but at least surely now :-) Groetjes, Berend. (-:

1 0

Re: your mail without subject :-(
by Peter Gerwinski 31 Dec '97

31 Dec '97

According to hantschr(a)hantsch.co.at: Username: [rainer] > Use the above line in your e-Mail body to reach me in our company. > Subject: Latest GPC version > [...] > Please, be so kind and leave me > detailled instructions (detailled enough > to be followed by an absolute > newcomer to Linux) about which file(s) > to download (with Netscape for > Windows, because my Linux host is not > online !!), Point your browser to the following URL: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/gpc-971001.i586-linux.tar.gz Download that file and store it under some name that survives transport through a DOS filesystem. Save it as `/tmp/gpc-971001.i586-linux.tar.gz'. > where to store them to, how > to do the update (with YaST?)... In order to reduce interference mit YaST, *uninstall* GPC from YaST before you install gpc-971001. To install gpc-971001, do the following as root: cd / tar xvzf /tmp/gpc-971001.i586-linux.tar.gz This will install some files in /usr/bin, some in /usr/lib/gcc-lib, and some in /usr/info. These are the correct places for Linux; on other UNIX-like systems these would be /usr/local/*. After that, you can remove `/tmp/gpc-971001.i586-linux.tar.gz' or move it to some other place where you keep distribution archives. (I have a directory `/usr/local/src/archive/' for such purposes.) > Thanks in forward, (* You mean: in advance. ;*) Guten Rutsch, 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

None
by hantschr＠hantsch.co.at 30 Dec '97

30 Dec '97

--note----------------------------------------------------------------- Username: [rainer] Use the above line in your e-Mail body to reach me in our company. You may use [rainer] at the beginning of the SUBJECT line (with higher priority) instead. -- This will allow us "Automatic Mail Forwarding". Our human "postmaster" may be reached with [rainer]. DO NOT USE OTHER FILE-ENCODING THAN UUENCODE, IT CANNOT BE PROCESSED!!! --note----------------------------------------------------------------- Received: from Hantsch-Message_Server by hantsch.co.at with WordPerfect_Office; Tue, 30 Dec 1997 14:11:01 +0100 Message-Id: <s4a900f5.001(a)hantsch.co.at> X-Mailer: WordPerfect Office 4.0 Date: Tue, 30 Dec 1997 14:10:40 +0100 From: hantschr(a)hantsch.co.at To: gpc(a)hut.fi Subject: Latest GPC version Item Type: Note ** High Priority ** Hello to all! I already received some suggestions for GPC, so I experienced that my GPC is relatively old. I was told to take the latest Beta version instead, because it is very similar to BP7... So I was visiting the ~GNU-PASCAL FTP site to find the files, but I could not find out which is the right one and how to do the update (I am a bloody beginner with Linux). I use currently: SuSE Linux 5.1 (Dec. 97) I have one DOS (mounted to /dosc) partition and one Linux Partition. All Linux directories are standard setup. Please, be so kind and leave me detailled instructions (detailled enough to be followed by an absolute newcomer to Linux) about which file(s) to download (with Netscape for Windows, because my Linux host is not online !!), where to store them to, how to do the update (with YaST?)... Thanks in forward, Rainer Hantsch ---------------------------------------------------------------------- | Office address: | You may reach us by: | |--------------------------|-------------------------------------------| | ING. RAINER HANTSCH | Phone : +43 1 7988538 0 | | Khunngasse 21/1 | Fax : +43 1 7988538 18 | | A-1030 Wien/Vienna | BBS : +43 1 7988538 17 | | | e-Mail: hantschr(a)hantsch.co.at | | *** A U S T R I A *** | www : http://members.eunet.at/hantschr/ | ----------------------------------------------------------------------

1 0

Re: identifiers in module declarations
by Peter Gerwinski 30 Dec '97

30 Dec '97

According to Kevin A. Foss: > > Thanks for uploading this, it appears to fix a lot of stuff that I have > been waiting to try. However I had to do a lot of patching to the > makefiles to get it to compile under EMX -- it looks like the RTS had a > lot of changes :) . Hmm ... I was sure that I had included your EMX patches into `config/emx' - including `dostage1.cmd' which was in `..' (the GCC source directory). > I'm afraid that in all of the patching I did, I may have missed > something, or else read(ln) has been seriously broken [...] Indeed. (The second one.) Thanks for the test program; a patch to fix it follows below. (I usually only use strings of variable length; that's why I didn't find the error myself.) (BTW, does a port of the `patch' program to EMX exist? If so, we could replace the patched GCC source files in `config/emx' by a diff - just like we do for other platforms.) Greetings, 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/ 8< --------------------------------------------------------------------------- Changes for gpc from gpc-971229. Changes in files you can reconstruct with Bison, etags, makeinfo, and TeX have been omitted. Some of these files are updated just by building the compiler. You can update the rest of these files by executing this command make TAGS info dvi -f Makefile.in in the directory of GPC sources, provided the necessary tools (etags, makeinfo, TeX and texi2dvi) are installed. To apply these diffs, go to the directory gpc-971229 and use the command patch -p1 feeding it the following diffs as input. Then rename the directory to gpc. diff -r -U3 -N -x *.o -x *.log -x *.old -x Makefile -x config.cache -x config.status -x gpc-version.c -x *parse.c -x *parse.h -x gpc-gperf.h -x TAGS -x gpc.?? -x gpc.??s -x gpc.aux -x g?c.info* -x gpc*.html -x *.dvi -x *.toc -x *.html -x INSTALL -x FPKvsGNU -x specs -x core -x version -x rts-version.c -x rts-config.h -x gpc -x gpc-cpp -x gpc1 -x libgpc.a -x config.h -x b[i,c]-* -x hconfig.h -x tconfig.h -x insn-*.[c,h] -x options.h -x specs.h -x stamp* -x tm.h -x gen* -x stage[1-4] -x include -x ?++* -x cc1 -x cccp -x cpp -x enquire -x float.h* -x gfloat.h* -x multilib.h -x lib*.a -x underscore.c -x xg?c -x xlimits.h -x site.exp -x *.bak -x *.swp -x gcc-2.7.2.2.patch -x *.aux -x *.cp -x *.cps -x *.ky -x *.kys -x *.gdt -x *.gpr -x *.gpi -x gpc-config.h -x *.orig gpc-971229/p/rts.c gpc/p/rts.c --- gpc-971229/p/rts.c Fri Dec 5 18:37:52 1997 +++ gpc/p/rts.c Tue Dec 30 13:13:13 1997 @@ -525,46 +525,48 @@ } break; - case RECORD_TYPE: /* String schema */ - case ARRAY_TYPE: /* fixed length strings */ - switch (is_string_type (p, 1)) { - case 0: - error ("only packed arrays of char may be read from `text' files"); - continue; - case 1: - break; - case 2: - /* @@@ Should generate a runtime check for conformant arrays. - * (low index has to be 1 for arrays to be valid string-type) - */ - /* for now, just read them */ - break; - default: - abort (); - } + case RECORD_TYPE: /* String schema. */ + case ARRAY_TYPE: /* Fixed length string. */ + switch (is_string_type (p, 1)) + { + case 0: + error ("only packed arrays of char may be read from `text' files"); + continue; + case 1: + break; + case 2: + /* @@@ Should generate a runtime check for conformant arrays + * (low index has to be 1 for arrays to be valid string-type). + * + * For now, just read them. + */ + break; + default: + abort (); + } if (PEDANTIC (E_O_PASCAL)) pedwarn ("ISO Pascal does not allow reading of strings from textfiles"); - /* run time system expects another argument - before max length: a pointer to int where - it stores the current length of the string - - If that is null_pointer, the string is a fixed length string. - - This needs to be an lvalue if not NULL_TREE. - */ if (is_variable_string_type (TREE_TYPE (p))) - string_curlen = build_unary_op (ADDR_EXPR, PASCAL_STRING_LENGTH (p), 0); + { + what = P_STRING; + /* The run time system expects another argument + * before max length: a pointer to int where + * it stores the current length of the string. + * + * This needs to be an lvalue. + */ + string_curlen = build_unary_op (ADDR_EXPR, PASCAL_STRING_LENGTH (p), 0); + } else - string_curlen = null_pointer_node; + what = P_FIXED_STRING; /* The char store */ p = PASCAL_STRING_VALUE (p); /* String max length */ string_length = pascal_array_type_nelts (TREE_TYPE (p)); - what = P_STRING; break; default : @@ -591,11 +593,11 @@ build_unary_op (ADDR_EXPR, p, 0))); allow_packed_var_parameters--; if (what == P_STRING) - arglist = chainon (arglist, - tree_cons (NULL_TREE, - string_curlen, - build_tree_list (NULL_TREE, - string_length))); + arglist = chainon (arglist, + build_tree_list (NULL_TREE, string_curlen)); + + arglist = chainon (arglist, + build_tree_list (NULL_TREE, string_length)); /* Mark that we have assigned a value to this variable. */

1 0

Re: identifiers in module declarations
by Kevin A. Foss 30 Dec '97

30 Dec '97

On Mon, 29 Dec 1997 16:41:10 +0100 (MET), Peter Gerwinski wrote: >I am uploading something more recent than gpc-971001 (gpc-971216 - don't >get confused when it produces a wrong version number with the `-v' switch) >to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/. This will >fix this problem and some others. Sorry for not posting more comments >on this "version" of GPC - see ChangeLog for what has happend since >gpc-971001. :-I Thanks for uploading this, it appears to fix a lot of stuff that I have been waiting to try. However I had to do a lot of patching to the makefiles to get it to compile under EMX -- it looks like the RTS had a lot of changes :) . I'm afraid that in all of the patching I did, I may have missed something, or else read(ln) has been seriously broken as I can't even use simple code like: program test(input, output); type string5 = packed array[1..5] of char; var inname : string5; begin readln(inname); writeln(inname); end. It exits with "?Gpc: Incorrect reading of string" no matter what I enter. So I'm stumped as to what might be the problem. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: ASM question. Wait! Don't shoot!...
by Orlando Llanes 29 Dec '97

29 Dec '97

> I forgot to tell something. I don't know how to acceed video memory > ... > I don't know if it's a good way but it seems to work. Thanks! It's not accessing it using a base address, but it's the closest thing :) I'm not partial to any particular segment register so gs is good enough for me so long as I don't have to reload it every time :) If anybody knows how to access the VGA segment using only a base address I'd still appreciate the tip. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 1

Re: ASM question. Wait! Don't shoot!...
by Frank Heckenbach 29 Dec '97

29 Dec '97

Orlando Llanes wrote: > Does anyone have any working code to access the VGA segment using only a > base address? I'm looking to see if it's possible to access the VGA > segment without having to load a segment register under GPC's asm(). Which platform, please? I suppose DJGPP or EMX... Don't they use memory mapping so that each process has its own address space? In this case it might help to call some memory mapping function, and then you get the linear base address you want. E.g. for DJGPP: __djgpp_map_physical_memory in dpmi.h (NOTE: I haven't done anything like this myself, I've just grepped the DJGPP includes, so I don't know if this is the correct thing...) -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

2 1

Re: ASM question. Wait! Don't shoot!...
by Peter Gerwinski 29 Dec '97

29 Dec '97

According to Orlando Llanes: > I know this has been asked over and over again, but I promise I've tried > what I've been told and have even read FAQs. Did you also look at the GPC assembler documentation? ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/gpcasm.zip > Does anyone have any working code to access the VGA segment using only a > base address? I'm looking to see if it's possible to access the VGA > segment without having to load a segment register under GPC's asm(). There is no chance to access the VGA memory without - explicitly or implicitly - loading a segment (selector) register. The best thing you can do - if possible; I didn't check - is to let GPC move the value $A000 to the segment register rather than doing that yourself with an explicit `movw %ax, %gs' (or whatever) asm statement. Consult the "gpcasm" manual (URL above) for how to do such things. (* Please note that that segment register will *not* get "clobbered" by the asm statement. If you use several `asm's in sequence that all want to have $A000 in `%gs', an optimizing GPC will move it only once. *) > I tried the following code > > ... > asm( 'movl $0xA0000, %edi' ); > asm( 'addl $1000, %edi' ); > asm( 'movb $15, (%edi)' ); > ... No chance without a selector prefix. asm ( 'moveb %0, gs:(%1)' : (* no output *) : 'r' ( <source byte> ), 'r' ( <destination offset> ) ); > and even the following code: > > VGASel := SegToSelector( $A000 ); > GetSegmentBase( VGASel, VGABase ); > ... > asm( 'movl %0, %%edi' : '=m' (VGABase) ); > asm( 'addl $1000, %edi' ); > asm( 'movb $15, (%edi)' ); > ... This cannot work unless you have a selector for memory address 0 somewhere - which I don't see. Good luck, 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: Slightly Off Topic ... Video Modes in Linux
by Peter Gerwinski 29 Dec '97

29 Dec '97

According to hantschr(a)hantsch.co.at: Username: [rainer] > Use the above line in your e-Mail body to reach me in our company. (* Rainer, I fished the subject out of your e-mail's body. It would be nice if you could tell your mailer to put the subject line where it belongs. thanks. *) > Subject: Slightly Off Topic ... Video Modes in Linux Indeed: This is *completely* off-topic. Rather than answering this, I should work on GPC. Sorry to everybody! > My Linux system uses a originalk TSENG ET > 4000 W32i Graphics Card. > Entering the line vga=ask into the startup file of > LILO, I get a long list of possible text modes, also > mode 100x40. [...] LILO tells me that it is mode 0b, but > entering vga=0b, vga=9x0b, vga=12 as > replacement for vga=all does not change the > mode. My LILO shows me a list of 16-bit mode numbers, for instance 0x0f05 is 80x30. When I place "vga = 0x0f05" in my `/etc/lilo.conf' and run `lilo', I get 80x30 after the next reboot. > I encountered that YaST is changing back all > modifications of X. I entered automatic startup of > xearth, etc., but if I add some X applications, > YAST recreates the configuration file. Is there a > special filename which is executed during startup > of X which contains my personal and/or > system wide settings for X? Doesn't the YaST documentation or the configuration file generated by YaST say something about that? What I mean is something equivalent to `/etc/profile.local' which is - in contrast to `/etc/profile' - not touched by YaST. But the correct place to ask is S.u.S.E. <support(a)suse.de> who does the support for YaST and their Linux distribution. 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: identifiers in module declarations
by Peter Gerwinski 29 Dec '97

29 Dec '97

According to Kevin A. Foss: > > I have the following module which doesn't work with gpc971001 > (a known problem, see below): > [...] I see, it's high time for gpc-2.1 - or at least the next beta. I am uploading something more recent than gpc-971001 (gpc-971216 - don't get confused when it produces a wrong version number with the `-v' switch) to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/. This will fix this problem and some others. Sorry for not posting more comments on this "version" of GPC - see ChangeLog for what has happend since gpc-971001. :-I Greetings, and thanks for your patience, 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

None
by hantschr＠hantsch.co.at 29 Dec '97

29 Dec '97

--note----------------------------------------------------------------- Username: [rainer] Use the above line in your e-Mail body to reach me in our company. You may use [rainer] at the beginning of the SUBJECT line (with higher priority) instead. -- This will allow us "Automatic Mail Forwarding". Our human "postmaster" may be reached with [rainer]. DO NOT USE OTHER FILE-ENCODING THAN UUENCODE, IT CANNOT BE PROCESSED!!! --note----------------------------------------------------------------- Received: from Hantsch-Message_Server by hantsch.co.at with WordPerfect_Office; Mon, 29 Dec 1997 08:01:56 +0100 Message-Id: <s4a758f3.001(a)hantsch.co.at> X-Mailer: WordPerfect Office 4.0 Date: Mon, 29 Dec 1997 08:01:36 +0100 From: hantschr(a)hantsch.co.at To: gpc(a)hut.fi Subject: Slightly Off Topic ... Video Modes in Linux Item Type: Note Hello, everybody! Problem #1: ~~~~~~~~~~~ My Linux system uses a originalk TSENG ET 4000 W32i Graphics Card. Entering the line vga=ask into the startup file of LILO, I get a long list of possible text modes, also mode 100x40. This mode is very readable and therefore I want to make it my default text font. Where do I enter the settings to make them permanent? LILO tells me that it is mode 0b, but entering vga=0b, vga=9x0b, vga=12 as replacement for vga=all does not change the mode. Problem #2: ~~~~~~~~~~~ I encountered that YaST is changing back all modifications of X. I entered automatic startup of xearth, etc., but if I add some X applications, YAST recreates the configuration file. Is there a special filename which is executed during startup of X which contains my personal and/or system wide settings for X? Please, leave me*some instructions what I must do. Thanks, in forward, Rainer Hantsch ---------------------------------------------------------------------- | Office address: | You may reach us by: | |--------------------------|-------------------------------------------| | ING. RAINER HANTSCH | Phone : +43 1 7988538 0 | | Khunngasse 21/1 | Fax : +43 1 7988538 18 | | A-1030 Wien/Vienna | BBS : +43 1 7988538 17 | | | e-Mail: hantschr(a)hantsch.co.at | | *** A U S T R I A *** | www : http://members.eunet.at/hantschr/ | ----------------------------------------------------------------------

1 0

identifiers in module declarations
by Kevin A. Foss 28 Dec '97

28 Dec '97

Hello, I have the following module which doesn't work with gpc971001 (a known problem, see below): Module foo Interface; Export foo = (test1); procedure test1(addr : integer; float : real); end. { Interface } Module foo Implementation; procedure test1; begin writeln(addr); writeln(float); end; end. with unpatched 971001 I get: coltrane:~> gpc -c nsl.pas nsl.pas: In function `Test1': nsl.pas:14: undeclared identifier `Addr' (first use this function) [...] nsl.pas:15: undeclared identifier `Float' (first use this function) [...] Then I applied the patch of Nov. 10 for module.c posted by Peter to the list -- which I thought would fix this problem, and I get: coltrane:~> gpc -c nsl.pas nsl.pas:15: undeclared identifier `Float' (first use this function) [....] Is there another patch that needs to be applied to make both identifiers available to the implementation? -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

ASM question. Wait! Don't shoot!...
by Orlando Llanes 27 Dec '97

27 Dec '97

I know this has been asked over and over again, but I promise I've tried what I've been told and have even read FAQs. Does anyone have any working code to access the VGA segment using only a base address? I'm looking to see if it's possible to access the VGA segment without having to load a segment register under GPC's asm(). I tried the following code ... asm( 'movl $0xA0000, %edi' ); asm( 'addl $1000, %edi' ); asm( 'movb $15, (%edi)' ); ... and even the following code: VGASel := SegToSelector( $A000 ); GetSegmentBase( VGASel, VGABase ); ... asm( 'movl %0, %%edi' : '=m' (VGABase) ); asm( 'addl $1000, %edi' ); asm( 'movb $15, (%edi)' ); ... Neither of the two crashes. What's supposed to happen is a white pixel is supposed to show up at about (8,12) but nothing happens. I even got the AT&T Syntax right (instruction source, destination). Thanks in advance! See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: gdb & tty
by Peter Gerwinski 27 Dec '97

27 Dec '97

According to Laussy Fabrice: > It seems GPC does not allow proper debugging with GDB under Emacs when > output are redirected to any tty device. Does this only occur when debugging or does it also happen when you just redirect output to the GPC-compiled program? > It seems that the bug is due to emacs or gdb itself, because the error > is that what I enter is not given properly to the program debugged, but > this problem I have never encountered when debugging C code under > similar circumstances, so I think GPC may be responsible for something! I know that there are problems with the debugging informations produced by GPC. If you could post a short example of a Pascal program that behaves incorrect in the debugger, it would help us to fix the problem. Greetings, 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

gdb & tty
by Laussy Fabrice 26 Dec '97

26 Dec '97

Hi all, It seems GPC does not allow proper debugging with GDB under Emacs when output are redirected to any tty device. It seems that the bug is due to emacs or gdb itself, because the error is that what I enter is not given properly to the program debugged, but this problem I have never encountered when debugging C code under similar circumstances, so I think GPC may be responsible for something! Of course one debugging Pascal code with gdb deserve such desagrement, just it may be of interest for some of you. If one of the list has a trick to make it work... Oh yeah... also merry Xmas and happy new year to all of you. FPL

1 0

Re: GPC documentation (was without subject)
by Peter Gerwinski 24 Dec '97

24 Dec '97

Hallo, Rainer! Hello, everybody! Username: [rainer] > Use the above line in your e-Mail body to reach me in our company. [...] (I am doing so.) > A few days ago I started to play around with Linux > -- and it is very exciting. I also played around with > Sun Solaris x86 before, but there is no Pascal > compiler available Now there is: GNU Pascal runs there, too. :-) > -- and I do not want to change to "C". (* Nor do I; that's why I started my work on GPC. *) > Therefore I was very surprised to find GPC > on my SuSE 5.1 distribution, but my happyness > was only of a short time... The GPC that comes with S.u.S.E. 5.0 has not been compiled correctly, so some important features do not work there. I recommend to download a working binary distribution from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/binary/ - or, even better, upgrade to the more recent version gpc-971001: ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/binary/. > DOES ANYBODY HAVE SOMETHING LIKE A > REFERENCE MANUAL? YES! IT COMES WITH THE COMPILER! As Orlando already pointed out, try `info -f gpc'. That documentation is somehow outdated, but we are constantly working on improving it. (Currently, the best "documentation" for GPC is this mailing list.) > I experienced that my GPC v2.0 does not > understand the simplest TurboPascal > commands like Assign(). While gpc-2.0 doesn't have a built-in `Assign', gpc-971001 does. To get more compatibility to BP, please download the `BPcompat' compatibility Units from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/. You might also want to use an integrated development environment like BP's one. If so, please download RHIDE for Linux from http://www.tu-chemnitz.de/~sho/rho/rhide.html. > Best wishes for Christmas, Danke, ebenso! :-) 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: Platform questions...
by Peter Gerwinski 24 Dec '97

24 Dec '97

According to Orlando Llanes: > I'm curious about Cygnus Win32 and EMX. What I'm curious about is what > does GPC compile using Win32 or EMX (for OS/2)? Does it compile a console > application? Or could they make calls to the Win32 or OS/2 system API? GPC (like GCC) under EMX by default produces console applications. Producing applications for the OS/2 presentation manager is straightforward if you know the OS/2 API. With some effort you can also produce 16-bit Windows applications with EMX. One interesting thing concerning the `.exe' files produced by EMX is that they run as DOS applications *as well as* as OS/2 applications. :) Greetings, 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

None
by hantschr＠hantsch.co.at 23 Dec '97

23 Dec '97

--note----------------------------------------------------------------- Username: [rainer] Use the above line in your e-Mail body to reach me in our company. You may use [rainer] at the beginning of the SUBJECT line (with higher priority) instead. -- This will allow us "Automatic Mail Forwarding". Our human "postmaster" may be reached with [rainer]. DO NOT USE OTHER FILE-ENCODING THAN UUENCODE, IT CANNOT BE PROCESSED!!! --note----------------------------------------------------------------- Received: from Hantsch-Message_Server by hantsch.co.at with WordPerfect_Office; Tue, 23 Dec 1997 09:36:15 +0100 Message-Id: <s49f860f.001(a)hantsch.co.at> X-Mailer: WordPerfect Office 4.0 Date: Tue, 23 Dec 1997 09:35:20 +0100 From: hantschr(a)hantsch.co.at To: gpc(a)hut.fi Subject: Looking for "GPC-Manual" Item Type: Note Hello! A few days ago I started to play around with Linux -- and it is very exciting. I also played around with Sun Solaris x86 before, but there is no Pascal compiler available -- and I do not want to change to "C". Therefore I was very surprised to find GPC on my SuSE 5.1 distribution, but my happyness was only of a short time... DOES ANYBODY HAVE SOMETHING LIKE A REFERENCE MANUAL? I experienced that my GPC v2.0 does not understand the simplest TurboPascal commands like Assign(). Maybe, I do something wrong, but because of a missing documentation I do not know the reason. Please, point me to a location, where I get the required information. Best wishes for Christmas, Rainer Hantsch ---------------------------------------------------------------------- | Office address: | You may reach us by: | |--------------------------|-------------------------------------------| | ING. RAINER HANTSCH | Phone : +43 1 7988538 0 | | Khunngasse 21/1 | Fax : +43 1 7988538 18 | | A-1030 Wien/Vienna | BBS : +43 1 7988538 17 | | | e-Mail: hantschr(a)hantsch.co.at | | *** A U S T R I A *** | www : http://members.eunet.at/hantschr/ | ----------------------------------------------------------------------

2 1

Platform questions...
by Orlando Llanes 23 Dec '97

23 Dec '97

I'm curious about Cygnus Win32 and EMX. What I'm curious about is what does GPC compile using Win32 or EMX (for OS/2)? Does it compile a console application? Or could they make calls to the Win32 or OS/2 system API? Thanks in advance! Happy Christmas and Merry New Year! =B) See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 1

Request_for_quotation
by gpc＠hut.fi 22 Dec '97

22 Dec '97

Att. Sales / Export Department Re: Request for quotation A RFQ for products which, to the best of our knowledge are similar to those offered by you ,was placed with us by one of our clients. We are a world wide sourcing firm and we are paid by our clients to find them suitable suppliers . To you ,our service is totally free of charge !!! The information we will get from you will not only be immediately sent to this particular client but also to all other clients looking for similar products . To define and advise us the products you are interested to export and/or to get more information about us and our FREE SERVICE , please use our Internet interface at: http://www.thebol.com Best Regards theBOL - Purchasing Department

2 1

Re: Regular Expression
by Peter Gerwinski 22 Dec '97

22 Dec '97

Hallo, Hans! Hello, everybody! Hans, I like your ideas, but I have some problems to imagine how this should work in praxis. According to Hans Ecke: > * announce such an archive in the Homepage > * make a directory, where new items go inside. > They will stay there some time (2 weeks?) if after that time, nobody has > protested against them, they would be moved to the archive. Normally, nobody will take the time and download a file just for checking whether it is worth to be in such an archive. If it is the default to move it to the archive, I expect it to overflow relatively soon. I think that such an archive cannot work reasonably for a longer time without continuous human interaction. A "moderator" who feels responsible for it would be needed here. (Interested?;-) > This could be done rather easily. How? Are you thinking of some auxiliary program invoked by a `cron' script? > To stay in time, the files can be put in meantime to > the archive via symbolic links. You mean that there should be a readable `incoming' directory for the archive where files stay for some "evaluation time"; after that they can become members of the archive, and in the meantime they are symlinked into the archive? Schoene Gruesse, 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: unit init
by Peter Gerwinski 22 Dec '97

22 Dec '97

Hi! > it seems this little unit hangs GPC > > unit test; > interface > implementation > var pro:array[0..1] of ^procedure; > k:integer; > {*******************************} > procedure MC; > begin > writeln(' Merry Christmas ! '); > end; > {*******************************} > begin > for k:=0 to 1 do pro[k]:=@MC; > end. > > Maybe there are syntax errors , but I think it shouldn't > crash the compiler This bug is fixed meanwhile, but the result is not yet published. (There are no syntax errors in your unit, BTW.) > It works only if I use the option --fBorland , This is fixed, too. > I use the compiler which is in GPC-9710.zip, I see: It's high time for the release of gpc-2.1. > Bye and Merry Christmas everybody ! Thank you - as well! > PS : I hope you can understand my english... (Not a single word. ;-) 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: Last value in enum...
by Peter Gerwinski 21 Dec '97

21 Dec '97

According to Orlando Llanes: > How do you get the highest value from an enumerated type? Delphi defines > functions First() which gets the first value, and Last() which gets the > last value, which I believe is equivalent to High() and Low() in Borland > Pascal. Is there an equivalent function in GPC? There isn't, but since this does not break anything else (and is not too complicated), this is a good candidate to be implemented in the future. 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 I/O & errors
by heckenb＠helena.hut.fi 20 Dec '97

20 Dec '97

Kevin A. Foss wrote: > >Well... but I think in most cases it would be more appropriate to return > >false for directories (I hadn't thought about this problem at all) because > >I'd usually call this functions before trying to open the file for reading > >or updating. > > Yeah, that's true -- I was thinking of using a check for file > existance to check and see if the filename was available for creating a > file with a unique filename. But your use is more common and good > code would check to see if the bind fails anyway. True, this seems like another use for the functions (and I just saw that I was using it in this way sometimes... ;-). OTOH, there can be other obstacles to creating a file, such as write-protected directories / file systems / volumes, so one would have to check the Bind, and perhaps the Rewrite as well. > >So, I think it would be better to return false if the binding fails. > > Yes I do too, now that I considered the actual usage of the function. > :) Just for the record, with the built-in Assign function, Exists could be shortened a little: function Exists(FileName:String):Boolean; var b:BindingType; f:Text; begin Assign(f,FileName); b:=Binding(f); Exists:=b.Bound and b.Existing; Unbind(f) end; Chief, perhaps it would be worth putting such a function into one of the BP compatibility units. Though BP does not have a built-in Exists, it could be hard for many ex-BP users (like me ;-) to figure out the bindings... -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Last value in enum...
by Orlando Llanes 19 Dec '97

19 Dec '97

How do you get the highest value from an enumerated type? Delphi defines functions First() which gets the first value, and Last() which gets the last value, which I believe is equivalent to High() and Low() in Borland Pascal. Is there an equivalent function in GPC? See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: gpc I/O & errors
by Kevin A. Foss 19 Dec '97

19 Dec '97

On Fri, 19 Dec 1997 22:00:21 +0100, Frank Heckenbach wrote: >Kevin A. Foss wrote: >> The problem (as noted in the >> comments) is that if the bind fails it thinks the file exists, which is >> a bit of a kludge. However I couldn't get around the problem that >> appeared when a user gives a name that is used by a directory. Frank's >> code using stat() correctly reports true for directories. > >Well... but I think in most cases it would be more appropriate to return >false for directories (I hadn't thought about this problem at all) because >I'd usually call this functions before trying to open the file for reading >or updating. Yeah, that's true -- I was thinking of using a check for file existance to check and see if the filename was available for creating a file with a unique filename. But your use is more common and good code would check to see if the bind fails anyway. >So, I think it would be better to return false if the binding fails. Yes I do too, now that I considered the actual usage of the function. :) -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: gpc I/O & errors
by heckenb＠helena.hut.fi 19 Dec '97

19 Dec '97

Kevin A. Foss wrote: > The advantage is that you don't have to deal with any C-isms at all and > it should work on any GPC platform without worrying about the > underlying stat() implementation. Yes, that's better, thanks. I didn't know about these binding flags. > The problem (as noted in the > comments) is that if the bind fails it thinks the file exists, which is > a bit of a kludge. However I couldn't get around the problem that > appeared when a user gives a name that is used by a directory. Frank's > code using stat() correctly reports true for directories. Well... but I think in most cases it would be more appropriate to return false for directories (I hadn't thought about this problem at all) because I'd usually call this functions before trying to open the file for reading or updating. So, I think it would be better to return false if the binding fails. (As currently implemented, the binding will fail if the given file name is a directory, or the file doesn't exist and the directory isn't writable.) -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Re: gpc I/O & errors
by Peter Gerwinski 19 Dec '97

19 Dec '97

According to Frank Heckenbach: > Laurentiu COCEA wrote: > > 2. Where do I get a list of compile-time and run-time errors? > > I fear such a list doesn't exist -- there's much work to do about the > documentation... :-( > > If you get the source distribution of GPC, you can find a *non-complete* list > of run-time errors in rts/rts-error.c. I don't know if the compile-time errors > are listed somewhere Such a list does not exist, but in my current GPC source (the `p' directory), grep -w "error (" *.c ../*.c | less grep -w "pedwarn (" *.c ../*.c | less grep -w "warning (" *.c ../*.c | less yields 887 error, 516 pedwarn, and 461 warning messages. ("Pedwarn" means that the warning turns into an error message in `--pedantic-errors' mode.) If you want to help us to produce a list with the most important compile-time and run-time messages, be welcome. Greetings, 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 I/O & errors
by Kevin A. Foss 18 Dec '97

18 Dec '97

On Thu, 18 Dec 1997 20:19:16 +0100, Frank Heckenbach wrote: >Laurentiu COCEA wrote: > >> 1. How do I suspend I/O error messages in order to detect the >> presence/absence of a file? In Turbo Pascal, one does this as follows: >> >> {$I-} >> reset(file); >> {$I+} >> if IOResult <> 0 then... >Sorry, there's no {$I+-} directive in GPC yet, but some work has already >been done towards implementing it. > >As for checking if a file exists, there are other ways, e.g. searching the >directory, or (at least under Un*x systems, I don't know if also under Dos) >stat(2)ing the file. The following works on my Linux system, so it should >be alright for you: It is also possible to use gpc's built in extension to file binding that checks if a file exists, e.g. something like: program pas(input, output); var a : string(200); function exists(filename: string) : Boolean; { Checks if a file exists. It returns positive if b.existing is TRUE or if the bind failed. The bind will fail for example if the name given is actually a directory name. } var b : BindingType; f : bindable text; begin unbind(f); b := binding(f); b.name := filename; bind(f, b); b := binding(f); if b.bound then exists := b.existing else exists := TRUE; unbind(f); end; begin write('Enter a file name: '); readln(a); if exists(a) then writeln(a, ' exists.') else writeln(a, ' doesn''t exist.'); end. The advantage is that you don't have to deal with any C-isms at all and it should work on any GPC platform without worrying about the underlying stat() implementation. The problem (as noted in the comments) is that if the bind fails it thinks the file exists, which is a bit of a kludge. However I couldn't get around the problem that appeared when a user gives a name that is used by a directory. Frank's code using stat() correctly reports true for directories. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: gpc I/O & errors
by heckenb＠helena.hut.fi 18 Dec '97

18 Dec '97

Laurentiu COCEA wrote: > 1. How do I suspend I/O error messages in order to detect the > presence/absence of a file? In Turbo Pascal, one does this as follows: > > {$I-} > reset(file); > {$I+} > if IOResult <> 0 then... > > In SunWorkshop Pascal it's a little bit more complicated even if its > different. > Is there something similar to these in GNU Pascal? Sorry, there's no {$I+-} directive in GPC yet, but some work has already been done towards implementing it. As for checking if a file exists, there are other ways, e.g. searching the directory, or (at least under Un*x systems, I don't know if also under Dos) stat(2)ing the file. The following works on my Linux system, so it should be alright for you: program FileExists; type TStatBuf=Array[1..$4000] of Byte; {It's currently not easy to get the correct C structure into GPC, but since I don't use the contents of the structure here, it doesn't matter. The above should be big enough, anyway... ;-} function stat(Name:CString;var Buf:TStatBuf):Integer; C; function Exists(s:String):Boolean; var Buf:TStatBuf; begin Exists:=stat(s+#0,Buf)=0 end; var a:String(200); begin Write('Enter a file name: '); readln(a); if Exists(a) then Writeln(a,' exists.') else Writeln(a,' doesn''t exist.') end. > 2. Where do I get a list of compile-time and run-time errors? I fear such a list doesn't exist -- there's much work to do about the documentation... :-( If you get the source distribution of GPC, you can find a *non-complete* list of run-time errors in rts/rts-error.c. I don't know if the compile-time errors are listed somewhere -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

gpc I/O & errors
by Laurentiu COCEA 17 Dec '97

17 Dec '97

Hello, This is not about a bug, I'm just trying to understand how gpc works. I have some experience--as an amateur, though--with TPW1.5 (MS-Windows) and TP6.0 (MS-DOS), and with SunWorkshop Pascal Compiler 4.2 (SunOS 5.5.1). I'm trying to compile some Pascal code of my own with the GNU Pascal Compiler on a PC running RedHat Linux 4.2. Questions: 1. How do I suspend I/O error messages in order to detect the presence/absence of a file? In Turbo Pascal, one does this as follows: {$I-} reset(file); {$I+} if IOResult <> 0 then... In SunWorkshop Pascal it's a little bit more complicated even if its different. Is there something similar to these in GNU Pascal? 2. Where do I get a list of compile-time and run-time errors? Thank you very much for any help you can provide. Laurentiu COCEA -- Laurentiu COCEA, M.D., M.Sc. Institut National de la Sante et de la Recherche Medicale, U.373 Faculte de Medecine Necker, 8e etage, porte 811Ter 156 rue de Vaugirard, 75730 Paris Cedex 15, France Ph:(33)14061-5384 Fax:(33)14061-5590 e-mail:cocea@necker.fr

1 0

Re: Regular Expression
by Peter Gerwinski 17 Dec '97

17 Dec '97

According to Hans Ecke: > Please excuse me, this is not a mail about GPC in special, but Pascal in > general. I'm searching for an regular expression library - I mean > something like > > function pos(SearchPattern;S:string):integer > > just like BPs build in Pos(SubString,String):integer function. Of course > their is Unix-regexp (in C), but if somebody already had done it in > Pascal, why do unnecessary work of translation? What about writing a GPC unit that interfaces GNU regex and/or GNU rx? > Beside this, I have the suggestion to build at agnes.dida a little > archive of rare plants and vegetables which you seldom find at the net - > like Lex/Yacc and maybe some Programming help (but not yet another SWAG > mirror). Of course this is Peters decission and I dont know if it > would be usefull. It depends, if their are enough good things on the HD of > the list members and if we think of the same if I say "rare good tools and > docs for Pascal Programming". We could make a start with what is crawling > at agnes.dida/gnu-pascal/misc. I would not mind to have such an archive on Agnes, but we must carefully choose what to put there and what not to put there. We must not collect just everything written in Pascal; having an overfull and/or badly documented archive is as useless as having no archive at all. As Agnes is devoted to GNU (that's why I have chosen a name containing "gn":-), I would require everything to be free, i.e. available in source code and without restrictions to use it even commercially. And it would be desirable to have everything ported to GNU Pascal. 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: Script interpreter object specs [Long!]...
by Peter Gerwinski 15 Dec '97

15 Dec '97

According to Orlando Llanes: > > What I'm working on learning now is breaking down an Algabraic > Equation (did I get the right term?) and arranging it so that it's in an > order ready to be translated into the byte codes. I think this step is > called converting Postfix to Infix. I saw some code in Pascal that parses > an equation and translates it by using loops and arrays rather than > recursing. What it does is juggle variable names, I don't know how capable > it is for processing real numbers or others. It only handles * / + and - > but it can be modified to handle Boolean operations, etc. I got the code > out of the Pascal SWAG. I'll upload the code where Peter moved Hans' > upload. Now the trouble begins: Is this program another candidate for that archive of tools? While it compiled straightforwardly with GPC, it is less general than a Pascal `lex' or `yacc', and it is in the SWAG. What are the licensing conditions of that Program? 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

Regular Expression
by Hans Ecke 15 Dec '97

15 Dec '97

Hi all! Please excuse me, this is not a mail about GPC in special, but Pascal in general. I'm searching for an regular expression library - I mean something like function pos(SearchPattern;S:string):integer just like BPs build in Pos(SubString,String):integer function. Of course their is Unix-regexp (in C), but if somebody already had done it in Pascal, why do unnecessary work of translation? Beside this, I have the suggestion to build at agnes.dida a little archive of rare plants and vegetables which you seldom find at the net - like Lex/Yacc and maybe some Programming help (but not yet another SWAG mirror). Of course this is Peters decission and I dont know if it would be usefull. It depends, if their are enough good things on the HD of the list members and if we think of the same if I say "rare good tools and docs for Pascal Programming". We could make a start with what is crawling at agnes.dida/gnu-pascal/misc. Bye Hans

1 0

GNU GUILE...
by Orlando Llanes 14 Dec '97

14 Dec '97

If anyone is interested, the website where I read information about GNU GUILE is: http://ns.cinfo.ru/linux/WWW/www_gnu.org/software/guile/guile.html The thing that GUILE has in common with my script interpreter other than extensibility is providing an interface so that the user is not restricted to just 1 language. Where the line ends on similarity is in the extent of features. What I'm trying to do is create an interface for programmers that is simple yet can do what is required of it, needs little modification, and allows them to add internals from their program into the script language while at the same time keeping it simple and flexible enough for the common ordinary end-user to modify the behavior of the program. GUILE seems to support file I/O and pointer operations, and is expected to (if it doesn't already) have a facility for system calls and system pipes. Allowing those 3 things could be a security compromise for applications such as a game (most likely others, but I can't think of any right now). It's not to say that GUILE is not worth a look, I'm sure it has its uses. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: Script interpreter object specs [Long!]...
by Peter Gerwinski 13 Dec '97

13 Dec '97

According to Orlando Llanes: > > [...] I found Lex/Yacc for TP on > ieec.com(?), it was a version from the "Dragon Book" [...] I know this is a stupid question but what is the title/author/foobar of this famous "Dragon Book"? I really have the impression that I should read it ... > Below are the specs for the script object > followed by the reasons for the specs and then my plans for the script > executor object.. What is the aim of this scripting language? You are probably not going to reinvent Pascal or Java. I assume that you want to have a language that allows the user to customize and extend the behaviour of your program. Did you have a look at GUILE, GNU's answer to this question? (I haven't, but I have read a lot about GUILE's existence.;-) Or else, what about defining a CGI-like interface between your program and another program written by the user in his/her favourite language? > [...] I'm planning on doing this is by allowing > the programmer to add tokens of their own to the script language at > run-time. What is the difference between this and the concept of user-defined types, variables, and procedures? > Now for the script executor object. I want to have a fixed set of base > opcodes so that no matter what language the scanner is written to handle, > it will always execute the opcodes in the same way, this way 2 or more > script scanners can be written to cater to the tastes of the end-user, but > will execute the same. The GNU compilers also support such a platform-independent "bytecode", and so does UCSD's P-Code and Java's J-Code. Perhaps you should have a look at their specifications first? Those of GCC/GPC are in the source code. Greetings, 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: Script interpreter object specs [Long!]...
by Orlando Llanes 13 Dec '97

13 Dec '97

On Sat, 13 Dec 1997, Stefan Tschirren wrote: > http://www.geocities.com/CollegePark/Quad/8070/tgc.html > The compiler and interpreter were pretty much working... I cant remember > now, It was a long time ago :-) K00l, I'll check it out :) > The reason I never actually finished that project was because I got stuck! I know how that goes :) > I couldnt figure out a way to make the character that you control move > around the screen, and interact with the enviromnent. EG: The character > must be able to move BEHIND the table, but not THROUGH the table. In other That's the key component to my game lib, and the main reason I want to add a script engine. I saw an article in "Game Developer's Magazine" about one of the programmers of Star Wars (Rebel Assault I think it was? I don't remmeber, could be Shadows Of The Empire), and in the script language it had one for the doors, walls, characters, and I think other things. One of the game designers wrote a script that would flood the level after hitting a certain sequence of switches, and nobody knew how he did it (the programmer who wrote the script engine himself was baffled :), so a good script engine could be a key component. > words, I couldnt figure out a good way of knowing where a character is > allowed to walk... Hmm, now that I come to think of it - It doesnt seem > that hard (I have an idea). Maybe the project will be reborn... Do a web search on Amit Patel, his web site is chock full of A* algorithms and AI. What you need for that is most likely the A* algorithm. > Anyway, if you want to take a look at some source, just ask and Ill email > the whole lot to you. You probably wont understant most of it (I wouldnt!)... > I usually like to keep the end-user away from programming type problems. > Scripting is clearly a programmers job, so it should not be tailored for > the end user (How many end-users actually write macros in MS-WORD??). I IMO, the programming part, the programmer interface, is important to the programmer, but the actual language and syntax is important to the user, not everybody is a programmer. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Re: ANNOUNCEMENT : TP Lex/Yacc 4.0
by Peter Gerwinski 13 Dec '97

13 Dec '97

Hi, Hans, Berend, and everybody! > I have uploaded TP Lex/Yacc 4.0 to (see above). Its a Version from October > 96. Author is Berend de Boer mailto:berend@pobox.com. It can be compiled > with and can make code for TP, BP-Real, BP-PM, BP-Windows, Delphi-16, > Delphi-32 (As far as I understood). It should be legal to put it on the > Net, because Berend - may the force be with him - has copyrighted it under > GPL2. I have moved it to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/misc/ > Maybe somebody has time enough to port it to GPC... I agree that this would be a good thing. Greetings, 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: Compiler writing-related question...
by Peter Gerwinski 13 Dec '97

13 Dec '97

According to Hans Ecke: > > Well, mathematically spoken, there exist at least one solution. I don`t > know where I found it, but I have at home Yacc&Lex for Pascal (with > source, AFAI remember), at least for BP. If you can`t find it in the Net, > I can send it to you (or better, upload it to GPC-home). It is under some > GPL-like licence, allowing to redistribute it. If you would either point us to where we can find it in the Net or upload it to ftp://agnes.dida.physik.uni-essen.de/incoming/ (and send me an E-Mail after you have done), it would be a good thing. :-) Dankeschoen im Voraus, 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: Error report capturing...
by Peter Gerwinski 13 Dec '97

13 Dec '97

According to Orlando Llanes: > > I beleive that gpc outputs to STDERR does it not? I know that gcc does, so > > you would have to do something like > > Sorry, I forgot to say that I'm using DOS :( [...] With DJGPP, use the `redir' program to get the same effect: redir -e <error file> gpc <options to gpc> (See also the DJGPP FAQ list, section 6.10.) 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: Error report capturing...
by Frank Heckenbach 13 Dec '97

13 Dec '97

Orlando Llanes wrote: > > I beleive that gpc outputs to STDERR does it not? I know that gcc does, so > > you would have to do something like > > Sorry, I forgot to say that I'm using DOS :( I tried what you wrote > anyway, but DOS would just write to the file &1 I looked in the DOS > Programmer's Reference (from DOS 6.0), and the handle to StdOut and StdErr > are different, it looks like DOS only redirects StdOut at the command > line. Yes, stderr is file handle 2 in Dos. You need the redir utility to redirect stderr (should be in one of the DJGPP packages). -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Error report capturing...
by Orlando Llanes 13 Dec '97

13 Dec '97

How could I redirect output generated by GPC so that it goes to a file? I tried -v but had no luck in capturing the errors. I want to do the following... gpc source.pas > file.err and have the compiler messages redirected to the file. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 2

Shall we drop the read-ahead?
by Peter Gerwinski 13 Dec '97

13 Dec '97

Hello, folks! When GPC opens a file, it reads one item ahead: Program Foo; Var F: File of Char; Ch: Char; begin Assign ( F, 'foo.pas' ); reset ( F ); (* This already reads the first character. *) Ch:= F^; (* <-- Wouldn't this be early enough here??? *) close ( F ); end. Since this causes problems with untyped files (which are currently being implemented) and already has caused bugs in other situations (see the thread "[BUG] GPC - a char killer?" discussed on this list in April) I think it would be only good to change this behaviour and to make GPC actually read the item when the file variable is accessed (see "<--" in the comment in the example above). Translated to Borland Pascal (well ... the example above almost *is* in BP syntax; it does definitly *not* comply to ISO Pascal;-) this would mean that the physical `read' will happen at the point where `read' appears in the source: reset ( F ); (* This already reads the first character. *) read ( F, Ch ); (* <-- Wouldn't this be early enough here??? *) (Right now, it happens *before* the `read', and during the call to `read' the *next* item is read physically.) (* O dear - I hardly understand my own mail; I hope you do. ;*) If anybody knows what the standard says about this, please tell me through this list. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Re: errors
by Peter Gerwinski 13 Dec '97

13 Dec '97

According to igor(a)merlot.stat.uconn.edu: > > I don't know if this is really a bug but I didn't find an FAQ with > my answer and I haven't found a place to post this except to send it to you. This list is the correct place. > I installed gpc-2.0 with gcc-2.7.2.3 (I just switched the GCCVERSION > variable in Makefile.in). I runed the configure with my machine arch and > used the --with-gccsrc, --with-gccbin, --prefix, --exec-prefix flags. > Somehow the --prefix didn't pass to the Makefile so I edited the Makefile > switching gcc_prefix to the correct place on my machine (I didn't touch > gcc_local_prefix). Just to ensure that we are not suffering from something trivial: GPC v2.0 derives its configuration from that of GCC and merely ignores (?) switches given to `configure'. Thus the problem might be that you gave these switches to GPC's `configure' instead of GCC's one. (* I am not sure about all this ... *) > After typing make, the program is build without any warnings or > errors. Sounds as if nothing has gone wrong with this. > So I tried some test programs and I looked in the standard_pascal > directory. I compiled hello.pas using gpc (gpc hello.pas) and also > tried linking with gcc (gpc -c hello.pas, gcc -o hello hello.o -lm -lgpc). AS > "hello world" wouldn't print out, I added the -g flag and tried to look at > it through a debugger. What I got is this: > > > (dbx) s > stopped in program_Hello at line 4 in file "hello.pas" > 4 writeln('Hello, world!'); > (dbx) s > internal error: unexpected value 120 at line 3851 in file stabstring.c > internal error: expected char ',', found 's__LC_locale:,768,32;__meth_ptr:9,800,32;__data_ptr:9,832,32;;' Looks like a plain bug in GPC's generation of DBX debugging information. First, you should upgrade to the most recent beta, gpc-971001, available from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/. Maybe this already fixes the bug; if not, you can help us to find the bug as follows: Please make sure that your GCC compiles `hello.c' and generates correct DBX debugging information. Then compile `hello.pas' and `hello.c' with the options `-g -S', compare both generated versions of `hello.s', and post your results to this list. I expect some tiny differences in otherwise equivalent `.stabs' lines. Good luck and thanks for your cooperation, 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: using Pascal binaries
by Peter Gerwinski 13 Dec '97

13 Dec '97

According to Victor Sperber: > I wanted to get Pascal from the GNU. Not being sufficiently > knowledgeable to get the source and compile it, I opted for getting the > binaries. In fact you need Linux to compile GPC for Windows 95/NT ... > I read the GNU Pascal FAQS and brought over cygwin32 beta16 > (and later 17) and expanded them in order to run Pascal under Windows95. > However on running gpc.exe I get "a required DLL file CYGWIN.DLL was not > found". This is the case on the 16 and 17 packages. Is there something I > need to do to get Pascal to run apart from executing it? I am not an expert for Windows issues, but you might find relevant files and additional information at ftp://agnes.dida.physik.uni-essen.de/home/janjaap/cygwin32/ > I have searched > my disk and it is true that there is no such DLL. Should it come with > binaries in the package, or do I have to get it from somewhere else? You can get it from http://www.cygnus.com/ Make sure that the CygWin beta version number matches that one specified in the GPC distribution because different versions are completely incompatible. (* If everything else fails, you can use the DOS (DJGPP or EMX) version of GPC in your Windows DOS box; see the GPC home page http://home.pages.de/~GNU-Pascal/ for more information. *) 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: Compiler writing-related question...
by Peter Gerwinski 12 Dec '97

12 Dec '97

According to Orlando Llanes: > > I want to include a script interpreter into my game programming lib which > will compile the plain-text script source into a platform independant > virtual machine, I also want to write the interpreter using OOP, so I > don't know if Lex/Yacc will help with this Lex/Yacc (Flex/Bison) are designed to generate C code, AFAIK. If you want to use it with Pascal, you can either just write Pascal code between the {...} and translate the remaining parts of the generated file somehow, or you can write a C wrapper that calls Pascal procedures which in turn do the real work. Having solved these problems, it's your decision whether you want to use OOP or not. I recommand to do so; GPC's parser itself - while written in C, not C++ - uses kind of objects ("tree nodes"). > (BTW, does anyone know where I > can find Lex/Yacc for Pascal that allows *commercial* use? Lex/Yacc > itself won't be part of the libs, but the code it generates will), Recent versions of Bison have more relaxed license conditions that allow the generated source to be used in non-free programs, so this should be no problem. > The main things I'm confused about is about > everything, the syntax checking phase (scanning?), parsing, and executing. I am not an expert, but AFAIK, "scanning" means to split the input into its atoms, the "tokens", "parsing" means to check the syntax rules and to "understand" the input, and if you write an interpreter, the execution of your input will be in the parsing stage. 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/

3 2

errors
by igor＠merlot.stat.uconn.edu 12 Dec '97

12 Dec '97

Hi, I don't know if this is really a bug but I didn't find an FAQ with my answer and I haven't found a place to post this except to send it to you. I know that you must be very busy and I hope that you could just tell me where to start looking for the answer. I installed gpc-2.0 with gcc-2.7.2.3 (I just switched the GCCVERSION variable in Makefile.in). I runed the configure with my machine arch and used the --with-gccsrc, --with-gccbin, --prefix, --exec-prefix flags. Somehow the --prefix didn't pass to the Makefile so I edited the Makefile switching gcc_prefix to the correct place on my machine (I didn't touch gcc_local_prefix). After typing make, the program is build without any warnings or errors. So I tried some test programs and I looked in the standard_pascal directory. I compiled hello.pas using gpc (gpc hello.pas) and also tried linking with gcc (gpc -c hello.pas, gcc -o hello hello.o -lm -lgpc). AS "hello world" wouldn't print out, I added the -g flag and tried to look at it through a debugger. What I got is this: (dbx) s stopped in program_Hello at line 4 in file "hello.pas" 4 writeln('Hello, world!'); (dbx) s internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: expected char ',', found 's__LC_locale:,768,32;__meth_ptr:9,800,32;__data_ptr:9,832,32;;' internal error: expected char ',', found '__LC_locale:,768,32;__meth_ptr:9,800,32;__data_ptr:9,832,32;;' internal error: expected char ';', found '_LC_locale:,768,32;__meth_ptr:9,800,32;__data_ptr:9,832,32;;' internal error: unexpected value 44 at line 3851 in file stabstring.c internal error: expected char ',', found '768,32;__meth_ptr:9,800,32;__data_ptr:9,832,32;;' internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: expected char ',', found 's_LC_locale_objhdl:,64,32;;' internal error: expected char ',', found '_LC_locale_objhdl:,64,32;;' internal error: expected char ';', found 'LC_locale_objhdl:,64,32;;' internal error: unexpected value 44 at line 3851 in file stabstring.c internal error: expected char ',', found '64,32;;' internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c internal error: unexpected value 120 at line 3851 in file stabstring.c stopped in _p_write at line 49 in file "rts-write.c" couldn't read "rts-write.c" As you can tell, I am a bit perplexed with these messages. I would think that somehow the -g option didn't work so well. I am runing AIX 4.1.4 with an ibm rs6000 machine. Do you have any idea of where to start to make the whole thing work? I need a pascal compiler and I'd hate to have to reprogram everything using a C compiler. Thanks for any help, Igor

1 0

Re: pascal binaries
by Peter Gerwinski 09 Dec '97

09 Dec '97

According to laussy: > Victor Sperber wrote: > > > > I have tried to send this once but it was returned. Trying again! > > > > I wanted to get Pascal from the GNU. Not being sufficiently > [snip] > > Yeah, by the way it's something quite annoying when posting to this > group to receive an error message even when the post is all right. We know that problem, and we are working on a solution. Please be patient! )-:, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

pascal binaries
by Victor Sperber 08 Dec '97

08 Dec '97

I have tried to send this once but it was returned. Trying again! I wanted to get Pascal from the GNU. Not being sufficiently knowledgeable to get the source and compile it, I opted for getting the binaries. I read the GNU Pascal FAQS and brought over cygwin32 beta16 (and later 17) and expanded them in order to run Pascal under Windows95. However on running gpc.exe I get "a required DLL file CYGWIN.DLL was not found". This is the case on the 16 and 17 packages. Is there something I need to do to get Pascal to run apart from executing it? I have searched my disk and it is true that there is no such DLL. Should it come with binaries in the package, or do I have to get it from somewhere else? The dir structure looks ok, I have bin,lib, hlp and test directories. However, I seem to need some more HLP. Thanks, -- Victor Sperber -- Victor Sperber

2 1

Compiler writing-related question...
by Orlando Llanes 08 Dec '97

08 Dec '97

This is aimed at the GPC team and anybody who knows about compiler/interpreter writing. I want to include a script interpreter into my game programming lib which will compile the plain-text script source into a platform independant virtual machine, I also want to write the interpreter using OOP, so I don't know if Lex/Yacc will help with this (BTW, does anyone know where I can find Lex/Yacc for Pascal that allows *commercial* use? Lex/Yacc itself won't be part of the libs, but the code it generates will), any tips are appreciated. The main things I'm confused about is about everything, the syntax checking phase (scanning?), parsing, and executing. Thanks in advance! See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

using Pascal binaries
by Victor Sperber 08 Dec '97

08 Dec '97

I wanted to get Pascal from the GNU. Not being sufficiently knowledgeable to get the source and compile it, I opted for getting the binaries. I read the GNU Pascal FAQS and brought over cygwin32 beta16 (and later 17) and expanded them in order to run Pascal under Windows95. However on running gpc.exe I get "a required DLL file CYGWIN.DLL was not found". This is the case on the 16 and 17 packages. Is there something I need to do to get Pascal to run apart from executing it? I have searched my disk and it is true that there is no such DLL. Should it come with binaries in the package, or do I have to get it from somewhere else? The dir structure looks ok, I have bin,lib, hlp and test directories. However, I seem to need some more HLP. Thanks, -- Victor Sperber

1 0

Re: [gpc-2.0] gcc version number mismatch
by Peter Gerwinski 07 Dec '97

07 Dec '97

According to Karl Heuer: > I need to build the latest gcc and gpc for a Deluxe Distribution. > The current version of gcc is 2.7.2.3, but gpc-2.0 is expecting > 2.7.2.1. I think 2.7.2.3 is nearly identical to 2.7.2.1, so maybe > I can just change gpc's Makefile.in so that it expects 2.7.2.3. > Do you know if this should work? This works. However the current beta version gpc-971001 is already much more stable than gpc-2.0; I hope that we will be able to release gpc-2.1 soon. You can get it from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/gpc-971001.tar.gz Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 2

ISO-10206 Extended Pascal for GNU Pascal
by Peter Gerwinski 06 Dec '97

06 Dec '97

(Posted to comp.lang.pascal.ansi-iso and to the GNU Pascal mailing list, gpc at hut dot fi.) Hello, Extended Pascal experts! We need your help to increase the compliance of the GNU Pascal compiler (GPC) to the ISO-10206 Extended Pascal standard. 1) We need a test suite to check in how far GNU Pascal does comply to the EP standard. (Our aim is 100%.) Does anyone know where to get such a thing? 2) The standard says that not only files, but also other Pascal entities may be bound to external entities, but the effect of such a binding is "implementation dependent". How do other implementations handle this? (* In case you don't know: GNU Pascal is a portable 32-bit Pascal compiler. It is Free Software according to the GNU General Public License. The current beta version (gpc-971001) supports most of ISO-10206 Extended Pascal as well as most of Borland Pascal 7.0. For more information, see our WWW pages, http://home.pages.de/~gnu-pascal/. *) Thanks in advance, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

"Time" bug - good news
by The African Chief 06 Dec '97

06 Dec '97

Hiya all, I have just discovered that the "time bug" which I reported a few days ago (in DJGPP) is not a bug in the GPC compiler at all. It it seems to have been caused by a bad parameter passed at the command line ("-extended-pascal", instead of "--extended-pascal"), which causes ld.exe to give a warning, and then produces a buggy .EXE file. Sorry for leading Peter and Frank on a wild goose chase! Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro 4.01 for Win16 and Win32: http://www.simtel.net/pub/simtelnet/win3/install/chief401.zip

1 0

Re: File/Record locking on Linux with GPC
by Frank Heckenbach 06 Dec '97

06 Dec '97

The African Chief wrote: > I was not talking about the date/time format at all. I was > talking about the actual values that are displayed. I just ran > the program again, and this is the output (DJGPP, running under > Windows NT v4.0): > > "327680.786432.130875392 851968:2490368:2424832" > > That is what I mean by "unintelligible". I don't know how to > translate these values into something that means something to > human beings. Ah, OK, that's something different -- namely a bug... :-( Of course, there should be no need for any translation, as the values in the time stamp should be the actual time -- and that's what they are on my Linux box. Perhaps it's the same bug that was reported about test\extended\time.pas in <34396148.5C71(a)ujf-grenoble.fr>, but I'll record this, too. Thanks for the bug report... :-| I'll take a look into the RTS and see if I can find something wrong. However, since I don't see the bug I'm not sure if I can find the problem... -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

3 2

Re: File/Record locking on Linux with GPC
by Peter Gerwinski 05 Dec '97

05 Dec '97

According to Maurice Lombardi: > > Perhaps it's the same bug that was reported about test\extended\time.pas > > in <34396148.5C71(a)ujf-grenoble.fr>, but I'll record this, too. Thanks > > for the bug report... :-| > No it is different. I have checked that this old bug is still there, > while the example of the Chief works fine on my machine. > (All is made in plain DOS/ DJGPP v2.1, > the old bug did not appear under bash shell in the same machine) I suspect that this bug is not in GPC but in the DJGPP port of the UNIX function `gettimeofday'. Maybe the `bash' shell catches and "repairs" the DOS interrupt? I don't know ... Maybe we should re-write `_p_gettimestamp' for the MSDOS target using the interrupt directly? The other bug reported by The African Chief *might* have the same reason. A lot of guessing, sorry ... Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: binary gpc2.0 for Solaris 2.5.1
by Frank Heckenbach 05 Dec '97

05 Dec '97

Hi Javier, I have successfully installed the Solaris binary on the computers at the math institute of our university -- exactly on the 20th anniversary of the computer station. :-) When the next beta version of GPC comes out, can you please provide me a binary of this, too? Then I could run the test suite on the sparcs and make sure there are no new bugs, before we can finally release GPC 2.1. Regards, Frank -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

GPC article
by The African Chief 05 Dec '97

05 Dec '97

Hi all, This month's edition of the Developers Review (sister magazine of the Delphi Magazine) carries an article on GPC, written by (yours truly!! :-)). I I have already had an email about it! Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro 4.01 for Win16 and Win32: http://www.simtel.net/pub/simtelnet/win3/install/chief401.zip

1 0

UNSUBSCRIBE
by Ron Perrella 05 Dec '97

05 Dec '97

UNSUBSCRIBE

1 0

Re: File/Record locking on Linux with GPC
by Peter Gerwinski 05 Dec '97

05 Dec '97

According to Pismo: > I have posted in the Borland Delphi group(s)that I use GPC and the > Delphi command line compiler to write CGIs on Linux and NT that > ported with very few mods. :-) Good news! > Have you considered a GPC newsgroup, and if so do you need somewhere > to host it? I'll be putting up a NNTP server to spool local > newsgroups for the ISP where my server is hosted and would be able to > add a group for GPC. Can one simply create a new Newsgroup "just like that"? I think that you can do so only for "alt.*" Newsgroups, and for a GNU Pascal Newsgroup the "natural" name would be "comp.lang.pascal.gnu". The host would not be a problem, but doesn't the creation of a new Newsgroup require some voting etc.? It also would be nice to do it like the DJGPP guys and to route the mailing list into the Newsgroup and vice versa. If you can help to solve these problems, it would be highly welcome. > Also if you want to quote anything I've said in email on the GPC-list > I had assumed it would probably be forwarded there anyway. I only > wrote you directly because my posts had been rejected with that error > I sent you recently. The error message can be ignored; your messages went through to the list members. (I am CCing this e-mail to the list and will probably get the same error message again.) > Thanks a bunch, and I really appreciate your efforts producing GPC. You are welcome. :-) Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: File/Record locking on Linux with GPC
by Frank Heckenbach 05 Dec '97

05 Dec '97

The African Chief wrote: > > program x; > > var time:TimeStamp; > > begin > > GetTimeStamp(time); > > writeln(time.day,'.',time.month,'.',time.year,' ', > > time.hour,':',time.minute,':',time.second) > > end. > > The output from this is unintelligible. Is there a way to convert > the output into something useful? We won't argue about different date/time formats, will we? I just used the format that's usual around here. Since the writeln statement should be self-explanatory, you should have no problems converting it into a format that you prefer. Regards, Frank -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

2 1

[gpc-2.0] gcc version number mismatch
by kwzh＠gnu.org 05 Dec '97

05 Dec '97

I need to build the latest gcc and gpc for a Deluxe Distribution. The current version of gcc is 2.7.2.3, but gpc-2.0 is expecting 2.7.2.1. I think 2.7.2.3 is nearly identical to 2.7.2.1, so maybe I can just change gpc's Makefile.in so that it expects 2.7.2.3. Do you know if this should work?

2 1

Re: File/Record locking on Linux with GPC
by Frank Heckenbach 05 Dec '97

05 Dec '97

The African Chief wrote: > Pismo wrote: > > [...] > > > > If I could lock a file with GPC (like flock in Perl) then > > > > I could create my own record locking implementation. Without > > > > being able to lock a file at the OS level trying to accomplish > > > > this would be flakey at best. I want to use GPC for multi-user > > > > database apps I'm porting from BP/Delphi. > > > > > > If there is a C function for that you can use that: > > > > > > extern void foobar ( int foo, char *bar ); > > > > > > becomes > > > > > > Procedure Foobar ( foo: Integer; bar: CString ); C; > > > > > > but you should better ask again at the GPC mailing list, gpc(a)hut.fi. > > > I have no experience with Perl, sorry. > > > > > > > I don't use Perl or C, but I'm sure we must have a C programmer on > > the list who can answer this for us. > > File and record locking is a service that should be provided by > the operating system, not by a compiler. I believe that any > modern operating system provides this facility - but this means > that you might have to access the service in a different way > under each operating system that you want to support (or write a > single function to access the service, with zillions of #IFDEFs > to cater for different operating systems). For Linux: man flock says: int flock (int fd, int operation) So, in GPC this is function flock (fd, operation: integer): integer; C; Operation is one of LOCK_SH, LOCK_EX, LOCK_UN, possibly OR'ed with LOCK_NB. Unfortunately, these "constants" are macros in C, declared in <sys/file.h>, and there's not yet a way to automatically translate them into Pascal, so you have to translate them manually, hoping that they're the same on all OS versions... fd is the file descriptor. In recent GPC betas, you can get the "FILE*" of a file (a pointer) via GetFile, but you need a way to get the file descriptor (an integer). I didn't find a C function that does this, but if there's really none, you could write one yourself. An example: file fileno.c: #include <stdio.h> int getfileno(FILE* foo) {return foo->_fileno;} file x.p: program x; const { translated from <sys/file.h> } LOCK_SH = 1; { Shared lock. } LOCK_EX = 2; { Exclusive lock. } LOCK_UN = 8; { Unlock. } { Can be OR'd in to one of the above. } LOCK_NB = 4; { Don't block when locking. } {$L fileno.c} function getfileno (f: pointer): integer; C; function flock (fd, operation: integer): integer; C; var a,b:text; begin reset(a,'x.p'); reset(b,'x.p'); writeln(flock(getfileno(getfile(a)),lock_ex)); writeln(flock(getfileno(getfile(b)),lock_ex OR lock_nb)); close(a); close(b) end. On my system, it outputs 0 and -1, which means that the first lock succeeded, the second didn't, as it ought to be. > > BTW how would I check the system clock? > > Look at the DOS and DOSH units in the BPCOMPAT package. Not really. He was asking for Linux, and the Dos unit is not portable, AFAIK. But there's no need to use any units, because Extended(?) Pascal has a built-in way to access the time: program x; var time:TimeStamp; begin GetTimeStamp(time); writeln(time.day,'.',time.month,'.',time.year,' ', time.hour,':',time.minute,':',time.second) end. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

2 1

Re: lost mail forwarded to list from GNU central...
by Peter Gerwinski 05 Dec '97

05 Dec '97

According to Sean <mecan(a)hotmail.com>: > > I have been trying to use the gpc and I keep getting the error > ld: cannot open -lgpc: No such file or directory (* Sean, please break up your lines; otherwise your mail is hard to read. Thanks. *) The name of the file is `libgpc.a' or `libgpc.so'. I was reported that the Debian distribution fails to symlink libgpc.so -> libgpc.so.2.8 and only sets libgpc.so.2 -> libgpc.so.2.8 which is not sufficient. Doing `ln -s libgpc.so.2.8 libgpc.so' manually in `/usr/lib/gcc-lib/i586-unknown-linux/2.7.2/' (or whereever Debian keeps this lib) should solve your problem. > find | grep lgpc Try `find | grep libgpc'. I guess it will be in `/usr/lib'. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

lost mail forwarded to list from GNU central...
by Mail Delivery Subsystem 05 Dec '97

05 Dec '97

From: root <root(a)toxic40.dyn.ml.org> Date: Thu, 4 Dec 1997 06:44:22 -0500 I have been trying to use the gpc and I keep getting the error ld: cannot open -lgpc: No such file or directory I am running debian linux, I used to be an assembly programmer but saw it fit to attempt to learn C because I came to really enjoy running LINUX and since I already know how to program in pascal I have been trying to do just that until I get oriented with programming in linux, hope you can help. I guess all I need is to find out what package would install this -lgpc that it's looking for because I have search my entire system looking for it and can't find it. ie: find | grep lgpc Hope you can help, I would rather be programming for LINUX than for the DOS environment thanx Sean mecan(a)hotmail.com

1 0

lost mail forwarded to list from GNU central... (fwd)
by Jan-Jaap van der Heijden 04 Dec '97

04 Dec '97

...And I shall forward it again, to the list, where it belongs... Does libgpc come seperate from the compiler in the Debian Linux package? JanJaap ---------- Forwarded message ---------- Date: Thu, 4 Dec 1997 06:46:21 -0500 (EST) From: Mail Delivery Subsystem <MAILER-DAEMON(a)prep.ai.mit.edu> To: postmaster(a)prep.ai.mit.edu Subject: lost mail forwarded to list from GNU central... Resent-Date: Thu, 4 Dec 1997 16:46:38 -0500 (EST) Resent-From: GNU Mailing List Maintenance <gnu(a)prep.ai.mit.edu> Resent-To: gpc(a)prep.ai.mit.edu From: root <root(a)toxic40.dyn.ml.org> Date: Thu, 4 Dec 1997 06:44:22 -0500 I have been trying to use the gpc and I keep getting the error ld: cannot open -lgpc: No such file or directory I am running debian linux, I used to be an assembly programmer but saw it fit to attempt to learn C because I came to really enjoy running LINUX and since I already know how to program in pascal I have been trying to do just that until I get oriented with programming in linux, hope you can help. I guess all I need is to find out what package would install this -lgpc that it's looking for because I have search my entire system looking for it and can't find it. ie: find | grep lgpc Hope you can help, I would rather be programming for LINUX than for the DOS environment thanx Sean mecan(a)hotmail.com

1 0

Re: File/Record locking on Linux with GPC
by Peter Gerwinski 04 Dec '97

04 Dec '97

According to Pismo: > Perl and C have Flock, and GPC > should (does?) have a similar call [...] I just have discovered the following C header for `flock' (see `man flock' under Linux; I hope that DJGPP provides an equivalent function): int flock ( int fd, int operation ) The equivalent Pascal declaration is Function FLock ( fd, operation: Integer ): Integer; C; You can look up the values for `operation' from the C include file. The remaining problem is how to get the file descriptor `fd' from a Pascal `file'. First, you can get a C-style `FILE' pointer from a Pascal file using the `GetFile' function (built-in in gpc-971001): Function GetFile ( Const F: <file type> ): Pointer; (With GPC before gpc-971001, say Function GetFile ( Const F: <file type> ): Pointer; AsmName '_p_getfile'; to declare the function.) Having that you can use the `filenum' function to get the file number: int fileno ( FILE *stream ); or, in Pascal, Function FileNo ( Stream: Pointer ): Integer; C; With this declarations, the following should do what you wish: Function GetFile ( Const F: <file type> ): Pointer; AsmName '_p_getfile'; Function FileNo ( Stream: Pointer ): Integer; C; Const SharedLock = 1; (* From <sys/file.h> under Linux *) ExclusiveLock = 2; Unlock = 8; Var Foo: File of Bar; ... Flock ( FileNo ( GetFile ( Foo ) ), SharedLock ); Good luck, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: File/Record locking on Linux with GPC
by Pismo 04 Dec '97

04 Dec '97

> From: Peter Gerwinski <peter(a)agnes.dida.physik.uni-essen.de> > Subject: Re: File/Record locking on Linux with GPC > To: pismo(a)warf.com > Date: Wed, 3 Dec 1997 23:48:34 +0100 (MET) > Hi, Pismo, > > you wrote: > > > > If I could lock a file with GPC (like flock in Perl) then > > I could create my own record locking implementation. Without > > being able to lock a file at the OS level trying to accomplish > > this would be flakey at best. I want to use GPC for multi-user > > database apps I'm porting from BP/Delphi. > > If there is a C function for that you can use that: > > extern void foobar ( int foo, char *bar ); > > becomes > > Procedure Foobar ( foo: Integer; bar: CString ); C; > > but you should better ask again at the GPC mailing list, gpc(a)hut.fi. > I have no experience with Perl, sorry. > I don't use Perl or C, but I'm sure we must have a C programmer on the list who can answer this for us. BTW how would I check the system clock?

2 1

Re: File/Record locking on Linux with GPC
by Pismo 04 Dec '97

04 Dec '97

> > File and record locking is a service that should be provided by > the operating system, not by a compiler. This is true, but the compiler must provide some way (interface) to call the operating system service. Perl and C have Flock, and GPC should (does?) have a similar call that is transparent to the programmer implemented at the compiler level to call the correct operating system service for each OS it runs on for code portability. BP or Delphi compatible calls would be nice, but anything that would work on GPC that is standard on every platform supported only makes sense. [snip] > > BTW how would I check the system clock? > > Look at the DOS and DOSH units in the BPCOMPAT package. > > Best regards, The Chief > --------

1 0

January 1998 GNU's Bulletin
by Peter Gerwinski 03 Dec '97

03 Dec '97

Hello, everybody! In the GNU's Bulletin, GNU Pascal is mentioned at two places: "Current Software" has the text @need 301 @item @code{gpc} @value{hfill-kludge} @emph{Also @pxref{GNUs Flashes}} @w{ } (SrcCD) @code{gpc} is the GNU Pascal Compiler. and "GNUs Flashes" carries a real article about GNU Pascal (included below). Is it okay like this, or would somebody like to have it changed? Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005] 8< ---- GNUs Flashes --------------------------------------------------------- @need 301 @item @b{GPC, the GNU Pascal Compiler} The GNU Pascal Compiler (GPC) is part of the GNU compiler family, GNU CC or GCC. It combines a Pascal front end with the proven GNU compiler backend for code generation and optimization. Unlike utilities such as p2c, this is a true compiler, not just a converter. Version 2.0 of GPC corresponds to GCC version 2.7.2.1. The purpose of the GNU Pascal project is to produce a compiler which: @itemize @bullet{} @item combines the clarity of Pascal with powerful tools suitable for real-life programming, @item 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) @item supports other Pascal standards (UCSD Pascal, Borland Pascal, Pascal-SC) in so far as this serves the goal of clarity and usability, @item can generate code for and run on any computer for which the GNU C Compiler can generate code and run on. @end itemize The current release (2.0) implements Standard Pascal (ISO 7185, level 0) and a large subset of Extended Pascal (ISO 10206) and Borland Pascal. The upcoming release 2.1 features better conformance to the various Pascal standards, and of course bug fixes. A growing group of GPC enthusiasts contributes to the project with code, bug reports or fixes. @w{@file{http://agnes.dida.physik.uni-essen.de/~gnu-pascal/}}, also known as @w{@file{http://home.pages.de/~gnu-pascal/}}, is the GNU Pascal home page; sources may be downloaded from @w{@file{ftp://kampi.hut.fi/jtv/gnu-pascal/}} (official) or @w{@file{ftp://agnes.dida.physik.uni-essen.de/pub/gnu-pascal/}} (development versions).

1 0

Re: Sockets
by Peter Gerwinski 02 Dec '97

02 Dec '97

According to Matthew Wiggins: > this sort of helps, except in both of the replys I have gotten > you have mentioned ShortCard, what in god's name is that? yes, > okay but this does help alot, if I find out what shortcard is. (This was in one long line which made it hard to read; better break it up. It is also better to continue this discussion on the GPC mailing list because there might be others who have the same problem and are interested in the solution. Thanks.) `ShortCard' is a built-in integer type in recent beta versions of GPC. It is compatible to C's `unsigned short' and usually has 16 bits. To get the same in gpc-2.0, use Type Cardinal = __unsigned__ Integer; ShortCard = __short__ Cardinal; or Type ShortInt = __short__ Integer; ShortCard = __unsigned__ ShortInt; Other C-compatible modifiers are `__byte__', `__long__' and `__longlong__'. For other built-in integer types in GPC betas, see the online documentation, `info -f gpc -n "Integer types"'. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: ODP: Interfacing DJGPP C with Pascal
by Peter Gerwinski 02 Dec '97

02 Dec '97

According to Stanislaw Kozlowski: > > Yes, this is all that I needed. Maybe this informationit should be included > in INFO help ? Yes, that would be good. In fact I am already working on such things, but it costs time ... :-( > In fact inspecting binary code of LIBPC.A I figured out > that _p_initialize should be called but I did no know the parameters. Why didn't you inspect the *source* code of `libgpc.a'? It is available from the same place where you got the binaries. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

subscribe
by Marco Klein 02 Dec '97

02 Dec '97

subscribe

1 0

Re: File/Record locking on Linux with GPC
by Peter Gerwinski 01 Dec '97

01 Dec '97

According to Pismo: > I need to lock records or at least files on database > written with GPC on Linux system ... how? What do you mean by "locking records"? How would you do this manually or with another programming language? Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Re: Sockets
by Peter Gerwinski 01 Dec '97

01 Dec '97

Hello, Matthew! Hi, everybody! According to RHS Linux User: > I was trying to open a socket, but the problem I kept running into was > that connect wants a sockaddr struct, and in C you just casted it... > (struct sockaddr *)&address but, I don't think that that is possible in > pascal, [...] Since you cannot simply #include a C header file in a Pascal program you have to define the type by yourself: Const AF_UNSPEC = 0; AF_UNIX = 1; (* Unix domain sockets *) AF_INET = 2; (* Internet IP Protocol *) AF_AX25 = 3; (* Amateur Radio AX.25 *) AF_IPX = 4; (* Novell IPX *) AF_APPLETALK = 5; (* Appletalk DDP *) AF_NETROM = 6; (* Amateur radio NetROM *) AF_BRIDGE = 7; (* Multiprotocol bridge *) AF_AAL5 = 8; (* Reserved for Werner's ATM *) AF_X25 = 9; (* Reserved for X.25 project *) (*$ifdef LINUX_2_1_X *) AF_INET6 = 10; (* IP version 6 *) (*$endif *) AF_MAX = 12; (* For now.. *) Type SockAddrPtr = ^SockAddr; SockAddr = record case family: ShortCard of AF_UNSPEC: ( data: packed array [ 0..13 ] of Char ); AF_INET: ( port: ShortWord; address: array [ 1..4 ] of Byte ); end (* SockAddr *); Having this you can declare a variable `Address' of type `SockAddr', so `@Address' will have the correct type - no need to cast. However, `SockAddrPtr ( @Address )' is the exact analogon of your C fragment above. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Sockets
by Kevin A. Foss 01 Dec '97

01 Dec '97

On Thu, 27 Nov 1997 11:15:44 -0800 (PST), RHS Linux User wrote: Hello, >I was trying to open a socket, but the problem I kept running into was >that connect wants a sockaddr struct, and in C you just casted it... >(struct sockaddr *)&address but, I don't think that that is possible in >pascal, so if anyone has successfully done this or knows how. please email >me, Well, I've done some work interfacing GPC with sockets, and the problem you describe is the first one I hit. The only solution I've found so far for problems like these is to wrap them inside callable C routines. E.g. I have something like: int bind_socket(int orig_sock, short family, u_short port) { struct sockaddr_in serv_adr; memset( &serv_adr, 0, sizeof(serv_adr) ); serv_adr.sin_family = family; serv_adr.sin_addr.s_addr = htonl(INADDR_ANY); serv_adr.sin_port = htons(port); if (bind( orig_sock, (struct sockaddr *) & serv_adr, sizeof(serv_adr)) < 0) { close(orig_sock); return (-1); } return (0); } in socket.c (with all of the necessary includes) Then in my Pascal source I use: function bind_socket(socket : integer; family : ShortInt; port : ShortCard) : integer; C; and I can bind a socket with a call like: result := bind_socket(socket, AF_INET, port); The at compile time I just include my C file with the source: gcc sockettest.pas socket.c -lsocket or whatever... As I explore more of the features in GPC hopefully I'll be able to make more calls directly from Pascal, but for calls like bind(), accept() and connect() I've found it easier to write a wrapper in C. Obviously it would take a while to write good wrappers that would return full error conditions to GPC not to mention allowing users to get at all of the socket options you have in C, but I've been just kludging solutions that happen to fit my needs. Right now all I have working is a quick-and-dirty connection where a client can send strings to a server process on another machine and have it echoed back slightly modified. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: agnes down ?
by Jan-Jaap van der Heijden 30 Nov '97

30 Nov '97

I'm sorry that I ever questioned the stability of agnes. We seem to be dealing with a severe case of Micro$ofteritis here: [janjaap@ZOO-station janjaap]$ traceroute agnes.dida.physik.uni-essen.de traceroute to agnes.dida.physik.uni-essen.de (132.252.78.226), 30 hops max, 40 byte packets 1 router (130.89.220.1) 2.711 ms 3.995 ms 2.914 ms 2 Enschede2.router.surfnet.nl (145.41.162.97) 3.528 ms 2.835 ms 2.879 ms 3 BR1.Enschede.surf.net (145.41.8.109) 2.121 ms 6.237 ms 4.252 ms 4 BR2.Amsterdam.surf.net (145.41.7.30) 5.64 ms 14.08 ms 8.182 ms 5 BR1.Amsterdam.surf.net (145.41.8.101) 7.403 ms 12.607 ms 24.147 ms 6 Amsterdam1.belsurf.net (192.12.54.9) 7.402 ms 6.613 ms 9.705 ms 7 Amsterdam6.att-unisource.net (192.12.54.2) 8.483 ms 8.549 ms 7.352 ms 8 amsterdam5.att-unisource.net (195.206.64.17) 318.871 ms 361.2 ms 18.563 ms 9 frankfurt5.att-unisource.net (195.206.64.22) 17.684 ms 21.509 ms 23.506 ms 10 frankfurt6.att-unisource.net (195.206.64.42) 22.506 ms 43.934 ms 46.413 ms 11 DE.ten-34.net (195.206.64.62) 225.805 ms 264.866 ms 287.893 ms 12 ir-frankfurt1.WiN-IP.DFN.DE (193.203.227.18) 33.907 ms 20.889 ms 21.918 ms 13 ZR-Frankfurt1.WiN-IP.DFN.DE (188.1.144.98) 22.164 ms 22.444 ms 23.534 ms 14 ZR-Koeln1.WiN-IP.DFN.DE (188.1.144.33) 75.619 ms 211.154 ms 242.466 ms 15 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.102) 27.147 ms 28.515 ms 36.096 ms 16 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 28.153 ms 30.981 ms 24.481 ms 17 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 28.175 ms 27.505 ms 27.928 ms 18 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 251.871 ms 30.899 ms 30.939 ms 19 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 30.12 ms 33.21 ms 39.284 ms 20 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 27.753 ms 28.763 ms 28.15 ms 21 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 46.955 ms 32.169 ms 37.127 ms 22 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 37.985 ms 35.388 ms 26.641 ms 23 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 28.455 ms 30.814 ms 30.428 ms 24 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 47.757 ms 29.068 ms 30.278 ms 25 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 28.909 ms 49.848 ms 38.464 ms 26 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 42.089 ms 31.354 ms 35.137 ms 27 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 30.687 ms 44.349 ms 70.558 ms 28 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 33.559 ms 49.084 ms 36.502 ms 29 Uni-Essen1.WiN-IP.DFN.DE (188.1.6.165) 36.483 ms 45.423 ms 33.041 ms 30 KR-Uni-Essen1.WiN-IP.DFN.DE (188.1.6.166) 34.048 ms 32.716 ms 33.079 ms Damn, you shouldn't use NT for serious work :-( JJ --- 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

agnes down ?
by Jan-Jaap van der Heijden 30 Nov '97

30 Nov '97

agnes.dida.physik.uni-essen.de seems to be down since last night. Peter (you're not reading this -- your email is @agnes...), I hope nothing serious happened. JJ --- 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

Re: Interfacing DJGPP C with Pascal
by Peter Gerwinski 29 Nov '97

29 Nov '97

According to Stanislaw Kozlowski: > I am trying to link a Pascal unit DJGPP C. It links OK but > Pascal run time library seems to be unitialized [...] Before you can use the Pascal run time library you must initialize it by calling `_p_initialize()'. External declaration in C notation follows: extern void _p_initialize ( int argc, char **argv, char **envp ); (The parameters are self-explanatory for C programmers.;-) GPC quits the program by calling extern void _p_finalize ( void ); but it is sufficient to call `_p_fflush()' since `_p_finalize()' reads /* This is called when program ends normally */ void _p_finalize () { _p_fflush(FALSE); /* Call an empty routine, user might want to execute some code here */ _p_final (); exit (0); } Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

this unit does not work
by laussy 29 Nov '97

29 Nov '97

Hi all, I would like to put some file operation in a separate precompiled unit. The matter is the assign binding code given in the info file does not work when put in a UNIT, where it works when in the program source itself, and some others units I made exactly the same way works fine (not using to begin do). Here is the unit code contening just the binding : -------------- UNIT files_operations; INTERFACE Procedure Assign ( Var T: Text; Name: String ); IMPLEMENTATION Procedure Assign ( Var T: Text; Name: String ); Var B : BindingType; begin (* Assign *) unbind ( T ); B:= binding ( T ); B.Name:= Name; bind ( T, B ); B:= binding ( T ); end; (* Assign *) END. --------------- And when linked as the usual way in the program, it makes it crash (segmentation fault). gpc --version 2.0(2.7.2.1)

2 1

Re: iso10206 Seek Functions and a couple other little things....
by Peter Gerwinski 28 Nov '97

28 Nov '97

According to Kevin A. Foss: > > Actually it works without patching the source because you are doing > non-continuous reads -e.g. using seekread() before each read(). Okay, so what about this one: Program Test ( Output ); Var Data: File [ 0..25 ] of Char; C: Char; begin rewrite ( Data ); for C:= 'A' to 'Z' do write ( Data, C ); reset ( Data ); SeekRead ( Data, ord ( 'O' ) - ord ( 'A' ) ); read ( Data, C ); write ( C ); SeekRead ( Data, ord ( 'K' ) - ord ( 'A' ) - 1 ); read ( Data, C ); read ( Data, C ); writeln ( C ); end. It produces "OK" with the patch; "OJ" without. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: binary gpc2.0 for Solaris 2.5.1
by Peter Gerwinski 28 Nov '97

28 Nov '97

Hello, everybody! I moved the binary compiled by Javier in place. It can be downloaded now from ftp://kampi.hut.fi/jtv/gnu-pascal/binary/ and from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/binary/ Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Unsubscscribe
by m00g0s01＠email.mcmail.com 28 Nov '97

28 Nov '97

Please Unsubscribe me from your mailing lists

1 0

Interfacing DJGPP C with Pascal
by Stanislaw Kozlowski 28 Nov '97

28 Nov '97

Hello I am trying to link a Pascal unit DJGPP C. It links OK but Pascal run time library seems to be unitialized so writeln would not work. The error is: ?GPC runtime error: File is not open for writing (#9) Is there any possibility to initalize it properly either from this unit of from C main ? Best regards Stanislaw Kozlowski

1 0

Interfacing GNU Pascal with GNU C
by Stanislaw Kozlowski 28 Nov '97

28 Nov '97

Hello ! I tried calling GNU Pascal procedure (compiled as separate unit) from GNU DJGPP C main program. Everything worked fine except that Pascal run time output seems to be uninitialized so writeln would not work. How can I initialize it (from initialization of the Pascal unit or C main program) ? Best regards Stanislaw Kozlowski

1 0

Sockets
by RHS Linux User 27 Nov '97

27 Nov '97

I am not a part of the mailing list as of now, but I have subscribed. anyway, I was trying to open a socket, but the problem I kept running into was that connect wants a sockaddr struct, and in C you just casted it... (struct sockaddr *)&address but, I don't think that that is possible in pascal, so if anyone has successfully done this or knows how. please email me, lithium(a)lumni.com matthew wiggins

1 0

Re: binary gpc2.0 for Solaris 2.5.1
by Frank Heckenbach 27 Nov '97

27 Nov '97

Javier Medina Bautista wrote: > Hi team of gpc. > > My name is Javier Medina I'am the system manager at Universidad Autonoma > Metropolitana in Mexico City. > > I already compiled the gpc2.0 in a Sparcstation with Solaris 2.5.1 and I > have a binary distribution. > > What can I do for send you this file?, I thing there are many people > interested in binary from Solaris operating system. Great! We have such machines at our university, and I'd like to try GPC on them! (Up to now, I haven't had the chance to build one myself.) When you've uploaded it, I'll be happy to try some programs on these machines. I hope, when GPC 2.1 comes out soon, you can make a sparc-sun-solaris binary for it, too. Greetings, Frank -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Re: iso10206 Seek Functions and a couple other little things....
by Kevin A. Foss 27 Nov '97

27 Nov '97

On Thu, 27 Nov 1997 12:06:27 +0100 (MET), Peter Gerwinski wrote: >I consider this a bug in GPC, but in fact I am not sure either what the >EP standard really means. Prospero's Extended Pascal compiler (PEP) >rejects your code but it accepts the following: [...] (seekrd.pas) >To fix GPC so it produces 'OK' from this source, edit the >file `rts/rts-random.c' and comment out the `if' statement >after "Seek back to the place ..." in `_p_seekread()' and >in `_p_seekupdate()'. Actually it works without patching the source because you are doing non-continuous reads -e.g. using seekread() before each read(). >(* BTW, EP experts, if I write `Program Test ( Output, Data );', >the program does *not* ask me for a file name for `Data' when >compiled with PEP. It works anyway, but I do not detect the >data file on my hard disk afterwards. What is the legal way >to produce an external file in EP? *) My understanding is that you have to bind a file name. Program Test ( Output, Data ); Var Data: bindable File [ 0..25 ] of Char; b : BindingType; C: Char; begin b := binding (data); b.Name := 'data'; bind(data, b); [... rest of seekrd.pas] But then again, I'm shooting in the dark, as I was with the seek* calls, not having played around with extended Pascal features before. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: iso10206 Seek Functions and a couple other little things....
by Peter Gerwinski 27 Nov '97

27 Nov '97

According to Kevin A. Foss: > While I'm on the topic of exploring the file functions, does > anyone want to explain the function of the various Seek* functions in > extended Pascal? The descriptions in the standard contain a lot of > intelligible text and little in the way of examples. I have the same problem. > I assumed that > Seekread(file, n) would simply take me to the nth record in 'file,' -- > which it does, but then it actually seems to stall the file pointer at > n until you read two items. > [...] > I would have expected D D E F G H for output? Why does the file > pointer stay at 3 for two consecutive reads? Is this a bug or am I > misusing seekread()? I consider this a bug in GPC, but in fact I am not sure either what the EP standard really means. Prospero's Extended Pascal compiler (PEP) rejects your code but it accepts the following: Program Test ( Output ); Var Data: File [ 0..25 ] of Char; C: Char; begin rewrite ( Data ); for C:= 'A' to 'Z' do write ( Data, C ); reset ( Data ); SeekRead ( Data, ord ( 'O' ) - ord ( 'A' ) ); read ( Data, C ); write ( C ); SeekRead ( Data, ord ( 'K' ) - ord ( 'A' ) ); read ( Data, C ); writeln ( C ); end. (seekrd.pas) To fix GPC so it produces 'OK' from this source, edit the file `rts/rts-random.c' and comment out the `if' statement after "Seek back to the place ..." in `_p_seekread()' and in `_p_seekupdate()'. (* BTW, EP experts, if I write `Program Test ( Output, Data );', the program does *not* ask me for a file name for `Data' when compiled with PEP. It works anyway, but I do not detect the data file on my hard disk afterwards. What is the legal way to produce an external file in EP? *) (* sqr ( BTW ), UCSD/BP's `Seek' is now in GPC, too. *) (* BTW pow 3, I see it's time for the next beta ... *) > Also isn't the typechecking of seekread a little harsh to not allow: > [...] > reset(inputfile, 'data'); > [...] > when it does allow: > [...] > index : integer = 3; > [...] > seekread(inputfile, index); The problem was that, in order to avoid arithmetical overflow, GPC assigned the largest possible type to integer constants (either `LongestInt' or `LongestCard') and converted it to something smaller when the constant is used together with something of known type. This is fixed now, too: Integer constants in GPC are now `Integer'. Only if this does not fit, `Cardinal', `LongestInt', and `LongestCard' are used (in this order). > Various Miscellany: > When I was playing around with all of this I wrote an ugly bit of code > that could be reduced to: > > program test(output); > var i : 3..3; > begin > i := i + 1; > writeln(i); > end. > > Why isn't there a warning about i being undefined? This code outputs > 1, btw :) A good question. Maybe the GCC backend initializes global variables to zero, so it has a defined value (out of range)? I will have to investigate it (kevin2.pas) ... > Lastly according to iso7185:6.4.2.4, "The first constant of a > subrange-type shall specify the smallest value, and this shall be less > than or equal to the largest value..." yet gpc happily compiles code > like: > > program test(output); var i: 4..1;begin writeln(i) end. Fixed. :-) Thanks for the bug reports, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: reading from a typed file
by Peter Gerwinski 27 Nov '97

27 Nov '97

According to Kevin A. Foss: > > 1) is the following legal Pascal code? [...] No. A type `file' variable does not accept arrays of the type it was declared with for reading and writing. > 2) I take it GPC should do something more graceful than dump > core (OS/2) or give a fatal signal (Linux), even if the source is > invalid? :) This is with the 971001 beta. (kevin3.pas) Yes, that's a bug. Thanks for the report! Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: binary gpc2.0 for Solaris 2.5.1
by Peter Gerwinski 27 Nov '97

27 Nov '97

Hi, Javier! Hi, everybody! > I already compiled the gpc2.0 in a Sparcstation with Solaris 2.5.1 and I > have a binary distribution. > > What can I do for send you this file?, I thing there are many people > interested in binary from Solaris operating system. Please upload it to ftp://agnes.dida.physik.uni-essen.de/incoming/ and send me an e-mail when you have done that, so I can move it in place. > Another thing, I want to build a site gnu mirror can you help me for this > porpouse. See the GNU site for instructions, topic "Help GNU" - "mirroring". Thanks for your contribution! Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: reading from a typed file
by Dr E. Buxbaum 27 Nov '97

27 Nov '97

> program readdata(input, output, inputfile); > > var > inputfile : file of char; > temp : array[1..10] of char; > > begin > reset(inputfile, 'test'); > read(inputfile, temp); > writeln(temp); > close(inputfile); > end. try for i := 1 to 10 do read(InputFile, temp[i]); as your file is of type char, not temp. Also, I am not sure out of hand wether gpc allows writing to a file opend with Reset. Check the docs.

1 0

iso10206 Seek Functions and a couple other little things....
by Kevin A. Foss 27 Nov '97

27 Nov '97

Hi again, While I'm on the topic of exploring the file functions, does anyone want to explain the function of the various Seek* functions in extended Pascal? The descriptions in the standard contain a lot of intelligible text and little in the way of examples. I assumed that Seekread(file, n) would simply take me to the nth record in 'file,' -- which it does, but then it actually seems to stall the file pointer at n until you read two items. Take for example: program readchar(input, output, inputfile); var inputfile : file of char; letter : char; i : integer; begin reset(inputfile, 'data'); seekread(inputfile, 3); writeln(inputfile^); for i := 1 to 5 do begin read(inputfile,letter); writeln(letter); end; close(inputfile); end. Output: coltrane:~/Pascal> cat data ABCDEFGHIJKLMNOPQRSTUVWXYZ coltrane:~/Pascal> gpc readchar.pas -o readchar coltrane:~/Pascal> readchar D D D E F G coltrane:~/Pascal> I would have expected D D E F G H for output? Why does the file pointer stay at 3 for two consecutive reads? Is this a bug or am I misusing seekread()? Also isn't the typechecking of seekread a little harsh to not allow: program indexseek(input, output, inputfile); var inputfile : file [0..25] of char; begin reset(inputfile, 'data'); seekread(inputfile, 3); close(inputfile); end. when it does allow: program indexseek(input, output, inputfile); var inputfile : file [0..25] of char; index : integer = 3; begin reset(inputfile, 'data'); seekread(inputfile, index); close(inputfile); end. Various Miscellany: When I was playing around with all of this I wrote an ugly bit of code that could be reduced to: program test(output); var i : 3..3; begin i := i + 1; writeln(i); end. Why isn't there a warning about i being undefined? This code outputs 1, btw :) Lastly according to iso7185:6.4.2.4, "The first constant of a subrange-type shall specify the smallest value, and this shall be less than or equal to the largest value..." yet gpc happily compiles code like: program test(output); var i: 4..1;begin writeln(i) end. thanks for any explanations about the seekread() stuff, -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

binary gpc2.0 for Solaris 2.5.1
by Javier Medina Bautista 26 Nov '97

26 Nov '97

Hi team of gpc. My name is Javier Medina I'am the system manager at Universidad Autonoma Metropolitana in Mexico City. I already compiled the gpc2.0 in a Sparcstation with Solaris 2.5.1 and I have a binary distribution. What can I do for send you this file?, I thing there are many people interested in binary from Solaris operating system. Another thing, I want to build a site gnu mirror can you help me for this porpouse. Greetings from Mexico. ******************* Javier Medina Bautista ** ** Administrador de Sist. ** device ** E-mail:jmb@hp9000a1.uam.mx ** ** Tel: 724-45-05 ******************* Fax: 724-44-54

1 0

reading from a typed file
by Kevin A. Foss 26 Nov '97

26 Nov '97

Hello, I have a couple questions about the code sample at the bottom of this message: 1) is the following legal Pascal code? My gut feeling is that it isn't (my only other Pascal system -- albeit an interpreter, doesn't take it either), but I've never really played with typed files enough to know what to expect. 2) I take it GPC should do something more graceful than dump core (OS/2) or give a fatal signal (Linux), even if the source is invalid? :) This is with the 971001 beta. program readdata(input, output, inputfile); var inputfile : file of char; temp : array[1..10] of char; begin reset(inputfile, 'test'); read(inputfile, temp); writeln(temp); close(inputfile); end. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: Strange Behavior
by Peter Gerwinski 25 Nov '97

25 Nov '97

According to Pismo: > > > I've run into some strange behavior accessing > > > environment variables using GPC. Accessing certain > > > environment variables before others appears to clear > > > the value of others returning an empty value. > > > By shuffling the order that the following variables > > > are accessed returns all of the values. > > > > Which version of the "System" unit are you using? > > Maybe its `GetEnv' is broken and modifies the > > environment variables. > > > > It is probably best if you post the source of your > > `GetEnv' function here. > > It's the GetEnv that came in the BPCOMPAT unit. Yes, of course. :-I There are three versions of it ... Okay, I checked all their `GetEnv's, and they all seem okay for me. If you are in hurry and just want to get rid of the error, you can try and upgrade your GPC and your BPcompat library at ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ and ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/. If you want this bug really be fixed, you can help us by examining what happens to your `Gpc_envp' variable while your program calls `GetEnv'. This variable holds the address of an array of C-style strings - pointers to zero-terminated arrays of characters. * Declare it as a pointer to an array of CStrings. Type CStrArray = array [ 0..42 ] of __CString__; CStrArrayPtr = ^CStrArray; Var EnvP: __AsmName__ 'Gpc_envp' CStrArrayPtr; * While your program calls `GetEnv', examine the contents of this array - both the addresses and the values pointed to. Either use a debugger or additional `writeln' statements ... well, you know ... Good luck, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Strange Behavior
by Peter Gerwinski 24 Nov '97

24 Nov '97

According to Pismo: > > I've run into some strange behavior accessing > environment variables using GPC. Accessing certain > environment variables before others appears to clear > the value of others returning an empty value. > By shuffling the order that the following variables > are accessed returns all of the values. Which version of the "System" unit are you using? Maybe its `GetEnv' is broken and modifies the environment variables. It is probably best if you post the source of your `GetEnv' function here. Later, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: `Delay' for Linux
by Frank Heckenbach 23 Nov '97

23 Nov '97

Peter Gerwinski wrote: > > am i in > > trouble with many other > > built in functions..e.g I do need the DELAY function (i think it's built > > in) (* In BP, it's not built-in, but it's in the unit Crt. Besides, it's buggy, but that's another story... *) > > to wait a given delay time > > is this available in gpc? > > Not yet for Linux. You can use the `select' function from the > system library to implement it: Wouldn't it be easier to use usleep(3), like: procedure usleep (usec: MedCard); C; inline procedure Delay (msec: Integer); begin usleep (1000 * msec) end; This is for Linux. Other platforms may vary... -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Bill Currie has left us :-(
by Jeremy Taylor 21 Nov '97

21 Nov '97

I understand Bill has already said his goodbyes, but he asked me to make sure that he was removed from a couple of mailing lists. Bill Currie has now, sadly, left our company and so his account billc(a)blackmagic.tait.co.nz is closed. Bill would have removed himself from the lists himself but we had a wee internet connection outage right about the time he was walking out the door. I don't have detailed instructions for the list servers, but he gave me your address as someone that could remove his name from a list. If you have any questions please feel free to ask me or Bill (his new addr is bcurrie(a)tssc.co.nz)

1 0

unsubscribe & subscribe
by Achim Kalwa 20 Nov '97

20 Nov '97

Hello! Please remove my old address <achim.kalwa(a)do.netsurf.de> and add my new address <a_kalwa(a)osnabrueck.netsurf.de> Thank you! -- Achim Kalwa Tel.: +49(0)5483/74265 Hofbreede 8 Fax: +49(0)5483/74266 D-49536 Lienen mailto:achim.kalwa@osnabrueck.netsurf.de PGP Public Key available! Send mail with "send pgp key" as subject.

1 0

Re: BP string compatibility
by Peter Gerwinski 19 Nov '97

19 Nov '97

According to The African Chief: > > > and must be prevented. The Length > > field of a string should only be accessible read-only. > > I can think of many uses for this facility. Okay, but nevertheless I will fix this bug and provide a procedure to set the length instead. > BTW: the new function you refer to (AssignLength) exists in > 32-bit Delphi as "SetLength" - any chance of renaming your > function to "SetLength"? (for compatibility with Delphi). While I like the name `AssignLength' (in analogy to `AssignType') for this function, I agree that it is reasonable to rename it to `SetLength' if this means increased compatibility to other compilers (Delphi in this case). (Hmm ... maybe I should rename `AssignType' to `SetType' as well?) Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Re: your mail
by Peter Gerwinski 18 Nov '97

18 Nov '97

Hi, Jim! (What about a subject line for your mail? ;-) Hi, everybody! According to Jim Brander: > > The following program causes the compiler to crash in construct_set. Well, it does not crash my current development version of GPC, so you can either wait until we can provide a current CygWin binary distribution for you, or you can try to compile gpc-971001 by yourself. (AFAIK, you need Linux to compile GPC for CygWin.) > In addition, the > > module abc interface; > > end. > > module abc implementation; > > end. > > style of unit seems to have problems in carrying simple definitions forward, > whereas the alternative style module does not. Could you please give an example what definitions fail to be carried forward, so I can fix it for future releases of GPC? Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: undeclared identifiers
by Peter Gerwinski 18 Nov '97

18 Nov '97

According to Tom Dye: > > Oops! Another lesson learned the hard way! But it seems as if I'll have > to wait for the next beta, since neither the 971001 beta nor the patched > version will compile the code I have. Or could you recommend a previous > beta or other version that I might use in the interim? You can try previous beta versions which do not check whether the head in the interface module matches that in the implementation module. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: GPC and GPT
by Peter Gerwinski 18 Nov '97

18 Nov '97

In news:comp.lang.pascal.borland, Brian Jones <brijones(a)usa.net> wrote: > I have copies of both GPC and GPT, along with RH-IDE and the GNU binutils, > as well as almost the rest of the entire DJGPP collection. With GPT you mean the "Turbo flavour" version of GPC? This distinction only held for gpc-1.1p2; the current official version gpc-2.0 (and, of course, recent beta versions) accept Turbo Pascal source as well as ISO Pascal source. > I have tried to > write programs in Pascal using RH-IDE, and have had success getting them to > compile, but I can't get them to link (although I can get programs written > in C to link). My question is this, has anyone else had this same problem, > or does anyone know how to fix this? What error messages do you get? Did you try it from the command line? I suggest to run redir -e gpc.out gpc -v --automake <other options> yourprogram.pas and post `gpc.out' on this list (unless, of course, it is longer than I expect, which is one or two kilobytes;-). The output will help us to find and solve the problem. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

`Delay' for Linux - Re: Assign statements in GNU Pascal
by Peter Gerwinski 18 Nov '97

18 Nov '97

Hello, Badri; hello, everybody! According to Badri Gomatam: > > (i have gcc 2.7.2)...thinking "i'll just do gpc on these files and all will > be OK "...:) (Better don't think that. Even TP6 failed to recompile my TP5 sources out of the box; upgrading to BP7 was even more complicated, but the difference between 16-bit-BP and 32-bit-GPC is crucial, although we are working hard on improving compatibility.;-) > 1. ASSIGN statement appears as undeclared identifier (use this function > first.. sounds like a gcc type error for undeclared function identifiers) > isn't this a "standard" pascal fn? No, it isn't. > if not, what do i do now? Get a recent beta version of GNU Pascal which supports `Assign' from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/ which is also reachable from the GPC home page http://home.pages.de/~gnu-pascal/ > 2. all directives were flagged as errors Not *all*! ;-) > e.g {$O+ foo) was unrecognized Yes. GPC does not care about overlays and does not (yet!) check for overflowing ordinal types. > ($I+ foo) was OK, complained couldn't open the file foo.pas (which turned > out to be right).. > so the syntax of {$xx} appears to work GPC's directives are quite different from those of BP. Better write something like (*$ifdef __GPC__ *) (* Directives for GNU Pascal *) (*$N+*) (* nested comments *) (*$E+*) (* allow C-style char escapes in strings *) (*$else *) (* Directives for Borland Pascal *) (*$N+*) (* use the numeric coprocessor *) (*$E+*) (* link the emulator in case there is no coprocessor *) (*$endif *) One problem: There is no (*$ifopt FOO+- *) yet in GPC; if your programs contain this directive, you have to take them out. > does anybody know what that means, and how I could move to gpc smoothly: > is there a list of stuff in BP5.0 that's NOT in GPC and vice versa? See the GPC online documentation, `info -f gpc'. There is one chapter about differences between GPC and BP which is somehow outdated (many things which are described as "unimplemented" there are implemented now) but may still be useful for you. > am i in > trouble with many other > built in functions..e.g I do need the DELAY function (i think it's built > in) to wait a given delay time > is this available in gpc? Not yet for Linux. You can use the `select' function from the system library to implement it: (*$X+*) (* Don't warn about ignored function return value *) Type TimeValPtr = ^TimeVal; TimeVal = record sec, usec: Integer; end (* TimeVal *); Function select ( n: Integer; ReadFDS, WriteFDS, ExceptFDS: Pointer; TimeOut: TimeValPtr ): Integer; C; Procedure Delay ( ms: Integer ); Var TimeOut: TimeVal; begin (* Delay *) TimeOut.sec:= ms div 1000; TimeOut.usec:= 1000 * ( ms mod 1000 ); select ( 0, Nil, Nil, Nil, @TimeOut ); end (* Delay *); > many thanks ( and i have a feeling i'll be posting many msgs to this forum) Be welcome! :-) Hmm ... you will probably miss the BP standard units for GPC running on Linux. If you want to contribute to GPC, you can download the `BPcompat' package (written for DOS/DJGPP) from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/contrib/ and try to get as much as possible run on Linux. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

BP string compatibility
by Frank Heckenbach 18 Nov '97

18 Nov '97

The African Chief wrote: > Problem: > Under BP, one can do; > Var S:String; > Count:Integer; > .... > Dec(S[0], Count); > > This does not compile under GPC, but "Dec(Length(S), Count)" > compiles, and seems to work okay. Then I think this is a bug in GPC, and must be prevented. The Length field of a string should only be accessible read-only. However, there is (in the current developer version, not yet in the last beta) a built-in function AssignLength which is the proper way to directly wirte to the length field of a string (if messing with the length can be called proper at all... ;-) > Observation: > This is an incompatbility b/w BP and GPC - probably > because of the way strings are implemented under GPC. Right. > Questions: > 1. Is GPC ever going to support the BP syntax "Dec(S[0], Count);" > ? Short answer, yes, sometime. More details can be found in some other discussions in the list. > 2. Is it desirable to do so ? Yes. Mainly for the reason you described. > (obviously this would entail changes to the internal GPC string > format ???) Not changes to the "real" Pascal strings; rather, it would mean introducing a new string type with automatic conversions as far as possible. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

2 1

BP string compatibility
by The African Chief 18 Nov '97

18 Nov '97

Hi all Problem: Under BP, one can do; Var S:String; Count:Integer; .... Dec(S[0], Count); This does not compile under GPC, but "Dec(Length(S), Count)" compiles, and seems to work okay. Observation: This is an incompatbility b/w BP and GPC - probably because of the way strings are implemented under GPC. Questions: 1. Is GPC ever going to support the BP syntax "Dec(S[0], Count);" ? 2. Is it desirable to do so ? (obviously this would entail changes to the internal GPC string format ???) Best regards, The Chief -------- Dr. Abimbola A. Olowofoyeku (The African Chief) Email: laa12(a)keele.ac.uk Homepage: http://ourworld.compuserve.com/homepages/African_Chief/ Author of: Chief's Installer Pro 4.01 for Win16 and Win32: http://www.simtel.net/pub/simtelnet/win3/install/chief401.zip

1 0

None
by Jim Brander 18 Nov '97

18 Nov '97

Further to the previous message about a problem with sets in the cygwin version. The following program causes the compiler to crash in construct_set. The crash does not occur if the set definition is directly in the program rather than imported. The crash occurs whether the interface is in the same or separate files. # 1 "/Orion/pas/creatvar.pas" module data1 interface; export data1_interface = (usage1); type usage1 = (sysusage,sysgen,syscopy,master); end. module creatvar; export creatvar_int = (create_var); import data1_interface; procedure create_var(use1:usage1);C; end; procedure create_var; var i,j,k,l:integer; begin if not (use1 in [syscopy,sysgen]) {<<<<<<<<<-------<} then begin end; end; end. In addition, the module abc interface; end. module abc implementation; end. style of unit seems to have problems in carrying simple definitions forward, whereas the alternative style module does not. Regards Jim Brander

1 0

Assign statements in GNU Pascal
by Badri Gomatam 18 Nov '97

18 Nov '97

Hello all: I am new to gnu pascal, so this is a newbie question: I have a _ton_ of code written ca. 1992/3 on Borland Pascal 5.0 which for various reasons I need to port to a Unix environment: the present version runs on DOS: I downloaded the binary for linux-(i386) and installed on my linux box..no problems (at least, not yet:) (i have gcc 2.7.2)...thinking "i'll just do gpc on these files and all will be OK "...:) when i compiled one of the (several hundred) files i have in my legacy code (for which the programmer has left and gone to a better life on another planet) I got errors involving the following: 1. ASSIGN statement appears as undeclared identifier (use this function first.. sounds like a gcc type error for undeclared function identifiers) isn't this a "standard" pascal fn? if not, what do i do now? 2. all directives were flagged as errors e.g {$O+ foo) was unrecognized ($I+ foo) was OK, complained couldn't open the file foo.pas (which turned out to be right).. so the syntax of {$xx} appears to work basically i don't really know what the $O+ does..besides being called an overlay: this entire body of code apparently has to be compiled in Borland Pascal with "Overlay ON"... does anybody know what that means, and how I could move to gpc smoothly: is there a list of stuff in BP5.0 that's NOT in GPC and vice versa? am i in trouble with many other built in functions..e.g I do need the DELAY function (i think it's built in) to wait a given delay time is this available in gpc? many thanks ( and i have a feeling i'll be posting many msgs to this forum) badri

1 0

Re: undeclared identifiers
by Peter Gerwinski 17 Nov '97

17 Nov '97

Hi, Tom! Hi, all! According to Tom Dye: > > A while back I forwarded a bit of extended Pascal code that I thought > should compile with gpc, but doesn't. > [...] > I suspect that I have found something that gpc does not do correctly, ... Indeed, but I have posted a patch to `module.c' at this list on 10 November that fixes the problem (and causes some others which are fixed meanwhile in my development version;-). Your example modules work fine on my Linux box. > ..., but I am far from confident that my suspicion is correct. > Here are my other suspicions: > > a) I don't have gpc built correctly. I had some problems getting gpc to > compile on my Linux box and can't really say what I did to make it > compile--that is which change really made a difference. Could I be having > problems with an incorrectly built gpc? Did you apply the patch from 10 November? (But don't throw your working GPC away because the patch causes other problems which will be fixed in the next beta release.) > b) the code in examples 1) and 3) relies on a feature of extended Pascal > that gpc does not yet implement. I am relatively new to gpc and to > extended Pascal and can't answer this one myself. Does the code in > examples 1) and 3) fail because of an unimplemented feature of extended > Pascal? No. The last of the features needed to compile 3), export renaming, was implemented into GPC somewhere in spring 1997. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

None
by chris＠bockermann.ping.de 17 Nov '97

17 Nov '97

Subject: Re: Dodgy email To: richard.kerry(a)quantel.com Date: Mon, 17 Nov 1997 15:14:18 +0100 (MET) From: "Christian Bockermann" <chris(a)bockermann.ping.de> Cc: gpc(a)hut.fi In-Reply-To: <80256552.00422CA2.00(a)buffer1.quantel.com> from "richard.kerry(a)quantel.com" at Nov 17, 97 12:08:55 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 826 Hello ! Richard.Kerry(a)Quantel.com wrote : > > Does anyone recognize any of the names in the following extract : > > ------------------------- Could not deliver Message to > ------------------------- > CN=??r J Rodriguez/O=almenna kerfisfraedistofan@almenna kerfisfraedistofan > > User ??r J Rodriguez/almenna kerfisfraedistofan@almenna kerfisfraedistofan > not > > ------------------------- > > I am getting this whenever I send a message to the mailing list. I am told > that the names are not in the list explicitly. Does anyone have them in a > sub-list ? Or recognize them from anwhere else ? Yes ! I get the same error-message when sending e-mail to the list ! I also do not know why ... :-( -- Chris e-mail > chris(a)bockermann.ping.de ____________________________________ (subject "send pgp-key" for pgp-key)

1 0

Re: `case' statments: `default' and `others'
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Peter Wrote: According to richard.kerry(a)quantel.com: > [`begin/end' after `otherwise' ...] > [...] > Oh, and the lack of trailing colon is easier as that's the way Oregon has > it. Again, if it's optional it doesn't matter. Just to be sure that I have understood everything correctly: It is okay for you if we drop the colon after `otherwise' (i.e. forbid it) as long as we do not forbid a `begin/end' pair after `otherwise'? ------- That is correct. Oregon has no colon, and has 'statement' not 'statement-list' ie. it requires begin/end if there is more than one statement. It always has the Otherwise after all the cases. Richard.

1 0

Dodgy email
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Does anyone recognize any of the names in the following extract : ------------------------- Could not deliver Message to ------------------------- CN=??r J Rodriguez/O=almenna kerfisfraedistofan@almenna kerfisfraedistofan User ??r J Rodriguez/almenna kerfisfraedistofan@almenna kerfisfraedistofan not ------------------------- I am getting this whenever I send a message to the mailing list. I am told that the names are not in the list explicitly. Does anyone have them in a sub-list ? Or recognize them from anwhere else ? Richard.

1 0

Re: `case' statments: `default' and `others'
by Peter Gerwinski 17 Nov '97

17 Nov '97

According to richard.kerry(a)quantel.com: > [`begin/end' after `otherwise' ...] > [...] > Oh, and the lack of trailing colon is easier as that's the way Oregon has > it. Again, if it's optional it doesn't matter. Just to be sure that I have understood everything correctly: It is okay for you if we drop the colon after `otherwise' (i.e. forbid it) as long as we do not forbid a `begin/end' pair after `otherwise'? So it will be correct to write case foo of 1: writeln ( 'foobar!' ); otherwise writeln ( 'foo?' ); writeln ( 'bar!' ); end (* case *); as well as case foo of 1: writeln ( 'foobar!' ); otherwise begin writeln ( 'foo?' ); writeln ( 'bar!' ); end (* otherwise *); end (* case *); but GPC will reject case foo of 1: writeln ( 'foobar!' ); otherwise: writeln ( 'foo?' ); writeln ( 'bar!' ); end (* case *); or case foo of 1: writeln ( 'foobar!' ); otherwise: begin writeln ( 'foo?' ); writeln ( 'bar!' ); end (* otherwise *); end (* case *); or case foo of otherwise: begin writeln ( 'foo?' ); writeln ( 'bar!' ); end (* otherwise *); 1: writeln ( 'foobar!' ); end (* case *); Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: `case' statments: `default' and `others'
by richard.kerry＠quantel.com 17 Nov '97

17 Nov '97

Peter Wrote : I am currently fixing the bug with `otherwise' in `case' statements. While the ISO 10206 Extended Pascal standard wants case foo of (* 1 *) bar: writeln ( 'foobar!' ); otherwise write ( 'The answer is: ' ); writeln ( answer ); end (* case *); GPC implemented case foo of (* 2 *) bar: writeln ( 'foobar!' ); otherwise: begin write ( 'The answer is: ' ); writeln ( answer ); end (* otherwise *); end (* case *); which is simply wrong. Okay - when I fix it, does anybody want to keep an optional colon after `otherwise'? Or after `else' in the Borland syntax? (I would prefer if *not*.) --------- surely, since you need begin/end in : case foo of (* 1 *) bar: begin writeln ( 'foobar!' ); writeln ( 'again' ); end; you should need them in : otherwise: begin write ( 'The answer is: ' ); writeln ( answer ); end (* otherwise *); Having said that, it doesn't matter unless you explicitly stop them being usable there, but since you'd be making it accept statement-list rather than statement it'll still be usable. (I have three-hundred plus modules to convert so I look very carefully at suggestions to restrict the syntax accepted.) Oh, and the lack of trailing colon is easier as that's the way Oregon has it. Again, if it's optional it doesn't matter. -------------- Peter Wrote : I also found `default' and `others' as synonyms for `otherwise' which I would like to remove. what about removing `&' as an address operator and to keep only the BP-compatible `@'? -------------- These are ok by me as our Oregon-to-gpc translator can do these either way, and Oregon uses Otherwise. Richard.

1 0

undeclared identifiers
by Tom Dye 16 Nov '97

16 Nov '97

Hello all, A while back I forwarded a bit of extended Pascal code that I thought should compile with gpc, but doesn't. This is example 1) below. gpc complains that the identifier `I' is not declared and goes on to complain about the comparison of I with 2 not being a boolean type. I've been tinkering to see if I can figure out what is going on and found that I can get the code to compile if I use the module-declaration = module-heading[ `;' module-block] form rather than the module-declaration = module-heading module-identification `;' module-block form. The modified code from example 1) is given as example 2). This compiles without warnings. I couldn't find anything in the standard about when to use one form of module and when to use the other, so I typed in some of the code examples provided with the standard to see how gpc performs with (hopefully) correct extended Pascal code. I discovered that gpc compiles almost everything that I tried. It does not compile the example module `generic-sort' that is given on pages 129-130 of the standard. For convenience, I include this code as example 3). This code fails to complile with message that `greater' and `swap' are undeclared identifiers, which reminds me of the messages reported for example 1). This module also uses the module-declaration = module-heading module-identification `;' module-block form. I suspect that I have found something that gpc does not do correctly, but I am far from confident that my suspicion is correct. Here are my other suspicions: a) I don't have gpc built correctly. I had some problems getting gpc to compile on my Linux box and can't really say what I did to make it compile--that is which change really made a difference. Could I be having problems with an incorrectly built gpc? b) the code in examples 1) and 3) relies on a feature of extended Pascal that gpc does not yet implement. I am relatively new to gpc and to extended Pascal and can't answer this one myself. Does the code in examples 1) and 3) fail because of an unimplemented feature of extended Pascal? Thanks for your help! Tom Thomas S. Dye, Ph.D. Home: 813 16th Avenue, Honolulu, Hawaii 96816. Voice (808) 734-2087. Work: International Archaeological Research Institute, Inc., 949 McCully St., Suite 5, Honolulu, Hawaii 96826. Voice (808) 946-2548; Fax 943-0716. Example 1) module charbug interface; export charbug = (IsAlphaNum); function IsAlphaNum (ch : char; i : integer) : boolean; end. module charbug implementation; function IsAlphaNum; begin if i > 2 then IsAlphaNum:= ch in ['A'..'Z','a'..'z','0'..'9']; end; end. Example 2) module charbug; export charbug = (IsAlphaNum); function IsAlphaNum (ch : char; i : integer) : boolean; end; function IsAlphaNum; begin if i > 2 then IsAlphaNum:= ch in ['A'..'Z','a'..'z','0'..'9']; end; end. Example 3) module generic_sort interface; export generic_sort = (do_the_sort, max_sort_index, protected current_pass => number_of_passes, protected swap_occurred_during_sort); type max_sort_index = 1..maxint; procedure do_the_sort(element_count : max_sort_index; function greater(e1, e2 : max_sort_index) : boolean; procedure swap(e1,e2 : max_sort_index) ); var current_pass : 0..maxint value 0; swap_occurred_during_sort : boolean value false; end. module generic_sort implementation; procedure do_the_sort; var swap_occurred_this_pass : boolean; n : max_sort_index; begin current_pass := 0; swap_occurred_during_sort := false; repeat swap_occurred_this_pass := false; current_pass := current_pass + 1; for n := 1 to element_count - 1 do if greater(n, n + 1) then begin swap(n, n + 1); swap_occurred_this_pass := true; end; swap_occurred_during_sort := swap_occurred_during_sort or swap_occurred_this_pass; until not swap_occurred_this_pass; end; { do_the_sort } end.

1 0

Re: size of strings (was without subject)
by Peter Gerwinski 16 Nov '97

16 Nov '97

According to Kevin A. Foss: > > [...] Just wondering, but do you realize that if you define > rec as a packed record, you apparantly lose this additional byte. This > doesn't really hurt much as the chr(0) isn't used yet, but I don't know > if it will cause problems down the road. Sorry - I forgot: The change was on 31 October, so in fact *you* get a size of 16 due to 32-bit alignment, and *I* get a size of 16 due to that additional byte. (-; With `String ( 4 )' instead of `String ( 3 )', the current beta version will still reserve 16 bytes while my development version will reserve 20 (due to the 32-bit alignment). :-) (Yes, I want to release the next (final?) beta soon, but I don't dare to promise a date due to some bad experience ... ;-) Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Variant records (was without subject)
by Peter Gerwinski 16 Nov '97

16 Nov '97

According to Christian Bockermann: > > I have a little question concerning variant records and packed arrays. [...] According to myself (Peter Gerwinski): > > !! You have discovered a bug in GPC: The compiler had forgotten to store > the capacity of the string in the variant record. I will fix it as > soon as possible - thanks for the report. > > To work around, manually assign `x.rec.name.capacity:= 3' before you > assign a value to `x.rec.name'. Here is the fix: In `util.c', function `contains_file_or_schema_p()', change case RECORD_TYPE: to case RECORD_TYPE: case UNION_TYPE: Then it works. Greetings, Peter PS to Christian: Gib Deinen E-Mails besser ein "Betreff". ;-) Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: your mail
by Kevin A. Foss 16 Nov '97

16 Nov '97

On Sun, 16 Nov 1997 18:00:03 +0100 (MET), Peter Gerwinski wrote: > * Recent beta versions of GPC reserve one additional byte in each string > for appending a `chr ( 0 )' character for sake of compatibility to C > - which is not yet used. In future versions, byte 11 will be zero, and > only byte 12 will have random bits when the length of the string is `2'. > (That's why the size of the string is 12, not 11.) I've been playing around with this example... for some reason it interests me. :) Just wondering, but do you realize that if you define rec as a packed record, you apparantly lose this additional byte. This doesn't really hurt much as the chr(0) isn't used yet, but I don't know if it will cause problems down the road. E.g. if you put 'ABC' into the string instead of 'AB' you see the bits for the letters but there is no 12th random bits byte, and sizeof(x.rec) yields 15. Should it preserve the byte even when the string is part of a packed record? -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: your mail
by Peter Gerwinski 16 Nov '97

16 Nov '97

Hallo, Christian! Hello, everybody! According to Christian Bockermann: > > I have a little question concerning variant records and packed arrays. In schoolwe wrote a little program with a declaration part like this : > > var > x : RECORD > CASE Boolean OF > False :( > rec:Record > name : String[3]; > number : integer; > end); > true :( > field:packed array [0..47] of boolean > ); > end; > > [...] > > So I expected the output to be > 1.) the binary decoding of the length of the string, like > 00000010 > 2,3.) binary decoding of the ascii-code of the characters in the string, like > 01000001 01000010 > 4.) some 8 random bits > 01010101 or something similar... > 5.) the 16-bit decoding of the integer variable, like > 00000000 00001001 The output depends on the internal representation of strings and integers in your particular Pascal compiler. The result you expected is okay for Borland Pascal and obviously for Think Pascal as well, but GNU Pascal uses a different scheme to represent strings and integers. If you examine `SizeOf ( x.rec.name )' and `SizeOf ( x.rec.number )' you will see that they are 12 and 4, not 4 and 2. The "12" is because GPC's strings comply to the ISO-10206 standard for Extended Pascal which (a) requires that the "capacity" (maximum length) of the string is stored in the variable and (b) does not limit the length of the string to 255 characters. This way, we have an overhead of two integers instead of one byte in the string. The "4" is because GPC is a 32-bit compiler, so `Integer' has four bytes instead of two. (And `LongInt' has eight bytes instead of four.) So you have to replace `0..47' by `0..127', and the expected result reads 1..4: the binary decoding of the capacity (3) of the string, like 11000000 00000000 00000000 00000000 5..8: the binary decoding of the current length (2) of the string, like 01000000 00000000 00000000 00000000 9..10: the binary decoding of the ascii-code of the characters in the string, like 10000010 01000010 11..12: some 16 random bits 01010100 00000000 13..16: the 32-bit decoding of the integer variable, like 10010000 00000000 00000000 00000000 Remarks: * Intel processors store the least-significant byte first ("little-endian"), so `9' becomes 10010000 0 0 0, not 0 0 0 10010000. The Mac, AFAIK, has a 68k processor which does it vice versa ("big-endian"). * Recent beta versions of GPC reserve one additional byte in each string for appending a `chr ( 0 )' character for sake of compatibility to C - which is not yet used. In future versions, byte 11 will be zero, and only byte 12 will have random bits when the length of the string is `2'. (That's why the size of the string is 12, not 11.) !! You have discovered a bug in GPC: The compiler had forgotten to store the capacity of the string in the variant record. I will fix it as soon as possible - thanks for the report. To work around, manually assign `x.rec.name.capacity:= 3' before you assign a value to `x.rec.name'. !! You have discovered yet another bug in GPC: Accessing the packed array does not work correctly. Below is a patch to `types.c' which fixes the problem for Linux on the PC. (It may cause alignment problems on the Alpha; I will have to check ...) * It is planned for gpc-2.2 to implement that sort of strings used in Borland Pascal and Think Pascal as a new data type `ShortString'. > Does anybody know, what I did wrong ? Nothing. :-) Only one hint: Always avoid doing assumptions on the internal representation of data in your programs, if possible. > Is it possible in another way to access > and change some bits of a string of any other variable with the use of GPC ? Yes: GPC implements Borland's `absolute' directive: Var Name: String ( 3 ); (* Extended Pascal wants `String ( 42 )', *) (* not `String [ 42 ]'. *) Bits: packed array [ 0..95 ] of Boolean absolute Name; This means that `Name' and `Bits' share the same location in memory. But we do not want to rely on the internal structure of `Name', thus it is cleaner to write Bits: packed array [ 0..BitSizeOf ( Name ) - 1 ] of Boolean absolute Name; Then `Bits' will always have the correct size. Other methods to access bits are * Sets. A set is in fact an array of bits, indexed with the element type. Those bits whose indices are elements of the set are 1, the others are 0. * Bit masking. You can apply the (bitwise) `and' operator to a pair of integer values. If you want, for instance, to check whether the third bit (i.e. bit number 2) in a given integer `k' is set, you can write: if k and 8 = 0 then ... To test the `n + 1'th bit (i.e. the bit number `n') use if k and ( 1 shl n ) = 0 then ... with `shl' being the "shift left" operator. This is how packed arrays of Boolean as well as sets work internally. Greetings - and thanks for the bug reports, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005] 8< ---- gpc.diff ------------------------------------------------------------- To apply this patch, cd to the GPC source directory (a subdirectory `p' of the GCC source directory) and type patch -p1 < gpc.diff --- ../../gpc-971112/p/types.c Thu Nov 6 17:52:11 1997 +++ types.c Sun Nov 16 19:13:46 1997 @@ -1895,23 +1908,26 @@ * shift operations here. */ unsigned HOST_WIDE_INT imask; + tree long_type = TREE_INT_CST_LOW (bits) >= HOST_BITS_PER_WIDE_INT / 2 + ? long_long_unsigned_type_node + : unsigned_type_node; tree mask; - tree host_bits_per_wide_int = - build_int_2 (HOST_BITS_PER_WIDE_INT, 0); - tree ull_ptr = build_pointer_type (long_long_unsigned_type_node); + tree half_bits_per_long_type = build_int_2 (TYPE_PRECISION (long_type) / 2, 0); + tree half_bytes_per_long_type = build_int_2 (TYPE_PRECISION (long_type) / (2 * BITS_PER_UNIT), 0); + tree ull_ptr = build_pointer_type (long_type); tree offset = build_binary_op (FLOOR_MOD_EXPR, index, - host_bits_per_wide_int, 0); - index = build_binary_op (TRUNC_DIV_EXPR, index, - host_bits_per_wide_int, 0); + half_bits_per_long_type, 0); + index = build_binary_op (FLOOR_DIV_EXPR, index, + half_bits_per_long_type, 0); imask = ((unsigned HOST_WIDE_INT) ~0) - >> (HOST_BITS_PER_WIDE_INT - TREE_INT_CST_LOW (bits)); + >> (TYPE_PRECISION (long_type) - TREE_INT_CST_LOW (bits)); mask = build_int_2 (imask, 0); mask = build_binary_op (LSHIFT_EXPR, mask, offset, 0); var_access = convert_array_to_pointer (var_access); var_access = convert (string_type_node, var_access); var_access = build_binary_op (PLUS_EXPR, var_access, build_binary_op (MULT_EXPR, index, - host_bits_per_wide_int, 1), 1); + half_bytes_per_long_type, 1), 1); var_access = convert (ull_ptr, var_access); var_access = build_indirect_ref (var_access, "packed array access"); var_access = build_binary_op (BIT_AND_EXPR, var_access, mask, 1);

1 0

Re: getting at the bits [was: (null)]
by Kevin A. Foss 16 Nov '97

16 Nov '97

Christian Bockermann wrote: >Hello everyone ! Hiya. >var > x : RECORD > CASE Boolean OF > False :( > rec:Record > name : String[3]; > number : integer; > end); > true :( > field:packed array [0..47] of boolean > ); > end; If you do a writeln(sizeof(x)); you'll find GPC is making this a lot longer than 6 bytes long -- it shows up as 16 on my system. I think this has to do with the other fields that GPC uses for the string type (e.g. .Capacity), although that doesn't explain all of the length and even with a 128 bit field I don't see much. I'm sure someone else (Peter?) knows what is going on. I was able to get the code to do something intelligible If I change your record definition to: [...] rec: packed record name : packed array[0..2] of char; number : integer(16); [...] field:packed array [0..39] of boolean and fixed the loop to go through 40 bits. I get a nice little 5 byte structure and the output is: binary decoding : 10000010 01000010 00000100 10010000 00000000 Note that the end of the byte is different as the left most bit is the 1 bit -- gpc fills in a space for the undefined character, and you loose the length field because I used a standard Pascal string. Hope that is of some help, -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

None
by chris＠bockermann.ping.de 16 Nov '97

16 Nov '97

Subject: variant records and packed arrays To: gpc(a)hut.fi Date: Sun, 16 Nov 1997 13:12:13 +0100 (MET) From: "Christian Bockermann" <chris(a)bockermann.ping.de> X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1971 Hello everyone ! I have a little question concerning variant records and packed arrays. In schoolwe wrote a little program with a declaration part like this : var x : RECORD CASE Boolean OF False :( rec:Record name : String[3]; number : integer; end); true :( field:packed array [0..47] of boolean ); end; The consequence was that the record (rec) and the array (field) were settled in the same area in memory. So this area could be interpreted as a field of bits or a record of a string an an integer variable. This was done on a Mac with Think Pascal :-(, but I'm unable to do something like this on my Linux-Box. The rest of my program looks like this : procedure print_out; var i :integer; begin write('binary decoding :'); for i:=0 to 47 do begin if x.field[i] then write('1') else write('0'); if i MOD 8 = 7 then write (' '); end; end; begin x.rec.name:='AB'; x.rec.number:=9; writeln(x.rec.name, x.rec.number); print_out; end. So I expected the output to be 1.) the binary decoding of the length of the string, like 00000010 2,3.) binary decoding of the ascii-code of the characters in the string, like 01000001 01000010 4.) some 8 random bits 01010101 or something similar... 5.) the 16-bit decoding of the integer variable, like 00000000 00001001 The output I get is : 1.) 2.) 3.) 4.) 5.) 6.) binary decoding :00000000 00000000 00000000 00000001 10000000 00000000 Does anybody know, what I did wrong ? Is it possible in another way to access and change some bits of a string of any other variable with the use of GPC ? If anybody can help ... THANKS a lot !! -- Chris e-mail > chris(a)bockermann.ping.de ____________________________________ (subject "send pgp-key" for pgp-key) -- Bis denn, Chris e-mail > chris(a)bockermann.ping.de ____________________________________ (subject "send pgp-key" for pgp-key)

1 0

`case' statments: `default' and `others'
by Peter Gerwinski 15 Nov '97

15 Nov '97

Hello, everybody! I am currently fixing the bug with `otherwise' in `case' statements. While the ISO 10206 Extended Pascal standard wants case foo of (* 1 *) bar: writeln ( 'foobar!' ); otherwise write ( 'The answer is: ' ); writeln ( answer ); end (* case *); GPC implemented case foo of (* 2 *) bar: writeln ( 'foobar!' ); otherwise: begin write ( 'The answer is: ' ); writeln ( answer ); end (* otherwise *); end (* case *); which is simply wrong. Okay - when I fix it, does anybody want to keep an optional colon after `otherwise'? Or after `else' in the Borland syntax? (I would prefer if *not*.) I also found `default' and `others' as synonyms for `otherwise' which I would like to remove. May I? Or are they needed for compatibility with some Pascal compiler I am not aware of? If so, what is the syntax? Example 1 or 2 above? While I am on it, what about removing `&' as an address operator and to keep only the BP-compatible `@'? Please post your opinions here. Thanks, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Re: probs compiling current beta GPC
by Peter Gerwinski 15 Nov '97

15 Nov '97

According to Clyde Meli: > > Now I attempted to compile the beta but I ran into problems again, this time > with parse.y (I've recompiled bison again - version 1.25 - from what I tried > to check I found it should be the latest version) and using the new > parse.h which you gave me. Now I got the following errors: > [...] > parse.y:752: warning: implicit declaration of function `pedwarn' > parse.y:755: warning: implicit declaration of function `initialize_module' > parse.y:756: `current_module' undeclared (first use this function) This looks for me as if your `parse.c' does not include the correct header files. Maybe your `bison' behaves different than mine and stores `#include's in `parse.h' rather than `parse.c', so my version of `parse.h' does not work with your `parse.c'? To proceed, I suggest to `mv' away `parse.c' and my `parse.h' and to reconstruct both with your `bison'. Also check which files your `parse.c' does `#include'. Hope this helps a little, :-/ Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Type conversions
by Peter Gerwinski 15 Nov '97

15 Nov '97

According to Hans Ecke: > > I think I was a little bit lazy in my question. Of course I meant: What is > the schema of type conversion between the members of the ordinal,real and > string type familys. I.e. what happens internally and what does the > compiler ... This is a nontrivial question. The complete answer is the function `convert_for_assignment()' in the GPC source file `gpc-typeck.c'. When passing parameters, other conversions are made, see the function `convert_arguments()', also in `gpc-typeck.c'. Just a few general guidelines: - Strings are truncated, where necessary. - According to Extended Pascal, char variables may get a string value assigned :-( which results in the assignment of the first character or a space in case of the empty string. (GPC warns about this.;-) - If you assign a value to a variable of a compatible, but shorter type, *no* run-time checks are currently done to ensure that the result will fit in the variable. This is planned for gpc-2.2. > ... if there are lines like > > var i:integer; > l:longint; > > r:real; > e:extended; > > s:string(255); > p:pchar; > begin > i:=l; Silently truncated; overflows are not caught. > e:=r; Works without problem. (`Extended' may also be called `LongReal'.) > p:=s; This works if you enable extended syntax (*$X+*). Then the pointer will point to the first character in the string; the capacity and the length of the string are ignored. Please not that GPC does *not* (yet!;-) automatically append a `chr ( 0 )' to the string. > end. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Type problem
by Peter Gerwinski 15 Nov '97

15 Nov '97

According to Jim Brander: > > The cygwin32 version of gpc > gives "invalid operands to binary = " > for comparison of types in following test program. The compiled CygWin32 version of GPC is a little behind the current (beta) state, sorry. The program works well with more recent versions of GPC. Until a recent CygWin32-GPC will be available, maybe an explicit type cast will help? I know that older versions of GPC have problems with subranges of enumerated types ... Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Bug report
by Frank Heckenbach 15 Nov '97

15 Nov '97

Krzysztof Gozdziewski wrote: > I have found a strange behaviour of the gpc compiler, > when reading real numbers, having the form > x.xxe+00 > They are converted to 0. > > [...] > > /home/chris/Gravity>gpc --version > 2.0(2.7.2.1) GPC 2.0 is quite an old version (almost a year old now...). I recently rewrote the reading of real numbers completely, and with my code, your example works fine. The new code is not yet present in the latest beta version in GPC, but will be there in the next version to appear. It will be announced here in the list, not too far in the future, I think. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Bug report
by Krzysztof Gozdziewski 15 Nov '97

15 Nov '97

Hello! I have found a strange behaviour of the gpc compiler, when reading real numbers, having the form x.xxe+00 They are converted to 0. The sample session follows. Thanks. Krzysztof Gozdziewski /home/chris/Gravity>uname -a Linux ecia 2.0.30 #2 Sat Sep 27 15:42:44 MET DST 1997 i486 /home/chris/Gravity>gpc --version 2.0(2.7.2.1) /home/chris/Gravity>more test.p program testbug; var a : real; begin writeln('Enter 1.0e+00 to reproduce the error'); readln( a ); writeln( 'a = ', a ); end. /home/chris/Gravity>gpc test.p /home/chris/Gravity>a.out Enter 1.0e+00 to reproduce the error 1.0e+00 a = 2.1883084e-314 /home/chris/Gravity>a.out Enter 1.0e+00 to reproduce the error 2 a = 2.0000000e+00 -- ^-^ ~ Krzysztof Gozdziewski (o o) ~ Torun Centre for Astronomy =*= ~ Gagarina 11, PL-87-100 Torun, POLAND (m_m) ~ http://www.astri.uni.torun.pl/~chris

1 0

Type problem
by Jim Brander 15 Nov '97

15 Nov '97

Many thanks for directions to obtaining cygwin version of gpc. The cygwin32 version of gpc gives "invalid operands to binary = " for comparison of types in following test program. program testtype; type logstate1= (nyk1,uke1,error1,false_p1,true_p1); array_record1 = record state1: logstate1; actual : real; end; type info_array1 = array[0..100] of array_record1; var pinfo:info_array1; begin if (pinfo[3].state1 = nyk1) then pinfo[3].state1 := nyk1; if (pinfo[3].actual = 123.0) then pinfo[3].actual := 456.0; end. Regards Jim Brander

1 0

Type conversions (was: 2 suggestions about Units)
by Peter Gerwinski 14 Nov '97

14 Nov '97

According to Hans Ecke: > > [...] > > A last question: What is the schema of the automatic type-conversion? Is > there a global schema for converting between ordinal,real and string types > or is it only done from case to case? What do you mean by "automatic type-conversion" between ordinal, real, and string types? Assignments like "ordinal:= real" or "string:= integer" are - of course - simply illegal in Pascal. You can assign an integer to a real, but not vice versa. Am I missing something? Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Variant records, my bad =B)...
by Orlando Llanes 13 Nov '97

13 Nov '97

A short time ago, I said that there was a quirk in BP's SizeOf when it comes to variant records. I haven't tested it in GPC, tho I'm sure it works the same. But I digress, the point is that when I saw the CASE ... structure in other Pascal programs, it must've reported a bigger size because one of the field blocks was bigger than the rest. Hence my calling it a quirk, but as it turns out, it's not a quirk, so I will now go boot myself in the rear now :P See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

1 0

Goodbye, but I'll be back
by Bill Currie 13 Nov '97

13 Nov '97

Well, goodbye. I'm leaving my (now ex) employer and going on to a new on. I should be back on the net soon and I will send posts to the appropriate places when I get my new address. It's been nice knowing you and being part of the djgpp community for the last 2.5 years and gpc for 0.5 years. For anyone trying to get in touch with me, just send posts to djgpp and I'll check the archives (assuming I have web access). Well anyway, goodbye, good luck, and good hacking. Bill -- Leave others their otherness.

1 0

Re: probs compiling current beta GPC
by Clyde Meli 13 Nov '97

13 Nov '97

> According to Clyde Meli: > > /usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.3/include/unistd.h:230: conf > > licting types for `rename' > > /usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.3/include/stdio.h:161: previ > > ous declaration of `rename' > > It seems as if the (AutoConf) configuration script did not recognize > your system correctly. Please try and edit `gpc-config.h' manually > and flip the `HAVE_UNISTD_H' switch. > > Good luck, > > Peter > > Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer > peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] > maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005] > I found what was confusing AUTOCONF - I did not set the CC environment variable (I never did and I never had problems :) ) to /usr/local/bin/gcc (or wherever gcc is located). I recompiled the C compiler now using the precompiled gcc 2.7.2.1 package available on the net. Now I attempted to compile the beta but I ran into problems again, this time with parse.y (I've recompiled bison again - version 1.25 - from what I tried to check I found it should be the latest version) and using the new parse.h which you gave me. Now I got the following errors: # make LANGUAGES=pascal CC=/usr/local/bin/gcc cd p; make "AR_FLAGS=rc" "AR_FOR_TARGET=/usr/local/sparc-sun-solaris2.5.1/bin/ar " "BISON=bison" "BISONFLAGS=" "CC=/usr/local/bin/gcc" "CFLAGS=-g" "GCC_FOR_TARGE T=./xgcc -B./" "LDFLAGS=" "LEX=flex" "LEXFLAGS=" "MAKEINFO=makeinfo" "MAKEINFOFL AGS=" "RANLIB_FOR_TARGET=/usr/local/sparc-sun-solaris2.5.1/bin/ranlib" "RANLIB_T EST_FOR_TARGET=[ -f /usr/local/sparc-sun-solaris2.5.1/bin/ranlib ]" "SHELL=/bin/ sh" "exeext=" "objext=.o" "exec_prefix=/usr/local" "prefix=/usr/local" "tooldir= /usr/local/sparc-sun-solaris2.5.1" "bindir=/usr/local/bin" "libsubdir=/usr/local /lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.3" "CROSS=" "AR_FLAGS=rc" "AR_FOR_TARG ET=/usr/local/sparc-sun-solaris2.5.1/bin/ar" "BISON=bison" "BISONFLAGS=" "CFLAGS =-g" "X_CFLAGS=-DSVR4" "LDFLAGS=" "LEX=flex" "LEXFLAGS=" "MAKEINFO=makeinfo" "MA KEINFOFLAGS=" "MAYBE_TARGET_DEFAULT=" "MAYBE_USE_COLLECT2=" "RANLIB_FOR_TARGET=/ usr/local/sparc-sun-solaris2.5.1/bin/ranlib" "RANLIB_TEST_FOR_TARGET=[ -f /usr/l ocal/sparc-sun-solaris2.5.1/bin/ranlib ]" "SHELL=/bin/sh" "bindir=/usr/local/bin " "exec_prefix=/usr/local" "gxx_include_dir=/usr/local/lib/g++-include" "include dir=/usr/local/include" "libsubdir=/usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1 /2.7.2.3" "prefix=/usr/local" "target_alias=" "tooldir=/usr/local/sparc-sun-sola ris2.5.1" "gpc_version=971001" "rts_version=2.8" "version=2.7.2.3" ../gpc1 make[1]: Entering directory `/usr1/local/src/GNU/SOURCE/gcc-2.7.2.3/p' /usr/local/bin/gcc -c -DIN_GCC -DGPC -DSVR4 -g -Wall \ -I. -I.. -I. -I./.. -I./../config \ `echo ./parse.c | sed 's,^\./,,'` parse.y: In function `yyparse': parse.y:744: warning: implicit declaration of function `error' parse.y:748: warning: implicit declaration of function `get_main_program_name' parse.y:748: warning: assignment makes pointer from integer without a cast parse.y:752: warning: implicit declaration of function `pedwarn' parse.y:755: warning: implicit declaration of function `initialize_module' parse.y:756: `current_module' undeclared (first use this function) parse.y:756: (Each undeclared identifier is reported only once parse.y:756: for each function it appears in.) parse.y:779: warning: implicit declaration of function `associate_external_objec ts' parse.y:789: warning: implicit declaration of function `check_external_objects' parse.y:820: warning: implicit declaration of function `concat' parse.y:821: warning: assignment makes pointer from integer without a cast parse.y:823: warning: implicit declaration of function `no_parameters' parse.y:823: warning: assignment makes pointer from integer without a cast parse.y:839: warning: implicit declaration of function `init_constructor' parse.y:840: warning: implicit declaration of function `un_initialize_block' parse.y:858: warning: assignment makes pointer from integer without a cast parse.y:860: warning: assignment makes pointer from integer without a cast parse.y:884: warning: implicit declaration of function `output_real_main_program ' parse.y:912: warning: implicit declaration of function `store_executable_name' parse.y:1298: `const_id' undeclared (first use this function) parse.y:1305: warning: implicit declaration of function `handle_autoexport' parse.y:1335: warning: implicit declaration of function `declare_vars' parse.y:1487: `size_volatile' undeclared (first use this function) parse.y:1503: warning: implicit declaration of function `build_schema_type' parse.y:1503: warning: assignment makes pointer from integer without a cast parse.y:1506: `type_id' undeclared (first use this function) parse.y:1653: warning: implicit declaration of function `build_pascal_string_sch ema' parse.y:1653: warning: assignment makes pointer from integer without a cast parse.y:1706: warning: implicit declaration of function `declared_string_capacit y' parse.y:1716: warning: assignment makes pointer from integer without a cast parse.y:1851: warning: implicit declaration of function `maybe_schema_discrimina nt' parse.y:1851: warning: implicit declaration of function `string_may_be_char' parse.y:1851: warning: assignment makes pointer from integer without a cast parse.y:1852: warning: assignment makes pointer from integer without a cast parse.y:1859: warning: implicit declaration of function `build_pascal_range_type ' parse.y:1859: warning: assignment makes pointer from integer without a cast parse.y:1870: warning: assignment makes pointer from integer without a cast parse.y:1871: warning: assignment makes pointer from integer without a cast parse.y:1878: warning: implicit declaration of function `grok_packed' parse.y:1878: warning: assignment makes pointer from integer without a cast parse.y:1897: warning: implicit declaration of function `build_pascal_pointer_ty pe' parse.y:1897: warning: assignment makes pointer from integer without a cast parse.y:2007: `string_schema_proto_type' undeclared (first use this function) parse.y:2045: warning: unused variable `size' parse.y:2087: warning: assignment makes pointer from integer without a cast parse.y:2104: warning: implicit declaration of function `check_object_pointer' parse.y:2124: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2135: warning: implicit declaration of function `build_pascal_array_type ' parse.y:2135: warning: assignment makes pointer from integer without a cast parse.y:2176: warning: implicit declaration of function `convert_type_to_range' parse.y:2176: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2178: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2184: warning: implicit declaration of function `build_file_type' parse.y:2184: warning: assignment makes pointer from integer without a cast parse.y:2203: warning: implicit declaration of function `build_set_type' parse.y:2203: warning: assignment makes pointer from integer without a cast parse.y:2199: warning: unused variable `range' parse.y:2211: warning: assignment makes pointer from integer without a cast parse.y:2299: warning: implicit declaration of function `p_grokfields' parse.y:2299: warning: assignment makes pointer from integer without a cast parse.y:2316: warning: implicit declaration of function `build_record_variant_pa rt' parse.y:2317: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2425: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2429: warning: passing arg 1 of `build_tree_list' makes pointer from int eger without a cast parse.y:2429: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:2460: warning: implicit declaration of function `store_object_name' parse.y:2461: warning: implicit declaration of function `add_vmt_field' parse.y:2462: warning: implicit declaration of function `construct_vmt' parse.y:2476: warning: implicit declaration of function `inherit' parse.y:2536: warning: implicit declaration of function `mark_virtual_method' parse.y:2536: warning: assignment makes pointer from integer without a cast parse.y:2545: warning: assignment makes pointer from integer without a cast parse.y:2564: warning: assignment makes pointer from integer without a cast parse.y:2578: warning: implicit declaration of function `get_method_name' parse.y:2579: warning: assignment makes pointer from integer without a cast parse.y:2601: warning: assignment makes pointer from integer without a cast parse.y:2665: `const_string_schema_proto_type' undeclared (first use this functi on) parse.y:2672: warning: assignment makes pointer from integer without a cast parse.y:2682: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:2762: `extern_id' undeclared (first use this function) parse.y:2779: `static_id' undeclared (first use this function) parse.y:2781: `volatile_id' undeclared (first use this function) parse.y:2783: `attribute_id' undeclared (first use this function) parse.y:3102: warning: implicit declaration of function `name_exported_p' parse.y:3103: warning: implicit declaration of function `maybe_make_static' parse.y:3103: warning: assignment makes pointer from integer without a cast parse.y:3255: warning: assignment makes pointer from integer without a cast parse.y:3265: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:3306: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:3326: `inline_id' undeclared (first use this function) parse.y:3348: warning: assignment makes pointer from integer without a cast parse.y:3551: warning: implicit declaration of function `push_self_parameter' parse.y:3603: warning: implicit declaration of function `handle_formal_param_lis t' parse.y:3633: warning: implicit declaration of function `handle_formal_conf_arra y_param_list' parse.y:3722: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:3723: warning: assignment makes pointer from integer without a cast parse.y:3772: warning: implicit declaration of function `emit_nop' parse.y:3886: warning: implicit declaration of function `emit_line_note' parse.y:3916: warning: implicit declaration of function `warning_with_file_and_l ine' parse.y:3926: warning: passing arg 1 of `c_expand_start_case' makes pointer from integer without a cast parse.y:3952: warning: implicit declaration of function `error_with_decl' parse.y:4153: warning: implicit declaration of function `check_for_control_varia ble' parse.y:4158: warning: assignment makes pointer from integer without a cast parse.y:4163: warning: implicit declaration of function `get_unique_identifier' parse.y:4172: warning: passing arg 1 of `start_decl' makes pointer from integer without a cast parse.y:4197: warning: passing arg 1 of `start_decl' makes pointer from integer without a cast parse.y:4266: warning: implicit declaration of function `construct_set' parse.y:4266: warning: assignment makes pointer from integer without a cast parse.y:4300: warning: implicit declaration of function `make_new_variable' parse.y:4300: warning: assignment makes pointer from integer without a cast parse.y:4373: warning: implicit declaration of function `expand_computed_goto' parse.y:4393: warning: implicit declaration of function `suspend_function_calls' parse.y:4397: warning: implicit declaration of function `resume_function_calls' parse.y:4437: warning: implicit declaration of function `allow_function_calls' parse.y:4462: warning: implicit declaration of function `maybe_call_function' parse.y:4462: warning: assignment makes pointer from integer without a cast parse.y:4464: warning: implicit declaration of function `call_method' parse.y:4464: warning: assignment makes pointer from integer without a cast parse.y:4489: warning: passing arg 1 of `lookup_name' makes pointer from integer without a cast parse.y:4516: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:4607: warning: assignment makes pointer from integer without a cast parse.y:4612: warning: implicit declaration of function `base_type' parse.y:4612: invalid type argument of `->' parse.y:4614: warning: assignment makes pointer from integer without a cast parse.y:4615: warning: implicit declaration of function `is_string_type' parse.y:4617: warning: implicit declaration of function `assign_string' parse.y:4645: `schema_id' undeclared (first use this function) parse.y:4699: warning: implicit declaration of function `build_rts_call' parse.y:5040: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5044: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5056: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5065: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5071: warning: passing arg 1 of `build_tree_list' makes pointer from int eger without a cast parse.y:5071: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5076: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5088: warning: passing arg 2 of `build_tree_list' makes pointer from int eger without a cast parse.y:5300: `string_id' undeclared (first use this function) parse.y:5360: warning: initialization makes pointer from integer without a cast parse.y:5473: warning: assignment makes pointer from integer without a cast parse.y:5475: warning: assignment makes pointer from integer without a cast parse.y:5486: warning: assignment makes pointer from integer without a cast parse.y:5501: warning: implicit declaration of function `get_standard_output' parse.y:5501: warning: assignment makes pointer from integer without a cast parse.y:5503: warning: implicit declaration of function `get_standard_input' parse.y:5503: warning: assignment makes pointer from integer without a cast parse.y:5510: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:5523: warning: implicit declaration of function `is_schema_discriminant_ access' parse.y:5527: warning: assignment makes pointer from integer without a cast parse.y:5544: warning: assignment makes pointer from integer without a cast parse.y:5564: warning: implicit declaration of function `build_buffer_ref' parse.y:5564: warning: assignment makes pointer from integer without a cast parse.y:5575: `empty_arglist' undeclared (first use this function) parse.y:5575: warning: assignment makes pointer from integer without a cast parse.y:5596: warning: implicit declaration of function `build_pascal_array_ref' parse.y:5596: warning: assignment makes pointer from integer without a cast parse.y:5626: warning: assignment makes pointer from integer without a cast parse.y:5638: warning: passing arg 1 of `start_decl' makes pointer from integer without a cast parse.y:5646: warning: initialization makes pointer from integer without a cast parse.y:5662: warning: initialization makes pointer from integer without a cast parse.y:5687: warning: initialization makes pointer from integer without a cast parse.y:5697: warning: assignment makes pointer from integer without a cast parse.y:5720: warning: passing arg 1 of `get_identifier' makes pointer from inte ger without a cast parse.y:5744: warning: implicit declaration of function `build_set_constructor' parse.y:5744: warning: assignment makes pointer from integer without a cast parse.y:5773: warning: implicit declaration of function `construct_set_member' parse.y:5773: warning: assignment makes pointer from integer without a cast parse.y:5775: warning: assignment makes pointer from integer without a cast parse.y:5780: warning: assignment makes pointer from integer without a cast parse.y:5784: warning: assignment makes pointer from integer without a cast parse.y:5787: warning: assignment makes pointer from integer without a cast parse.y:5789: warning: assignment makes pointer from integer without a cast parse.y:6077: warning: implicit declaration of function `finalize_module' parse.y:6078: `NULL_MODULE' undeclared (first use this function) parse.y:6105: warning: implicit declaration of function `export_interface' parse.y:6110: warning: implicit declaration of function `module_repair_exported_ ranges' parse.y:6111: warning: implicit declaration of function `create_gpi_files' parse.y:6113: warning: implicit declaration of function `handle_pending_decls' parse.y:6134: warning: implicit declaration of function `create_gpm_file' parse.y:6161: warning: implicit declaration of function `load_gpm_file' parse.y:6235: `we_are_loading_a_gpi_file' undeclared (first use this function) parse.y:6275: warning: initialization makes pointer from integer without a cast parse.y:6277: warning: initialization makes pointer from integer without a cast parse.y:6329: warning: initialization makes pointer from integer without a cast parse.y:6331: warning: initialization makes pointer from integer without a cast parse.y:6376: warning: initialization makes pointer from integer without a cast parse.y:6378: warning: initialization makes pointer from integer without a cast parse.y:6477: warning: implicit declaration of function `module_export_range' parse.y:6477: warning: assignment makes pointer from integer without a cast parse.y:6479: warning: implicit declaration of function `module_export_clause' parse.y:6479: warning: assignment makes pointer from integer without a cast parse.y:6481: warning: assignment makes pointer from integer without a cast parse.y:6484: warning: assignment makes pointer from integer without a cast parse.y:6539: warning: implicit declaration of function `import_interface' make[1]: *** [parse.o] Error 1 make[1]: Leaving directory `/usr1/local/src/GNU/SOURCE/gcc-2.7.2.3/p' make: *** [gpc1] Error 2

1 0

undeclared identifiers
by Tom Dye 12 Nov '97

12 Nov '97

Hello Peter, Thank you for helping so often and so well. With the code below gpc says I is an undeclared identifier and that the condition that I is part of must be of Boolean type. I've been through the examples in the Extended Pascal Standard to see if something is obviously wrong with the code, but didn't find anything there. Sorry if this is an obvious error in Extended Pascal. My Borland Pascal background leads me to believe that the code is OK, though. Is gpc not doing something right here? Tom Thomas S. Dye, Ph.D. Home: 813 16th Avenue, Honolulu, Hawaii 96816. Voice (808) 734-2087. Work: International Archaeological Research Institute, Inc., 949 McCully St., Suite 5, Honolulu, Hawaii 96826. Voice (808) 946-2548; Fax 943-0716. module charbug interface; export charbug = (IsAlphaNum); function IsAlphaNum (ch : char; i : integer) : boolean; end. module charbug implementation; function IsAlphaNum; begin if i > 2 then IsAlphaNum:= ch in ['A'..'Z','a'..'z','0'..'9']; end; end.

1 0

Re: DPMI calls (Was: Re: Backflips, ...)...
by Frank Heckenbach 12 Nov '97

12 Nov '97

<Pine.3.89.9711111023.A17958-0100000@@bc> Orlando Llanes wrote: > <grin> I wish there was something that overlaps instead of it > increasing the size :-/ I guess the only way around it is Type-casting. Variant records are overlapping, as I said. Type-casting is another way, absolute variables are a third one (though I don't recommend it since it's IMHO quite unsafe)... > I mean does GPC add to the size of the record? Or are all the cases > one size? For example, in my SomeVar example, would GPC treat it as 4 > elements? Or 2? 2 elements (GPC and BP). -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Re: DPMI calls (Was: Re: Backflips, ...)...
by Frank Heckenbach 11 Nov '97

11 Nov '97

Orlando Llanes wrote: > > On the x86 platform, it is. All variables (global, local and dynamic) and > > code are in the same segment, and pointers and references are just 32-bit > > offsets. (On other platforms, there may not be anything like Descriptors, or > > pointers may have a different size, e.g. 64 bits.) > > Cool :) Where can I Get info on the Machine specifics of Alphas? I > want to know the low level details like how graphics are displayed, if > sound is available, the architecture of the memory (for example: PC has > segments, offsets, etc). Though I can't really give you any information about this, and Peter gave you some, I just want to remak that these things are not actually dependent on the processor, but on the other hardware and the OS. While I don't know if there's more than one hardware architecture with Alphas, I'm quite sure that there are different OS's running on the Alpha. > > Unfortunately, there is something wrong there, namely the declaration of > > __dpmi_regs. Instead of ShortCard (16 bit unsigned integers on the x86, and > > the natural translation of the "unsigned short" of dpmi.h), it uses Bytes for > > the 16-bit registers. Try changing it as below. (I did not check your program, > > however, because I'm too lazy now to boot DosEmu... ;-) > > Doh! It's *always* those dang pesky minor details that are so elusive, > the ones that you would never think could possibly go wrong :P One thing > tho, I think I tried it using the following declarations (and I changed > the sizes accordingly as well): > > TYPE > DWord = Cardinal(32); > Word = Cardinal(16); > Byte = Cardinal(8); > > So what said Byte previously, I changed to Word, and what was Word > previously I changed to DWord. I'll try it again, mayhaps I did something > wrong :} These declarations seem OK, they always guarantee the correct register sizes (in constrast to the other types which are merely a 1-to-1 translation of the types used in the C header; they might be different on other platforms, but then, for DPMI specific code, that's not much of an issue...). However, I would not call it "Word" because in a 32-bit environment, some people would expect a "Word" to have 32 bits (as the built-in Word type does). Perhaps something like "Word16", to avoid possible confusion... > > BTW: "Packed" is (I think) not necessary for this record, because all fields > > are aligned, anyway, i.e. 32-bit fields are preceeded only by other 32-bit > > fields, and so on. The original record is a "struct" in dpmi.h, and I think > > C's "struct"s correspond to non-packed records in Pascal. Is this right? > > Does Packed align on a Dword boundary? Or does it lump all the fields > together to ensure that they are continuous? I ask because from what I > remmeber about Pascal, it's to keep them continuous (the only time in > Borin... errr... Standard Pascal that I've seen Packed is for a character > array). Yes, it keeps them together. What I meant is: since the fields are aligned, anyway, even a non-packed array would not insert any gaps, so it doesn't matter here if packed or non-packed. Since the corresponding function was written in C, it has to use non-packed "struct"s, so a non-packed array would be the 1-to-1 translation into Pascal. > Ok, I think I figured out what went wrong. Apparently in C, the way > __dpmi_regs is defined is in a way such that the 3 sections (d, x, and h) > overlap, but it doens't appear to be overlapping in Pascal. I noticed a > quirk with Borland Pascal, and I was wondering if it was present in GPC, > when you define a record structure as follows: > > TYPE > MyRec = RECORD > CASE Integer OF > 0 : (SomeVar : Integer; SomeVar2 : Integer); > 1 : AnotherVar : ARRAY[ 1..2 ] OF Integer; > END; > END; > > Supposedly, you want to tell the compiler to use SomeVar, or AnotherVar > as if they were overlapping. An Integer is 16 bits in BP, with that in > mind, BP would report 8 when you use SizeOf( MyRec ), logically it should > be 4. By overlapping, I mean like a type cast. Is there a way to do this > in GPC like C apparently does? Variant records *are* overlapping in Pascal (both BP and GPC). I don't know what you tried, but the following program gives 8 in GPC and 4 in BP, both as I expected for an overlapping type. program x; TYPE MyRec = RECORD CASE Integer OF 0 : (SomeVar : Integer; SomeVar2 : Integer); 1 : (AnotherVar : ARRAY[ 1..2 ] OF Integer); END; begin writeln(sizeof(myrec)) end. If you still don't get the program working, please post a complete program that tries to set the mode, so we can try it. Kevin A. Foss wrote: > >> Is there anything in C that corresponds to packed records in Pascal? > > [...] > > However there are a lot of caveats, like you can only use integer > types, and the behavior if a field crosses a word boundry is > implementation defined. So it would take a lot of work to simulate > anything but the simplest Packed Pascal records--although I lost where > the discussion began so I don't know for what reason you want to pack > things in C. Nothing particular, just curiosity. Thanks for the info. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Re: GPC and GPT
by Frank Heckenbach 11 Nov '97

11 Nov '97

In news:comp.lang.pascal.borland, Brian Jones <brijones(a)usa.net> wrote: > I have copies of both GPC and GPT, along with RH-IDE and the GNU binutils, > as well as almost the rest of the entire DJGPP collection. I have tried to > write programs in Pascal using RH-IDE, and have had success getting them to > compile, but I can't get them to link (although I can get programs written > in C to link). My question is this, has anyone else had this same problem, > or does anyone know how to fix this? When replying, it's probably necessary to CC a copy to the poster. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

1 0

Re: DPMI calls (Was: Re: Backflips, ...)...
by Peter Gerwinski 11 Nov '97

11 Nov '97

According to Orlando Llanes: > I noticed a > quirk with Borland Pascal, and I was wondering if it was present in GPC, > when you define a record structure as follows: > > TYPE > MyRec = RECORD > CASE Integer OF > 0 : (SomeVar : Integer; SomeVar2 : Integer); > 1 : AnotherVar : ARRAY[ 1..2 ] OF Integer; > END; > END; This is not a quirk but a variant record which is even part of the ISO standard. (Hmmm ... so maybe it "must" be a quirk?;-) (BTW, you have one superfluous `END' in the above.) > Supposedly, you want to tell the compiler to use SomeVar, or AnotherVar > as if they were overlapping. An Integer is 16 bits in BP, with that in > mind, BP would report 8 when you use SizeOf( MyRec ), logically it should > be 4. By overlapping, I mean like a type cast. Is there a way to do this > in GPC like C apparently does? GPC accepts this, just like BP or any other Pascal compiler does. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Turbo/Free Vision --- or EFLIB
by Johan Larsson 11 Nov '97

11 Nov '97

[ EFLIB vs. Free Vision for FPK Pascal ] Hi Daniel Mantione and everybody, Pierre Phaneuf writes: >> EFLIB to be crushed by advanced capabilities, extreme flexibility >> and out-of-this-world performance! ;-) Daniel Mantione writes: >> What do you think of making EFLIB as a supplement to the objects unit? Daniel: yes - and no, depending on how to interprete ;-) your question! EFLIB will never be written to be compatible with Turbo Vision: let me explain why! The goal with EFLIB is to create a standardized class library. But as Pierre said, we also aim to create an extreme flexibility as well as modularity and code reusability - and simplicity. These are the main goals with EFLIB - not to follow existing standards thus limiting the new thinking and Java-alike solutions, event mechanisms, design patterns and so on. The only consideration that affect the way EFLIB will evolve is **what is the best solution**. "What is the best backward compatible solution" is of little or no concern (with one exception; backward compatiblity to earlier EFLIB releases starting with the first official release, but that will be a piece of cake when the modular interface is set). Let me give concrete examples. When classic data structures are designed, we do not look at traditional solutions and try to follow the expectations of the user. Instead, we find the solution we prefer, and try to package that solution in a simple interface and an intuitive design. Iterator classes for the data structures are one example. Hash table class hierarchy is one. ADT inheritance is yet one. But there is one thing that may be of interest for you. Since the capabilities of Turbo Vision (or Free Vision) is likely to be a subset of the capabilities of EFLIB, we could (with help from some Turbo Vision enthusiast of course) create classes that ***emulate Turbo Vision*** within EFLIB. The same goes with other features in EFLIB; for example the extended stream engine to be designed by Pierre Phaenuf or the GUI components to be designed by Aleksandar Dlabac and Miroslav Kharchuk - or anything else. We could provide a complete set of Turbo Vision (read: Free Vision) classes built on the modular and standardized EFLIB solutions. Thus, we can provide a dual interface so that old users can make use of the new features... But then, I'd rather see that you all learned EFLIB straight from the start... But I guess that never will happen --- ;-) Best Regards, Johan Larsson E-MAIL jola(a)ts.umu.se, EFLIB(a)ts.umu.se, EFLIB-Developers(a)ts.umu.se, EFLIB-Users(a)ts.umu.se HOME http://www.ts.umu.se/~jola/ Also, REMEMBER to check out http://ftp.sunet.se/EFLIB/ for a free application framework - SIMPLY SOPHISTICATED. Also, Subscribe to the EFLIB mailing lists! See http://www.ts.umu.se/EFLIB/Lists/.

1 0

Re: Backflips, cartwheels, and proc params...
by Peter Gerwinski 11 Nov '97

11 Nov '97

According to Orlando Llanes: > > Cool :) Where can I Get info on the Machine specifics of Alphas? I > want to know the low level details like how graphics are displayed, if > sound is available, the architecture of the memory (for example: PC has > segments, offsets, etc). [...] See the source (and its documentation) of the Linux kernel for the Alpha. > BTW, are there plans to port DJGPP and/or GPC to > the Mac platform? Are there any free tools you or anybody know of that > compile on it? AFAIK, the GNU project does not support the Mac platform because Apple did not give them the necessary information. > TYPE > DWord = Cardinal(32); > Word = Cardinal(16); > Byte = Cardinal(8); > > So what said Byte previously, I changed to Word, and what was Word > previously I changed to DWord. I'll try it again, mayhaps I did something > wrong :} `Byte' always has the smallest size direcly accessible to the processor anyway - usually eight bits ... > Does Packed align on a Dword boundary? Or does it lump all the fields > together to ensure that they are continuous? The second. Without `packed', you get the first. > I ask because from what I > remmeber about Pascal, it's to keep them continuous (the only time in > Borin... errr... Standard Pascal that I've seen Packed is for a character > array). It does not stop there: Try the following with BP and with GPC: Var foo: packed array [ 1..64 ] of Boolean; writeln ( SizeOf ( foo ) ); :-) > Got me on that one :( Although I am very familiar with the types, > type definitions, and I haven't seen anything really about packing the > records like in Pascal. I could be wrong tho, if there is something, it's > one of those deep dark secrets of C :P There are bit fields: struct foo { int i : 4; unsigned j : 2; int k : 1; unsigned l: 1; } is the same as the following in Pascal foo = packed record i: -8..7; j: 0..3; k, l: 0..1; end (* foo *); and both fit in a single byte. Have fun, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Binary installation
by Peter Gerwinski 11 Nov '97

11 Nov '97

According to Tom Dye: > > There might be another problem. The following code once compiled, but > doesn't now. > > *** code snippet *** > > module bug interface; > > export > bug = (StrPCopy); > > const > LONGEST_STRING = 256; > > type > Any_String = String(LONGEST_STRING); > CString = __cstring__; > > function StrPCopy (Dest : CString; Src : Any_String) : CString; > > end. > > module bug implementation; > [...] > function StrPCopy (Dest : CString; Src : Any_String) : CString; Since `Any_String' isn't exported, the implementation module does not know about it. (Should it? What does the standard say about this?) You can either export `Any_String' or change `StrPCopy' to accept just a `String' parameter. The latter method did not work in gpc-2.0 but is in fact the correct way to pass an arbitrary string. function StrPCopy (Dest : CString; Src : String) : CString; or function StrPCopy (Dest : CString; Const Src : String) : CString; Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: probs compiling current beta GPC
by Peter Gerwinski 11 Nov '97

11 Nov '97

According to Clyde Meli: > /usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.3/include/unistd.h:230: conf > licting types for `rename' > /usr/local/lib/gcc-lib/sparc-sun-solaris2.5.1/2.7.2.3/include/stdio.h:161: previ > ous declaration of `rename' It seems as if the (AutoConf) configuration script did not recognize your system correctly. Please try and edit `gpc-config.h' manually and flip the `HAVE_UNISTD_H' switch. Good luck, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Backflips, cartwheels, and proc params...
by Kevin A. Foss 11 Nov '97

11 Nov '97

On Mon, 10 Nov 1997 18:54:57 -0500 (EST), Orlando Llanes wrote: >> Is there anything in C that corresponds to packed records in Pascal? > > Got me on that one :( Although I am very familiar with the types, >type definitions, and I haven't seen anything really about packing the >records like in Pascal. I could be wrong tho, if there is something, it's >one of those deep dark secrets of C :P Well, it won't be totally analogous to a packed record in Pascal, but you can of course define bit fields for variables. The C standard also allows padding by putting in x # of bits assigned to an unnamed field in order to fill out a byte or word. Also, a bit width of 0 will force alignment on the next word boundry. {See the last section in Chapter 6 of K&R} So I think you could simulate packed records but you would have to do it by manually setting integers to specific bit-widths. In fact, K&R refers to bit-fields as a method to 'pack several objects into a machine word.' However there are a lot of caveats, like you can only use integer types, and the behavior if a field crosses a word boundry is implementation defined. So it would take a lot of work to simulate anything but the simplest Packed Pascal records--although I lost where the discussion began so I don't know for what reason you want to pack things in C. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

1 0

Re: Binary installation
by Peter Gerwinski 11 Nov '97

11 Nov '97

According to Tom Dye: > > [...] This code, which compiled > previously, fails now with a message that there is an undeclared > identifier `Ch' in function Isalphanum on line 17. [...] I fixed it. :-) Patch below. Since this patch changes the GPI file format, you must recompile all your modules/units after having applied it. Have fun, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005] 8< --------------------------------------------------------------------------- --- gpc-971106/p/module.c Sat Nov 1 03:30:22 1997 +++ gpc/p/module.c Sun Nov 9 21:02:24 1997 @@ -1186,7 +1186,7 @@ store_tree (DECL_NAME (t), s, depth + 1); /* name of function */ store_tree (DECL_ASSEMBLER_NAME (t), s, depth + 1); store_tree (TREE_TYPE (TREE_TYPE (t)), s, depth + 1); /* return type */ - store_tree (TYPE_ARG_TYPES (TREE_TYPE (t)), s, depth + 1); /* argument types */ + store_tree (DECL_LANG_SPECIFIC (t)->parms, s, depth + 1); /* arguments */ /* Machine attributes. */ for (a = TYPE_ATTRIBUTES (TREE_TYPE (t)); a; a = TREE_CHAIN (a)) @@ -1765,8 +1765,8 @@ * they already were prediscriminated before they were * written into the GPI file. */ - tree name = get_unique_identifier ("parm", 0); - d = build_tree_list (NULL_TREE, TREE_VALUE (a)); + tree name = DECL_NAME (a); + d = build_tree_list (NULL_TREE, TREE_TYPE (a)); d = build_tree_list (build_tree_list (d, name), build_tree_list (NULL_TREE, NULL_TREE)); push_parm_decl (d);

2 1

Re: Backflips, cartwheels, and proc params...
by Frank Heckenbach 11 Nov '97

11 Nov '97

Orlando Llanes wrote: > Let's say I have a record as follows: > > TYPE > ToeFoo = PACKED RECORD { Is PACKED neccessary to keep it continuous? } Yes, it is. If you want to verify for yourself, you can try something like var Foo: ToeFoo; begin {$x+} Writeln ( Pointer((a)Foo.BarNone) - Pointer((a)Foo.Bar) ) end. (works only with non-packed records). The type casts to Pointer are there to prevent GPC from assuming another base size than 1. > Bar : Byte; > BarNone : Word; > END; > The fields are not important, what is important is the following procedure: > > PROCEDURE DahDahDah( VAR aFoo : ToeFoo ); > BEGIN > END; > > I need to get a pointer to it in ASM in order to manipulate it and in > order to save the value. What would I have to do? Is it safe to assume > that DS = Descriptor to aFoo in procedure DahDahDah? And do VAR parameters > return a 32-bit offset? I remember it coming up once before that the > pointers were 32-bit offsets, but I just want to verify that I remembered > correctly :} On the x86 platform, it is. All variables (global, local and dynamic) and code are in the same segment, and pointers and references are just 32-bit offsets. (On other platforms, there may not be anything like Descriptors, or pointers may have a different size, e.g. 64 bits.) > For the curious, what I'm doing is coding a DPMI Simulate Real Mode > Interrupt so I Can call RM ISRs, but especially to change the graphics > mode. I'm aware of BPCompat (BTW, AWESOME collection of routines Chief et > al! :), and I tried it, but although the procedure > __dpmi_simulate_real_mode_interrupt() executed properly, I didn't get the > desired video mode. Besides, I'm coding it myself because I want to keep > it simple. (* IMHO, it would be simpler to use existing units. *) > Instead of getting mode 3, I got mode 1 or 2 (I didn't check beyond > noticing that it didn't look like Mode-13h, it was some 40x20 characters > per screen, and it looked like a text mode). I honestly don't think it was > something wrong in the DPMI unit, the DPMI unit links to a C routine. Unfortunately, there is something wrong there, namely the declaration of __dpmi_regs. Instead of ShortCard (16 bit unsigned integers on the x86, and the natural translation of the "unsigned short" of dpmi.h), it uses Bytes for the 16-bit registers. Try changing it as below. (I did not check your program, however, because I'm too lazy now to boot DosEmu... ;-) BTW: "Packed" is (I think) not necessary for this record, because all fields are aligned, anyway, i.e. 32-bit fields are preceeded only by other 32-bit fields, and so on. The original record is a "struct" in dpmi.h, and I think C's "struct"s correspond to non-packed records in Pascal. Is this right? Is there anything in C that corresponds to packed records in Pascal? -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm --- dpmi.pas Wed Oct 22 13:47:10 1997 +++ /dos/f/t/dpmi.pas Mon Nov 10 19:35:14 1997 @@ -68,23 +68,23 @@ ); x : ( - di, di_hi : Byte; - si, si_hi : Byte; - bp, bp_hi : Byte; - x_res, res_hi : Byte; - bx, bx_hi : Byte; - dx, dx_hi : Byte; - cx, cx_hi : Byte; - ax, ax_hi : Byte; - flags : Byte; - es : Byte; - ds : Byte; - fs : Byte; - gs : Byte; - ip : Byte; - cs : Byte; - sp : Byte; - ss : Byte; + di, di_hi : ShortCard; + si, si_hi : ShortCard; + bp, bp_hi : ShortCard; + x_res, res_hi : ShortCard; + bx, bx_hi : ShortCard; + dx, dx_hi : ShortCard; + cx, cx_hi : ShortCard; + ax, ax_hi : ShortCard; + flags : ShortCard; + es : ShortCard; + ds : ShortCard; + fs : ShortCard; + gs : ShortCard; + ip : ShortCard; + cs : ShortCard; + sp : ShortCard; + ss : ShortCard; ); h : (

2 2

Re: 2 suggestions about Units
by Frank Heckenbach 10 Nov '97

10 Nov '97

Hans Ecke wrote: > [...] > > unit communication(graph,keyboard,mouse); > > interface > > ...no interface because its unchanged > ...new/changed procedures or variables would be declared here Should there be a way to "hide" some of the other units' declarations, i.e. not export all of them? If so, any ideas, how? > begin > assign(logfile,`log`); > rewrite(logfile); > > inherited begin; (*or inherited init? or inherited main? Don't know > which is better*) I don't think this should/must/may be written at all. The initalization code of the other units will be called, anyway, before the code of this unit. I don't think there's any reason to change this, since it's good practice (also in OOP) to do the "inherited" initialization *before* one's own initialization (and the inherited finalization after one's own finalization). BTW: Does GPC already make sure that unit initializations/finalizations happen in this order? Otherwise, this might cause problems in some programs. > New syntax-elements needed : 1.) "unit foo(bar1,bar2,..);" > 2.) "inherited <someprocedure>;" > Advantages are, that this new syntax is IMHO very intuitive and uses > existing keywords by carefully extending their meaning. True. > Discussion of the new syntax: > ---------------------------- > 1.) The "unit foo(bar);" part would be simple(?,IMHO): Its just that all > interfaces are put after each other in order of appearence. I think (hope) so. This certainly seems useful. > 2.) The "inherited <someprocedure>;" part should be possible too. You have > procedure-overloading. As far as I know from C++ this is implemented by > translating names of procedures : > > procedure foo(s:string) -> asmname "foostring" (the identifier in the) > procedure foo(i:integer) -> asmname "foointeger" (.o-file, just example) > > The .gpi-file includes a mapping asmname<->pascalname of all funtions that > the compiler can put a call to "foostring" for a command like > foo(`bar!bar??BAR!!`) and a call to "foointeger" for foo(10). I think, overloading of procedures for different parameters is not quite the same, but so-called "qualified identifiers" for procedures with the same name in different units are planned to be introduced until GPC 2.2, anyway. > Assuming our example, the compiler reads the line "inherited > putpixel(..);". It looks for the asmname of graph.putpixel and calls it. > Communication.putpixel then gets its own asmname which has to be different > from the one of graph.putpixel. Then, I agree, "inherited" procedures don't seem like a big problem. However, there is a big difference to a "real" virtual procedure. Namely, when the original Graph unit contains a call to putpixel (e.g. from a line drawing function), the compiler can't possibly know that putpixel will be "overriden", so it will call graph.putpixel. The overriden procedure would only be effective for units using Communication. For putpixel, it might be only an efficiency problem, but e.g. mouse events that are called from within the mouse unit would not be logged in your example. OTOH, real virtual procedures might be possible, too, but they will have to be marked as virtual in the *original* unit, and it will probably be more work to implement them. (The compiler would have to automatically generate something like the code I showed last time.) > There is the only question/problem I can see : We want to have one > interface - this meens only one file communication.gpi. What with the > object-files? Just leave them as (see example) graph.o,keyboard.o,mouse.o > or build a librarie communication.a? I think that's left to the programmer (when GPC will be able to produce libraries). Either he takes the several .o files, or makes a library out of them. However, there seem to be some problems (technical and syntactical) to be solved for letting GPC produce libraries. > Also a problem with the librarie : What to do with generic units which > will be included often - like system.o or crt.o - include them into the > librarie? Also left to the programmer. But I would advise him not to do so, since when they will be updated, the user should have a chance to use the updated versions instead of the ones built into the library. Also, I'm not sure what happens when one uses several libraries that each include system.o. And, please note the conditions of the LGPL under which system and crt are. If he includes their binary files, he has to provide their sources, too. Therefore, it might be easier for him, just to point to or include the complete BPCompat package. -- Frank Heckenbach, Erlangen, Germany fjf(a)gmx.de http://home.pages.de/~fjf/links.htm

2 1

Backflips, cartwheels, and proc params...
by Orlando Llanes 10 Nov '97

10 Nov '97

Let's say I have a record as follows: TYPE ToeFoo = PACKED RECORD { Is PACKED neccessary to keep it continuous? } Bar : Byte; BarNone : Word; END; The fields are not important, what is important is the following procedure: PROCEDURE DahDahDah( VAR aFoo : ToeFoo ); BEGIN END; I need to get a pointer to it in ASM in order to manipulate it and in order to save the value. What would I have to do? Is it safe to assume that DS = Descriptor to aFoo in procedure DahDahDah? And do VAR parameters return a 32-bit offset? I remember it coming up once before that the pointers were 32-bit offsets, but I just want to verify that I remembered correctly :} For the curious, what I'm doing is coding a DPMI Simulate Real Mode Interrupt so I Can call RM ISRs, but especially to change the graphics mode. I'm aware of BPCompat (BTW, AWESOME collection of routines Chief et al! :), and I tried it, but although the procedure __dpmi_simulate_real_mode_interrupt() executed properly, I didn't get the desired video mode. Besides, I'm coding it myself because I want to keep it simple. Again for the curious, I typed in the following code: PROGRAM VGA; USES DPMI; VAR Regs : __dpmi_regs; BEGIN Regs.x.ax := $03; __dpmi_simulate_real_mode_interrupt( $10, Regs ); END. Instead of getting mode 3, I got mode 1 or 2 (I didn't check beyond noticing that it didn't look like Mode-13h, it was some 40x20 characters per screen, and it looked like a text mode). I honestly don't think it was something wrong in the DPMI unit, the DPMI unit links to a C routine. See ya! Orlando Llanes "Hey, we all did the drug thing, we all did the money thing, and eventually you find out that none of that stuff fixes anything, and we have nowhere else to go except to evolve spiritually and intellectually" -- Meredith Brooks "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve/homepages/Monkey414

1 0

Re: Separate Compilation
by richard.kerry＠quantel.com 10 Nov '97

10 Nov '97

According to richard.kerry(a)quantel.com: > > Hello, > Could somebody please either : > 1. Direct me to - info -f gpc -n "Source structures" info -f gpc -n "Extensions" > or : > 2. Send me - > a comprehensive explanation of separate compilation using gpc, including > examples that clearly show which bits are in different files and how the > other bits pick up their definitions. And also including any > alternate/non-standard/old-fashioned techniques that are still usable. > I am working on a very large project, developed using Oregon Pascal. The > separate compilation is done by each module (eg fred.pas) having a header > file (eg fred.def) containing all the procedures, functions, types and > constants it wishes the rest of the world to know about. All the routines > in the header are 'external'. The modules all contain their own global > variables; if any need to share, this is done by access procedures, or > records shared via pointers. There is no > module/unit/import/export/interface/implementation system involved. The > modules are compiled individually, using #include (%include in Oregon) to You can also use (*$i Foo *) or (*$include "foo.pas" *) or (*$include <foo.pas> *). > pick up any external definitions and references required, and then linked. > I want to mechanically translate all these modules to gpc, so I'd prefer a > mechanism, if there is more than one available, that uses a structure as > similar as possible to the one we are currently using. The closest approximation to Oregon Pascal (as you describe it) which is currently possible with GNU Pascal is to use the "somewhat simpler GPC modules" described in `info -f gpc -n Extensions'. will have the desired effect ... uh - sh** (sorry!) it does not work! :-( :-( While implementing other things I threw away this one. The reason is that this feature turned into a bug when using Extended Pascal Modules or UCSD/Borland Pascal Units. Okay, this "GPC specific module" is very close to yet another type of Module defined in the PXSC standard. The only difference is that PXSC wants the reserved word `global' in front of each declaration that is to be exported. That's certainly more reasonable than to export just everything (like GPC did until February 1997 or so). It is planned to implement these PXSC modules into GPC. So you can either wait until GPC will have PXSC modules or use UCSD/Borland-style Units or Extended Pascal Modules. --------------------- Would it be possible to have a patch to re-enable the 'somewhat simpler' format, perhaps on a compiler switch ? The formatter program I am modifying to do our Oregon-to-GPC conversion doesn't have a symbol table that can be used to determine which routines are internal or external, so I prefer the syntaxes (is that a word ?) that don't need only the externals to be marked (global), or all to be bunched together or the definitions to be duplicated again (interface, implementation). That is to say I'd prefer to be able to use such a syntax at this stage so I can pass over three hundred modules through the conversion and not require every one of them to be hand-tweaked. I'd consider this a first stage of conversion, and expect to gradually convert them all to proper (Extended) syntax over a period of time. ----------------------- When is PXSC syntax likely to be available ? ----------------------- What's fatal signal 11 ? I've been changing my program to use separate compilation, rather than just $including all the bits of source it needs. I'm changing it to UCSD/Borland unit form, as I understand it from the Info and Peter's reply, and I get : 'gpc: Internal compiler error: program gpc1 got fatal signal 11' when I try to compile the unit. 'gpc fred.pas -o fred.o -v' gives : Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux/2.7.2.3/specs gpc version 971001(2.7.2.3) /usr/local/lib/gcc-lib/i586-pc-linux/2.7.2.3/gpc-cpp -lang-pascal -v -nocharescape -undef -D__GNUC__=2 -D__GPC__=2 -D__GNUC_MINOR__=7 -D__ELF__ -Dunix -Di386 -Dlinux -D__ELF__ -D__unix__ -D__i386__ -D__linux__ -D__unix -D__i386 -D__linux -Asystem(unix) -Asystem(posix) -Acpu(i386) -Amachine(i386) fred.pas /tmp/cca13174.i GNU CPP version 971001(2.7.2.3) (i386 Linux/ELF) #include "..." search starts here: #include <...> search starts here: /usr/local/include /usr/local/i586-pc-linux/include /usr/local/lib/gcc-lib/i586-pc-linux/2.7.2.3/include /usr/include End of search list. /usr/local/lib/gcc-lib/i586-pc-linux/2.7.2.3/gpc1 /tmp/cca13174.i -quiet -dumpbase fred.pas -version -famtmpfile=fred.gpc -o /tmp/cca13174.s GNU Pascal version 971001(2.7.2.3) (i386 Linux/ELF) compiled by GNU C version 2.7.2.3. gpc: Internal compiler error: program gpc1 got fatal signal 11 I hope you can help. Richard.

1 0

Re: probs compiling current beta GPC
by Peter Gerwinski 10 Nov '97

10 Nov '97

According to Clyde Meli: > > I don't think my previous post got through - If they did please excuse this > repetition. It did come through. ;-) > I'm having problems compiling the beta under Solaris 2.5.1/gcc 2.7.2.3 > - I had problems with gcc 2.7.2.1 also so I installed gcc 2.7.2.3. > > /usr/local/bin/gcc -c -DIN_GCC -DGPC -DSVR4 -O3 -I. -I.. -I. -I./.. -I./.. > /config gpc-lex.c > In file included from gpc-lex.c:102: > hash.h:122: `AND_' undeclared here (not in a function) > [...] Uh - sorry - `parse.h' in `gpc-971001.tar.gz' is broken. :-( You can reconstruct it from `parse.y' using `bison', but since this didn't happen automatically during you compiled GPC, I assume that you cannot use `bison' on that machine. But never mind: Since `parse.h' is pretty short, I include it below. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005] 8< ---- parse.h for gpc-971001 ----------------------------------------------- typedef union { char *filename; long itype; int lineno; enum tree_code code; tree ttype; } YYSTYPE; #define IDENTIFIER 258 #define AND_ 259 #define ARRAY 260 #define BEGIN 261 #define CASE 262 #define CONST_ 263 #define DIV_ 264 #define DO 265 #define DOWNTO 266 #define ELSE 267 #define END 268 #define FILE_ 269 #define FOR 270 #define FUNCTION 271 #define GOTO 272 #define IF 273 #define IN 274 #define LABEL 275 #define MOD_ 276 #define NIL_ 277 #define NOT_ 278 #define OF 279 #define OR 280 #define PACKED 281 #define PROCEDURE 282 #define PROGRAM 283 #define RECORD 284 #define REPEAT 285 #define SET_ 286 #define THEN 287 #define TO 288 #define TYPE 289 #define UNTIL 290 #define VAR 291 #define WHILE 292 #define WITH 293 #define AND_THEN 294 #define BINDABLE 295 #define EXPORT 296 #define IMPORT 297 #define MODULE 298 #define ONLY 299 #define OR_ELSE 300 #define OTHERWISE 301 #define POW 302 #define RESTRICTED 303 #define PROTECTED 304 #define QUALIFIED 305 #define VALUE 306 #define OP_ABSTRACT 307 #define OP_CLASS 308 #define OP_CONSTRUCTOR 309 #define OP_DESTRUCTOR 310 #define OP_INHERITED 311 #define OP_IS 312 #define OP_PROPERTY 313 #define OP_VIEW 314 #define D_EXTERNAL 315 #define D_FORWARD 316 #define UCSD_SEGMENT 317 #define BP_EXPORTS 318 #define BP_INDEX 319 #define BP_INLINE 320 #define BP_INTERRUPT 321 #define BP_LIBRARY 322 #define BP_OBJECT 323 #define BP_OVERLAY 324 #define BP_PRIVATE 325 #define BP_PUBLIC 326 #define BP_RESIDENT 327 #define BP_SHL 328 #define BP_SHR 329 #define BP_UNIT 330 #define BP_USES 331 #define BP_XOR 332 #define ALL 333 #define RENAME 334 #define SYMMETRIC_DIFF 335 #define STRING_KEYWORD 336 #define IMPLEMENTATION 337 #define INTERFACE 338 #define D_ASMNAME 339 #define D_ATTRIBUTE 340 #define D_C 341 #define D_C_LANGUAGE 342 #define D_EXTERN 343 #define D_OVERRIDE 344 #define D_STATIC 345 #define BP_ABSOLUTE 346 #define BP_VIRTUAL 347 #define r_WRITE 348 #define r_READ 349 #define r_INITFDR 350 #define r_LAZYGET 351 #define r_COLLECT 352 #define r_POW 353 #define r_EXPON 354 #define z_ARCTAN 355 #define z_COS 356 #define z_EXP 357 #define z_LN 358 #define z_SIN 359 #define z_SQRT 360 #define z_POW 361 #define z_EXPON 362 #define p_INPUT 363 #define p_OUTPUT 364 #define p_REWRITE 365 #define p_RESET 366 #define p_PUT 367 #define p_GET 368 #define p_WRITE 369 #define p_READ 370 #define p_WRITELN 371 #define p_READLN 372 #define p_PAGE 373 #define p_NEW 374 #define p_DISPOSE 375 #define p_ABS 376 #define p_SQR 377 #define p_SIN 378 #define p_COS 379 #define p_EXP 380 #define p_LN 381 #define p_SQRT 382 #define p_ARCTAN 383 #define p_TRUNC 384 #define p_ROUND 385 #define p_PACK 386 #define p_UNPACK 387 #define p_ORD 388 #define p_CHR 389 #define p_SUCC 390 #define p_PRED 391 #define p_ODD 392 #define p_EOF 393 #define p_EOLN 394 #define p_MAXINT 395 #define p_TRUE 396 #define p_FALSE 397 #define p_EXTEND 398 #define p_UPDATE 399 #define p_SEEKWRITE 400 #define p_SEEKREAD 401 #define p_SEEKUPDATE 402 #define p_READSTR 403 #define p_WRITESTR 404 #define p_BIND 405 #define p_UNBIND 406 #define p_HALT 407 #define p_GETTIMESTAMP 408 #define p_ARG 409 #define p_RE 410 #define p_IM 411 #define p_CARD 412 #define p_CMPLX 413 #define p_POLAR 414 #define p_EMPTY 415 #define p_POSITION 416 #define p_LASTPOSITION 417 #define p_LENGTH 418 #define p_SUBSTR 419 #define p_TRIM 420 #define p_EQ 421 #define p_LT 422 #define p_GT 423 #define p_NE 424 #define p_LE 425 #define p_GE 426 #define p_BINDING 427 #define p_DATE 428 #define p_TIME 429 #define p_MAXCHAR 430 #define p_MAXREAL 431 #define p_MINREAL 432 #define p_EPSREAL 433 #define ucsd_CONCAT 434 #define bp_ASSIGN 435 #define bp_GETMEM 436 #define bp_FREEMEM 437 #define bp_INC 438 #define bp_DEC 439 #define bp_NEAR 440 #define bp_FAR 441 #define PXSC_OPERATOR 442 #define gpc_ASSIGNTYPE 443 #define gpc_MIN 444 #define gpc_MAX 445 #define STANDARD_OUTPUT 446 #define STANDARD_INPUT 447 #define op_COPY 448 #define op_NULL 449 #define op_ROOT 450 #define op_SELF 451 #define op_TEXTWRITABLE 452 #define ASM_KEYWORD 453 #define BREAK 454 #define CONTINUE 455 #define p_INDEX 456 #define p_MARK 457 #define p_RELEASE 458 #define RETURN_ 459 #define RESULT 460 #define EXIT 461 #define DEFAULT 462 #define OTHERS 463 #define p_CLOSE 464 #define SIZEOF 465 #define BITSIZEOF 466 #define ALIGNOF 467 #define TYPEOF 468 #define ANDAND 469 #define CONJUGATE 470 #define p_DEFINESIZE 471 #define gpc_GETFILE 472 #define INLINE 473 #define EXTERNAL 474 #define ASMNAME 475 #define VOLATILE 476 #define STATIC 477 #define G_CONST 478 #define TQ_BYTE 479 #define TQ_SHORT 480 #define TQ_LONG 481 #define TQ_LONGLONG 482 #define TQ_UNSIGNED 483 #define UNSIGNED_INTEGER 484 #define STRING_LITERAL 485 #define CHAR_LITERAL 486 #define UNSIGNED_REAL 487 #define GTE 488 #define LTE 489 #define NEQ 490 #define EXPON 491 #define CARET 492 #define CONST_EQUAL 493 #define CEILPLUS 494 #define CEILMINUS 495 #define CEILMULT 496 #define CEILRDIV 497 #define FLOORPLUS 498 #define FLOORMINUS 499 #define FLOORMULT 500 #define FLOORRDIV 501 #define ASSIGN 502 #define LBRACKET 503 #define RBRACKET 504 #define TWODOTS 505 #define ELLIPSIS 506 #define UNIMPLEMENTED 507 extern YYSTYPE yylval; #define YYEMPTY -2

1 0

Re: 2 suggestions about Units
by Peter Gerwinski 10 Nov '97

10 Nov '97

Hallo, Hans! Hello, everybody! According to Hans Ecke: > > [...] > > 1.) The "unit foo(bar);" part would be simple(?,IMHO): Its just that all > interfaces are put after each other in order of appearence. > > 2.) The "inherited <someprocedure>;" part should be possible too. You have > procedure-overloading. Not yet, but we are planning to have it in gpc-2.2. > [...] > > Assuming our example, the compiler reads the line "inherited > putpixel(..);". It looks for the asmname of graph.putpixel and calls it. > Communication.putpixel then gets its own asmname which has to be different > from the one of graph.putpixel. No problem with this, but what about, say, a `Circle' procedure in `graph.o'? Of course, you want it to use `Communication.PutPixel' instead of `Graph.PutPixel'. This change can only be done if `graph.o' is either recompiled or calls `PutPixel' through a pointer. Since calling functions through pointers is slower than a direct call and has other drawbacks, it is undesireable to make this the default for every unit. A more realistic approach would be to declare `PutPixel' in `Graph' as `virtual', so the compiler will make this one a pointer and assign the default value of `Graph.PutPixel' to it. Perhaps it would be desirable to have this feature built into the compiler, but (sorry if I repeat parts of my last mail): * You can do this manually right now by declaring Var PutPixel: Procedure ( x, y, color: Integer ) value Graph_PutPixel; and setting `PutPixel:= Communication_PutPixel' in the initialization part of the `Communication' unit. * You can do it by letting the unit export an object with a virtual method `PutPixel' and do all your graphics through the methods of this object (in a `with' statement). I am currently writing such a thing - it's much nicer than the "traditional" approach because you can have more than one graphics output device at the same time(-: with Screen^ do begin ClearScreen; Line ( 0, 0, GetMaxX, GetMaxY ); end (* with *); with Printer^ do begin ClearScreen; Line ( 0, GetMaxY, GetMaxX, 0 ); end (* with *); What I mean is: I do not see a real need for such a new feature, so it is, IMHO, not worth the effort to implement it and - perhaps even more important - not worth the problems arising from the introduction of yet more incompatibilities between GPC and other existing compilers and standard specifications. (* But if you are interested in joining the GPC development team for doing the necessary changes to GPC, this would eliminate at least the first argument. ;*) Schoene Gruesse, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Weird ASM error...
by Peter Gerwinski 10 Nov '97

10 Nov '97

According to Orlando Llanes: > I'm using the latest GPC Beta (971101?), and when I type in the following > fragment of code: > > PROGRAM Foo; > BEGIN > asm('movl %eax, 0xa0000' ); > END. > > it compiles fine, but when I run it, the program reports a GPF. [...] This means to store the contents of the `eax' register at the absolute address $A0000. Perhaps you mean `movl $0xA0000, %eax' which means to move the value $A0000 into the `eax' register? Since GPC-compiled programs run in protected mode, you cannot simply access the VGA memory by specifying an absolute address, if that is what you wish to do. Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

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