Gpc August 1998

gpc@gnu.de

7 participants
18 discussions

Files
by berend＠beard.nest.nl 01 Feb '02

01 Feb '02

* Moved (from: gpc) by Berend de Boer using timEd 1.10.b3+. Peter Gerwinski wrote in a message to Berend de Boer: PG> I tried to use Extended Pascal "binding" to assign a file PG> variable to an external -- existing -- file. I just copied PG> the "Assign" pro- cedure by Berend as published in PG> borland2ep.doc. It does not always work: I often get a PG> runtime error saying that the file did not exist. If you can repeat it, compile with another Extended Pascal compiler, for example Prospero's one. If that fails too, there is really something wrong with the code. But I suspect gpc. You're using which OS? Groetjes, Berend (-: fido: 2:281/527.23 email: berend(a)beard.nest.nl

4 3

GPC Beta release: gpc-19980830
by Peter Gerwinski 04 Sep '98

04 Sep '98

Hello everybody! A new Beta version of GNU Pascal is now available: gpc-19980830. News ==== Apart from many bug fixes, we have significantly improved GPC's compatibility to Borland Pascal. Things like Extended Pascal's schema types are now more stable, and many functions such as conversion functions between Pascal and C strings are now built in. In particular: - A unit `gpc.pas' is now included which contains declarations of almost all the routines in the run time system. Many of them, including all that are required by the standard, are available without using this unit, but some new extensions, in particular most of the new string, CString and file name routines listed below, are only available when this unit is used. (It is planned to let GPC automatically use this unit in a later version, and then more declarations will go there that are currently built into the compiler.) - BP compatible runtime I/O error handling that is enabled/disabled by the compiler options {$I-} and {$I+}. In "disabled" mode, I/O errors don't cause runtime errors, but can be checked for by the program with the `IOResult' function. - Error messsages of the run time system are now output in the form: "a.out: [internal error:] unknown code in `Write' (#904)" which is closer to the GNU coding standards than the previous format was. - A symbol `__GPC_RELEASE__' is predefined, containing the release date of the GPC version in the format YYYYMMDD. This can be used in units that require certain features of the compiler to make sure they are now compiled with a too old compiler. Such a test might look like the following: {$if __GPC_RELEASE__ < 19980830} {$error This unit requires GPC release 19980830 or newer} {$endif} - New/GetMem/Dispose/FreeMem can now be mixed freely with malloc()/free(), to ease interfacing GPC code to C routines, and with Mark/Release. (The only thing that does not work is free()ing a New/GetMem'ed block between a Mark and the corresponsing Release, something which is not likely to happen unintentionally.) - New compiler options: --autolink (link units as used, but don't recompile them) When several --automake="foo", --autobuild="bar" and --autolink="baz" options are given, the "highest" one is valid, and the options of all of them are collected. --no-automake, --no-autobuild, --no-autolink (each of them disables all of --autolink, --automake and --autobuild) --gnu-pascal (disables any previously selected dialect options) --uses="foo" (automatically use a unit) --longest{int,real}-field-width (specify the field width in Write[ln] of long integer and real types) - String routines: UpCase (B) LoCase UpCaseString LoCaseString UpCaseStr LoCaseStr - CString routines: StrLen (B) StrEnd (B) StrScan (B) StrRScan (B) StrDup StrCmp StrCaseCmp StrPCopy (B) NewCString CString2String String2CString - File and I/O routines and declarations: IOResult (B) InOutRes (B) Erase (B) Rename (B) ChDir (B) MkDir (B) RmDir (B) FileMode (B) Flush (B) FilePos (B) FileSize (B) Truncate (B) Append (B) GPC_StatFS - File name routines and declarations: PathSeparator DirSeparator DirSeparators ExtSeparator DirSelf DirParent NullDevice TTYDevice ConsoleDevice GetCurrentDirectory GetTempDirectory GetTempFileName GetTempFileName_CString Slash2OSDirSeparator OSDirSeparator2Slash Slash2OSDirSeparator_CString OSDirSeparator2Slash_CString FileExists DirectoryExists FSearch (B) FSearch_Executable Expand_Environment FExpand (B) FSplit (B) DirFromPath NameFromPath ExtFromPath OpenDir ReadDir CloseDir - Other routines and declarations: ExitCode (B) ErrorAddr (B) RunError (B) SizeType PtrDiffType High (B) Low (B) Random (B) Randomize (B) Pi (B) DayOfWeek new fields DayOfWeek, MicroSecond in the TimeStamp record Items marked "(B)" are BP compatible routines/declarations. For a more detailed list of fixed bugs and new features, see the GPC TODO list, available online at http://fjf.gnu.de/gpc-todo_toc.html or as Texinfo source at http://fjf.gnu.de/gpc-todo.texi.gz . This version of GPC has been tested with and is expected to work on Linux on the Pentium and the Alpha platform, but there are known problems with packed arrays and "long" data types on 64-bit machines like the Alpha. The GNU Pascal development team welcomes the new members Nick Burrett and Matthias Klose. Where to get it =============== The source is available from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/gpc-19980830.tar.gz . Binaries for DOS (DJGPP), and Linux (ELF) will follow as soon as possible and will be announced separately. Acknowledgement =============== I still have lost overview, but the GNU Pascal development team thanks everybody who helped us by contributing useful ideas and reporting bugs. Thanks to all of you! Greetings, The GNU Pascal Development Team Peter, Frank, Matthias, Jan-Jaap, and Nick -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 Fight the SPAM and UBE! - http://spam.abuse.net/ - http://maps.vix.com/

3 4

Documentation
by Paul Doerwald 04 Sep '98

04 Sep '98

Since it is widely grokked that community efforts (especially in the software industry) work better than individual efforts, Peter and I have been discussing how we can, as a community, best work on the GPC documentation. Here is an idea that we came up with: Rather than a web-based form like I suggested, we propose an e-mail based system. With a simple syntax, you can request a portion of the GPC reference documentation, and it will be e-mailed back to you. You can reply, quote the text, and edit what you like, and when you send it back, your changes will be automatically added to the official GPC (texinfo) documentation, and will also be kept online in an HTML format so that everyone has immediate access to your contribution. This way we can all contribute to the GPC documentation effectively. Any thoughts? | clavicle(a)niagara.com "The LORD is my strength and my | www.niagara.com/~clavicle song; he has become my salvation." | ICQ#13902938 Exodus 15:2b

2 1

gpc-19980830 binaries for Linux
by Peter Gerwinski 02 Sep '98

02 Sep '98

Hi, folks! Two binary distributions of gpc-19980830 for i586-pc-linux-gnulibc1, one based on gcc-2.8.1 and one on egcs-2.91.55, are being uploaded to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/binary/ . Greetings, Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 Fight the SPAM and UBE! - http://spam.abuse.net/ - http://maps.vix.com/

2 1

GPC version question...
by Orlando Llanes 26 Aug '98

26 Aug '98

What's the name of the most recent patch (ok, I'm feeling a bit adventurous here now :P) or binary for GPC? I downloaded the 98-05-11 release (installed *after* DJGPP 2.8.1 and all its tools were installed), is that the most recent one? If so, I can't figure out why I get the "unit information deterioration" bug. Could installing GPC over DJGPP be the reason? Should I leave GPC in its own directory? See ya! Orlando Llanes "Meine Damen und Herren, Elvis hat soeben das Gebaeude verlassen!" "Look out fo' flyeeng feet" O__/ a010111t(a)bc.seflin.org \/|____. O <__. \/\> / \ ____________|___\______ http://ourworld.compuserve.com/homepages/Monkey414

2 2

Re: RunError
by Frank Heckenbach 22 Aug '98

22 Aug '98

Orlando Llanes wrote: > Is it possible to hook the RunError in GPC? I would definitely be > interested in a feature like that so that custom handlers can be used. If you mean the RunError procedure, yes (just write your own RunError procedure :-). If you mean the runtime error handling in general, no, not yet (except by modifying the RTS itself). For the time after GPC 2.1, I'm planning some form of exception handling like Delphi or Java which would make this possible. > Awesome 8o~~~ (<--- Drooling with goofy eyes) I think the C workaround > was not a good work-around anyway, I got weird results using them, for a > text file (for example) it worked fine, but (also for example) the pcx > encoder didn't properly encode a file despite using a proven algorithm. I didn't look to closely at the code, so I don't know if there were any problems with it. Another possible problem, if e.g. the code was tested with TP, is the different sizes of data types in GPC, buf I suppose you've thought of that... > I'm trying to eliminate > warnings wherever possible without requiring special command-lines :) Yes, me too. Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: RunError
by heckenb＠helena.hut.fi 22 Aug '98

22 Aug '98

Peter Gerwinski wrote: > > BTW, (Peter:) BP accepts "RunError" without an argument, so GPC should > > allow that, too. However, BP gives a "Runtime Error 0" then, which I don't > > like very much, since the exit status 0 usually means success. So, GPC > > should probably use some other error code... > > Which one? I'd say one in the "unsorted errors" range 0..99, perhaps 99 -- or 42. ;-) -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

3 2

Re: Weird error...
by Frank Heckenbach 22 Aug '98

22 Aug '98

Orlando Llanes wrote: > I got the following error: > > testpcx.pas:4: storage class specified for parameter `Close' Can't reproduce this one with my current version, so I assume it's been fixed by now. Much has changed since the last release, and this was probably among the bug fixes made. BTW (seeing the contents of edsys.pas and edfile.pas): GPC does support untyped files and BlockRead/BlockWrite (already since January), so there's actually no reason for you to do these workarounds you do with C files and direct libc calls. (And FillChar is build in which is internally the same as memset.) > testpcx.pas: In function `program_Testpcx': > testpcx.pas:33: warning: passing arg 4 of `Pcxencode' from incompatible > pointer type > > I have simplified the source as much as possible while leaving the > source structure as is to reproduce the error. I'm using GPC 2.8.1 under > DOS. The warning on line 33 is insignificant as far as I know, I'm passing > an address, and the routine expects a pointer. The warning is correct. You pass a pointer to EDUInt8 and the routine expects a PArray8 which is a quite different type. (Not all pointer types are the same in Pascal!) To get rid of the warning, you can use type casting. > BTW, if you recall, I got an error a long time ago about an empty > record. I found a way around that, I left the unit to keep up the source > structure, but I defined everything in an include file and included it > into the unit itself, now I don't have that problem anymore (I hope :}). This bug should have been fixed in the next version, too. (I had a lot of problems with various instances of this bug, too...) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

2 1

Re: RunError
by Frank Heckenbach 22 Aug '98

22 Aug '98

Peter Gerwinski wrote: > Frank Heckenbach wrote: > > I (Peter Gerwinski) wrote: > > > > BTW, (Peter:) BP accepts "RunError" without an argument, so GPC should > > > > allow that, too. However, BP gives a "Runtime Error 0" then, which I don't > > > > like very much, since the exit status 0 usually means success. So, GPC > > > > should probably use some other error code... > > > > > > Which one? > > > > I'd say one in the "unsorted errors" range 0..99, perhaps 99 -- or 42. ;-) > > What about 81 (assertion failure)? Don't think so. It's got nothing do to with assertions -- or rather, it might have, but then, it might be something completely different. It's up to the programmer what s/he uses this error for... I think 80 (call to predefined procedure `Bug') would be closer. AFAICS, there's no predefined procedure `Bug' currently. Does the standard or some dialect demand one? If not, we could use that and replace `Bug' by `RunError'. But we can just as well use a new error code (error codes are not a scarce resource -- we have the full Integer range available, and currently only nearly 200 out of the first 1000 are used ;-)... And apropos assertions: it's easy to write a procedure for runtime assertions, like the following: procedure Assert (Condition : Boolean; const Message : String); begin if not Condition then Runtime_Error_CString (81, Message) end; (changing the text of the error message to "failed assertion `%s'"). Should I put this routine into the RTS? (This would also make it easier to change the error number, when the error numbers are rearranged.) Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Weird error...
by Orlando Llanes 21 Aug '98

21 Aug '98

I got the following error: testpcx.pas:4: storage class specified for parameter `Close' testpcx.pas: In function `program_Testpcx': testpcx.pas:33: warning: passing arg 4 of `Pcxencode' from incompatible pointer type I have simplified the source as much as possible while leaving the source structure as is to reproduce the error. I'm using GPC 2.8.1 under DOS. The warning on line 33 is insignificant as far as I know, I'm passing an address, and the routine expects a pointer. BTW, if you recall, I got an error a long time ago about an empty record. I found a way around that, I left the unit to keep up the source structure, but I defined everything in an include file and included it into the unit itself, now I don't have that problem anymore (I hope :}). 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

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