Gpc June 2000

gpc@gnu.de

21 participants
52 discussions

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

15 Jun '00

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

2 1

None
by FSR SoWi 15 Jun '00

15 Jun '00

unsubscribe

1 0

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

15 Jun '00

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

1 0

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

15 Jun '00

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

1 0

Pascal support in GDB
by Pierre Muller 15 Jun '00

15 Jun '00

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

4 6

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

15 Jun '00

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

1 0

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

14 Jun '00

Maurice Lombardi wrote: > from the (old) gpc info file: > > The string type in gpc is something equivalent to > > TYPE > STRING = RECORD > Capacity : integer; > length : integer; > string : packed array [ 1..Capacity ] of char; > END; > > In fact I suppose that it is actually cardinal (identical to word), i.e. "unsigned int" in C (this doc is somewhat > outdated). Indeed. The current declaration is: type String (Capacity : Cardinal) = record Length : 0 .. Capacity; Chars : packed array [1 .. Capacity + 1] of Char end; (We added one extra char for easy conversion to CStrings.) > Of course gpc strings can contain any number of #0 inside the actual length. > > On the other hand Pchar exists, with an equivalent (but more understandable) Cstring, to enable interface with C system > functions, and there are lots of conversion functions between the two, but you don't need to know for GDB interface, > they are just like other functions. Yes. There can be no #0's inside CStrings. Of course, they can be stored there -- but then they signify the end of the string, like in C... Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html

1 0

upload ?
by Maurice Lombardi 07 Jun '00

07 Jun '00

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

1 0

Manpage
by Frank Heckenbach 06 Jun '00

06 Jun '00

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

1 0

Re: copyright
by Frank Heckenbach 06 Jun '00

06 Jun '00

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

1 0

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 June 2000