September 1996 - Gpc

Functions/strings
by John Michael Black 23 Sep '96

23 Sep '96

I remember reading in an older version's GUIDE that functions returning strings would not work. Was this corrected with 2.7.2? -john

1 0

Re: some questions ...
by JanJaap van der Heijden 23 Sep '96

23 Sep '96

At 11:15 PM 9/22/96 +0200, you wrote: >Hi Sven, hi everybody, Hello :) > > >> Why is the boolean type internal so big (Integer) ? > >I could not reproduce this bug. Var B: Boolean; writeln ( Sizeof ( B ) ) >yields 1 on my machine. > >> Boolean should only use a bit - yes thats stupid, > This is not so stupid. A 32bit CPU accesses memory in 32bit chunks. It is possible to access a byte, but this is considerably slower. Accessing a bit would require accessing a 32bit word first, then bitshifting. All compilers make this speed v.s. memory-consumption tradeof in favor of speed, and GPC is no exception. For a 64 bit CPU, it's even worse: 63bits per boolean are "waisted". JanJaap -- The latest & greates in software, hardware and manswear -- Bono Vox (U2)

1 0

Known GPC bugs
by Peter Gerwinski 23 Sep '96

23 Sep '96

Hello folks, I updated the "known bugs" section of the Texinfo documentation of the (experimental) gpc-1.2-2.7.2 pre-release. The new file "bugs.texi" can be found at ftp://agnes.dida.physik.uni-essen.de/home/peter/gpc-2.7.2/bugs.texi Other doc files got some minor changes, too. I included a link to the GPC documentation into the GPC home page, http://home.pages.de/~GNU-Pascal/ which is actually an alias to http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ See you, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Re: |||||||||| Free Pascal Compiler? ||||||||||
by Peter Gerwinski 23 Sep '96

23 Sep '96

According to Louis Cappitelli: > > On 22 Sep 1996 12:02:40 GMT, in comp.lang.pascal.misc you wrote: > > >Louis Cappitelli (lcappite(a)sprynet.com) wrote: > >> Does anybody know if there is one for DOS or win95? I am taking a > >> course in High School that uses Turbo pascal, but because it's illegal > >> to copy software, I can't work on my program projects at home and test > >> them. Is there something like djgpp c++ compiler or something better? > > > >Get GNU Pascal. It runs on the DJGPP platform for DOS and Win95, > >on the EMX platform for DOS and OS/2 and on any other platform > >supported by the GNU compiler family (e.g. Linux, FreeBSD). > > I got a question. Does it require DJGPP? Yes, you need at least the assembler (as), the linker (ld) and some libraries (libc.a, libm.a, crt0.o, ...) to run the DJGPP version (for DOS) of the GNU Pascal compiler. The C compiler is - of course - not needed. However, djgpp is not really a big packet. You do *not* need DJGPP to run a program *compiled with* GPC. With EMX, you need the EMX development tools (except, again, the C compiler) to compile programs; to run a compiled program you also need the EMX run time system, either an extender program (for DOS) or a DLL (for OS/2). But that's not a problem since the EMX license allows you to distribute the EMX runtime system along with your program. By the way, programs compiled with Borland Pascal also need Borland's runtime system (files RTM.EXE and DPMI16BI.OVL) to run in protected mode. Fortunately, Borland allows its licensed users to distribute them along with their programs. (Also posted to the GPC mailing list.) Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

some questions ...
by Peter Gerwinski 22 Sep '96

22 Sep '96

Hi Sven, hi everybody, > Somebody have found the C2PAS converter? I have never seen such a thing - only the p2c. > Why is the boolean type internal so big (Integer) ? I could not reproduce this bug. Var B: Boolean; writeln ( Sizeof ( B ) ) yields 1 on my machine. > Boolean should only use a bit - yes thats stupid, It's not stupid at all. One day, GPC will actually pack `packed arrays' of Boolean or `packed records' containing Booleans and Integer subranges, then each Boolean will only get a single bit. > Why crashed the compiler very often? If we knew the answer, the compiler wouldn't crash any more, sigh. Please collect the source which makes the compiler crash, so we can correct the bug. > If the compiler found a syntax fault, I think in some cases it's better to > show the fault position in the line. I agree, but I have no idea how to implement this with a Bison parser (I am not so experienced with Bison). Somebody has? > How I can _create_ functions with free type parameters, > _without get a warning_ while using with different typed variabels? This is a bug in GPC and must be fixed. For the moment, use (*$W-*) to switch off annoying warnings, use (*$W+*) to switch them on again. By the way, Sven, your DosFile Unit does not only work around a bug, but it also implements some missing functions such as BlockRead, BlockWrite, and IOresult. Gut gemacht! :-) :-) Shall I put it into a gpc-2.7.2/contrib directory? Somebody out there willing to make it portable? It should not be too difficult to translate the DOS system calls to UNIX system calls. Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

BUG: String schemas as function parameters
by Peter Gerwinski 22 Sep '96

22 Sep '96

Subject: Re: gnu pascal unit problem Newsgroups: comp.os.msdos.djgpp References: <Dxx3Bv.2G5(a)bercos.de> Organization: Universitaet Essen, Germany Reply-To: peter.gerwinski(a)uni-essen.de Distribution: Helge Kruse (hk(a)bercos.de) wrote: > I downloaded the version 1.2-2.7.2 of gpc and tried a unit > sample. But the code won't work. It's so small, that Id like > to post the code here: > program p1; > (* This program does NOT work correctly with GPC 2.7.2 *) > (* compiled with 'gpc --automake p1.pas' the a.out will *) > (* be compiled. But the function u1 in the unit u1 *) > (* does not prints the parameter. *) > (* Renaming the unit, so that unit/function name differ *) > (* gives no success. *) The function u1 accepts a formal parameter of type "String". Other than in Borland Pascal, this does not default to a String of maximum length 255 but stands for a String Schema type which is something more complicated. Indeed, you discovered a bug. Thank you for the report. To work around, use Strings of known maximum length instead of generic String Schemas, i.e. Type WrkString = String ( 80 ); Function u1 ( S: WrkString ): whatever; (Also posted to the GNU Pascal mailing list.) Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Re: gpc under SunOS or Solaris
by Peter Gerwinski 22 Sep '96

22 Sep '96

According to Friedrich Fahnert: > I found a solution for the problem I was having under SunOS. I can get > the program compiled if I specify the source files, to gpc, but not if I > compile the files, and link them separately. Should this be considered > to be a bug? Yes. :-( Thank you for the report. I was reported a similar bug for Linux but could not reproduce it. Strange. Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

some questions ...
by Sven＠rufus.central.de 22 Sep '96

22 Sep '96

Hallo gpc, Somebody have found the C2PAS converter? Why is the boolean type internal so big (Integer) ? Boolean should only use a bit - yes thats stupid, but a byte should work fast and easy !? Why crashed the compiler very often? Yes, I know syntax errors are my faults - but other compilers (you know what I mean) are not so touchy. If the compiler found a syntax fault, I think in some cases it's better to show the fault position in the line. How I can _create_ functions with free type parameters, _without get a warning_ while using with different typed variabels? working example in BP : function SendBuffer(var Buffer; BufferSize: Integer): Integer; My suggestion: function SendBuffer(var Buffer: Void; BufferSize: Integer): Integer; should not generate a warning in using of SendBuffer ... Greetings, Sven ...

1 0

DosFile.pas workaround for the CrLF-bug under old DOS
by Sven＠rufus.central.de 22 Sep '96

22 Sep '96

{ BP-like file operations for binary files } { simple workaround for the CRLF-bug in GCC/GPC } { Sven Hilscher - sven(a)rufus.central.de } unit DosFile; { version 0.01Beta } { provisional arrangement } Interface Type WrkStr = String(255); Pointer = ^void; NameT = array[1..13] of char; BinFile = record Name : NameT; Handle : Integer; BSize : Integer; end; Var IOResultTemp : Integer; procedure Assign(var F: BinFile; Name: WrkStr); procedure Reset(var F: BinFile; RecSize: Integer); procedure Rewrite(var F: BinFile; RecSize: Integer); procedure BlockWrite(var F: BinFile; var Buf: void; Count: Integer; var Result: Integer); procedure BlockRead(var F: BinFile; var Buf: Void; Count: Integer; var Result: Integer); procedure Close(var F: BinFile); function IOResult: Integer; Implementation procedure Assign(var F: BinFile; Name: WrkStr); var i : Integer; begin for i := 1 to 12 do if length(Name) >= i then F.Name[i] := Name[i] else F.Name[i] := chr(0); F.Name[13] := chr(0); F.Handle := 0; end; { functions converted from "dos.h" } function DosOpen(n: Pointer; i: Integer; h: pointer):Integer; AsmName '_dos_open'; function DosCreate(var n: NameT; i: Integer; h: pointer):Integer; AsmName '_dos_creat'; function DosClose(h: Integer): Integer; AsmName '_dos_close'; function DosWrite(h: Integer; b: Pointer; c: Integer; var r: Integer): Integer; AsmName '_dos_write'; function DosRead(h: Integer; b: Pointer; c: Integer; var r: Integer): Integer; AsmName '_dos_read'; procedure Reset(var F: BinFile; RecSize: Integer); begin if F.handle <> 0 then IOResultTemp := DosClose(F.Handle); IOResultTemp := DosOpen((a)F.Name, 0, @F.Handle); F.BSize := RecSize; end; procedure Rewrite(var F: BinFile; RecSize: Integer); begin if F.Handle <> 0 then IOResultTemp := DosClose(F.Handle); IOResultTemp := DosCreate(F.Name, 0, @F.Handle); F.BSize := RecSize; end; procedure Close(var F: BinFile); begin IOResultTemp := DosClose(F.Handle); F.Handle := 0; F.BSize := 0; end; function IOResult: Integer; begin IOResult := IOResultTemp; IOResultTemp := 0; end; procedure BlockWrite(var F: BinFile; var Buf: void; Count: Integer; var Result: Integer); begin IOResultTemp := DosWrite(F.Handle, @Buf, Count * F.BSize, Result); Result := Result div F.BSize end; procedure BlockRead(var F: BinFile; var Buf: Void; Count: Integer; var Result: Integer); begin IOResultTemp := DosRead(F.Handle, @Buf, Count * F.BSize, Result); Result := Result div F.BSize end; begin IOResultTemp := 0; end.

1 0

gpc under SunOS or Solaris
by Peter Gerwinski 21 Sep '96

21 Sep '96

According to Friedrich Fahnert: > I managed to get version 1.2-2.7.2 compiled on both, but neither works > very well. On Solaris gpc1 gets a fatal signal, and an internal > compiler error, when compiling certain programs. On SunOS, it seems > to compile properly, but it dumps core when linking. It would be nice to fix the bugs. If possible, I would like to have a minimum source which still triggers the error. Perhaps we can reproduce the error on other platforms we have access to. > Is there any platform where gpc could be considered to be stable? I tested GPC on various iX86-based platforms, so I'd consider it to be stable on DOS (DJGPP and EMX), OS/2 (EMX), Linux and FreeBSD. Good luck, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0