Gpc July 1999

gpc@gnu.de

24 participants
40 discussions

Structure of GPC.
by Alejandro Villarroel 20 Jul '99

20 Jul '99

Hi Peter, I going to copy all the structure of directories and files. C:\gpc\BIN C:\gpc\info C:\gpc\LIB C:\gpc\libc C:\gpc\Unit C:\gpc\Include C:\gpc\djgpp.env C:\gpc\BIN\exe C:\gpc\BIN\OUT C:\gpc\BIN\PAS C:\gpc\BIN\GO.BAT C:\gpc\BIN\JUA.BAT C:\gpc\BIN\BPC.EXE C:\gpc\BIN\EPC.EXE C:\gpc\BIN\GPC.EXE C:\gpc\BIN\PC.EXE C:\gpc\BIN\as.exe C:\gpc\BIN\GPC-CPP.EXE C:\gpc\BIN\RHIDE.EXE C:\gpc\BIN\gdb.exe C:\gpc\BIN\sal.exe C:\gpc\BIN\GPC1.EXE C:\gpc\BIN\ld.exe C:\gpc\BIN\stubify.exe C:\gpc\BIN\example.exe C:\gpc\BIN\CRT0.O C:\gpc\BIN\gpc.o C:\gpc\BIN\gmp.o C:\gpc\BIN\EXAMPLE.PAS C:\gpc\BIN\GPC.PAS C:\gpc\BIN\GMP.PAS C:\gpc\BIN\LEAME.TXT C:\gpc\Include\_ansi C:\gpc\Include\ar.h C:\gpc\Include\assert.h C:\gpc\Include\bios.h C:\gpc\Include\coff.h C:\gpc\Include\conio.h C:\gpc\Include\crt0.h C:\gpc\Include\ctype.h C:\gpc\Include\dir.h C:\gpc\Include\direct.h C:\gpc\Include\dirent.h C:\gpc\Include\dos.h C:\gpc\Include\dpmi.h C:\gpc\Include\errno.h C:\gpc\Include\fcntl.h C:\gpc\Include\file.h C:\gpc\Include\float.h C:\gpc\Include\fnmatch.h C:\gpc\Include\ftw.h C:\gpc\Include\getpagesize.h C:\gpc\Include\glob.h C:\gpc\Include\go32.h C:\gpc\Include\gppconio.h C:\gpc\Include\grp.h C:\gpc\Include\ieeefp.h C:\gpc\Include\io.h C:\gpc\Include\keys.h C:\gpc\Include\limits.h C:\gpc\Include\locale.h C:\gpc\Include\malloc.h C:\gpc\Include\math.h C:\gpc\Include\mem.h C:\gpc\Include\memory.h C:\gpc\Include\mntent.h C:\gpc\Include\osfcn.h C:\gpc\Include\pc.h C:\gpc\Include\process.h C:\gpc\Include\pwd.h C:\gpc\Include\random.h C:\gpc\Include\regex.h C:\gpc\Include\search.h C:\gpc\Include\setjmp.h C:\gpc\Include\share.h C:\gpc\Include\signal.h C:\gpc\Include\std.h C:\gpc\Include\stdarg.h C:\gpc\Include\stddef.h C:\gpc\Include\stdio.h C:\gpc\Include\stdlib.h C:\gpc\Include\string.h C:\gpc\Include\strings.h C:\gpc\Include\stubinfo.h C:\gpc\Include\termios.h C:\gpc\Include\time.h C:\gpc\Include\tzfile.h C:\gpc\Include\unistd.h C:\gpc\Include\utime.h C:\gpc\Include\values.h C:\gpc\Include\varargs.h C:\gpc\Include\wctype.h C:\gpc\Include\wchar.h C:\gpc\info\dir C:\gpc\info\INFVIEW.ENG C:\gpc\info\INFVIEW.GER C:\gpc\info\gpc.inf C:\gpc\info\EDITOR.INF C:\gpc\info\INFVIEW.INF C:\gpc\info\RHIDE.INF C:\gpc\info\gpc.i1 C:\gpc\info\gpc.i10 C:\gpc\info\gpc.i11 C:\gpc\info\gpc.i12 C:\gpc\info\gpc.i13 C:\gpc\info\gpc.i14 C:\gpc\info\gpc.i15 C:\gpc\info\gpc.i2 C:\gpc\info\gpc.i3 C:\gpc\info\gpc.i4 C:\gpc\info\gpc.i5 C:\gpc\info\gpc.i6 C:\gpc\info\gpc.i7 C:\gpc\info\gpc.i8 C:\gpc\info\gpc.i9 C:\gpc\info\INFVIEW.SPA C:\gpc\LIB\specs C:\gpc\LIB\libgpc.a C:\gpc\LIB\libm.a C:\gpc\LIB\libdbg.a C:\gpc\LIB\libc.a C:\gpc\LIB\libemu.a C:\gpc\LIB\libg.a C:\gpc\LIB\libpc.a C:\gpc\LIB\libgcc.a C:\gpc\LIB\djgpp.djl C:\gpc\LIB\dxe.ld C:\gpc\LIB\crt0.o C:\gpc\LIB\gcrt0.o C:\gpc\libc\specs C:\gpc\libc\libc.a C:\gpc\libc\libdbg.a C:\gpc\libc\libemu.a C:\gpc\libc\libg.a C:\gpc\libc\libm.a C:\gpc\libc\libpc.a C:\gpc\libc\djgpp.djl C:\gpc\libc\dxe.ld C:\gpc\libc\crt0.o C:\gpc\libc\gcrt0.o C:\gpc\Unit\crtc.c C:\gpc\Unit\dosc.c C:\gpc\Unit\getoptc.c C:\gpc\Unit\pexecutc.c C:\gpc\Unit\pipec.c C:\gpc\Unit\regexc.c C:\gpc\Unit\crtx.c C:\gpc\Unit\crtc.h C:\gpc\Unit\crtdospc.h C:\gpc\Unit\crtdummy.h C:\gpc\Unit\crtlinux386.h C:\gpc\Unit\crtunix.h C:\gpc\Unit\crtunix1.h C:\gpc\Unit\getopt.h C:\gpc\Unit\pexecute.h C:\gpc\Unit\crt.inc C:\gpc\Unit\dos.pas C:\gpc\Unit\crt.pas C:\gpc\Unit\dosunix.pas C:\gpc\Unit\getopt.pas C:\gpc\Unit\gmp.pas C:\gpc\Unit\gpc.pas C:\gpc\Unit\gpcutil.pas C:\gpc\Unit\internal.pas C:\gpc\Unit\overlay.pas C:\gpc\Unit\pexecute.pas C:\gpc\Unit\pipe.pas C:\gpc\Unit\ports.pas C:\gpc\Unit\printer.pas C:\gpc\Unit\regex.pas C:\gpc\Unit\strings.pas C:\gpc\Unit\system.pas C:\gpc\Unit\turbo3.pas C:\gpc\Unit\windos.pas Peter Gerwinski wrote: > Alejandro Villarroel wrote: > > command line> gpc -v --automake example.pas -o example > > error> > > Reading specs from c:\gpc\lib\specs > > gpc version 19990503, based on gcc-2.8.1 > > c:\gpc\bin\gpc-cpp.exe [...] > > Okay, this should be in a directory like > c:\djgpp\lib\gcc-lib\djgpp\2.81\ . Obviously something > is wrong with your installation ... > > What else do you have in your c:\gpc directory? A complete > DJGPP installation (with `djgpp.env' etc.)? > > Does your installation come with a `gpc.pas' file? > > It seems as if you are not using a distribution from our main > server ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/ . Where > did you get yours from? I recommend to retry with an archive > from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/binary/ . > > Peter > > -- > Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ > Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 > PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 > *** Vote against SPAM! ********* http://www.politik-digital.de/spam/ ***

2 1

Still bothering with the Units.
by Alejandro Villarroel 20 Jul '99

20 Jul '99

Ok. Peter, I'm going to put what the compiler says with those commands you gave me. But first, I think it's related with djgpp.env, I write there the lines the info files said about it. I don't have there the units directory, but the compiler and library paths. Another thing I'll appreciate is if you can tell me the directory and files I need in order to run properly GPC, I guess I have files missing. I read the info files, but finally I build up the directories and put there the files I thought were the proper ones. I guess I had to tell this before. Well to the point. 1. First try. command line> gpc --automake example.pas -o example error> example.pas:3: module/unit `gpc' could not be compiled 2. Second try. command line> gpc -v --automake example.pas -o example error> Reading specs from c:\gpc\lib\specs gpc version 19990503, based on gcc-2.8.1 c:\gpc\bin\gpc-cpp.exe -lang-pascal -v -nocharescape -D__GNU_PASCAL__ -undef -D __GNUC__=2 -D__GNUC_MINOR__=8 -D__GPC__=2 -D__GPC_MINOR__=0 -D__GPC_RELEASE__=19 990503 -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MINOR=2 -D__OS_DOS__=1 -D_ _unix__ -D__i386__ -D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D__DJGPP_MINOR__=2 -D__ OS_DOS__=1 -D__unix -D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=2 -D __BITS_LITTLE_ENDIAN__=1 -D__BYTES_LITTLE_ENDIAN__=1 -D__WORDS_LITTLE_ENDIAN__=1 example.pas c:/gpc/bin/RHbaaaaa\cccaaaaa GNU CPP version 2.8.1 (80386, BSD syntax) #include "..." search starts here: #include <...> search starts here: c:/gpc/lang/pascal c:/gpc/include c:/gpc/contrib/grx20/include /usr/local/include $DJDIR/djgpp/include $DJDIR/lib/gcc-lib/djgpp/2.81/include /usr/include End of search list. c:\gpc\bin\gpc1.exe c:/gpc/bin/RHbaaaaa\cccaaaaa -m486 -malign-jumps=2 -malign- loops=2 -malign-functions=2 -m486 -malign-jumps=2 -malign-loops=2 -malign-functi ons=2 -quiet -dumpbase example.pas -version -famtmpfile=c:/gpc/bin/RHbaaaaa\ccaa aaaa.gpc -fautomake -o c:/gpc/bin/RHbaaaaa\ccdaaaaa GNU Pascal version 2.8.1 (djgpp) compiled by GNU C version 2.8.1. example.pas:3: module/unit `gpc' could not be compiled

2 1

Re: Pascal Bug
by Frank Heckenbach 20 Jul '99

20 Jul '99

Ricky W. Butler wrote: > The following program: > > program bug(input,output); > var > x : real; > > begin > x := 0.5000000000000E+00; > writeln(' x = ',x:10:3); > end. > > incorrectly prints out > > x = 5.000 > > It should print out > > x = 0.500 This seems to be a severe bug. Thanks for pointing it out. It has been added to our test suite (rick1.pas), and will hopefully be fixed soon. As a work-around, you could use `E-00' instead of `E+00' (or no exponent at all)... 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

Re: About Units.
by Alejandro Villarroel 19 Jul '99

19 Jul '99

Peter Gerwinski wrote: > > Hi Peter, thanks a lot for your help. By the wat I'm using Rhide, and I > > put this in the compiler options --automake, and this time it said that it > > can not compile the module/unit gpc > > RHIDE can add `--automake' automatically. Remove it from the > compiler options, and instead define a "Pascal primary file" in > the "Project" menu. In the Project menu, there is a options called primary file, what exactily I have to write there? the name of the *.pas file? because I did that and the it said that It cannot import the Module/unit gpc. > > Peter > > -- > Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ > Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-19990118 > PGP key on request - 6C 94 45 BE 28 A4 96 - 0E CC E9 12 47 25 82 75 > *** Vote against SPAM! ********* http://www.politik-digital.de/spam/ ***

2 1

About Units.
by Alejandro Villarroel 19 Jul '99

19 Jul '99

I apologize for my questions but I'm just starting to use GNU pascal. I have this problem, I'm using a very small test program like this: program example; uses gpc; var a:integer; Begin a:=1; writeln('Hello'); end. But when I tried to compile this programa it said that It cannot import gpc module/unit, I tried with other units with the same result. { By the way the units (in the unit directory) are *.pas, right? } What I have to do?

2 1

Re: Modules/Units.
by Frank Heckenbach 15 Jul '99

15 Jul '99

Alejandro Villarroel wrote: > Hello. I'm a beginner with Gnu Pascal, so I have the binary file > gpc.exe and the other files like pc.exe, bpc.exe epc.exe I know there > are subtle dirfferences between them, can you tell me wich are. pc compiles Standard Pascal, epc Extended Pascal (both according to the official standards), bpc is as compatible to Borland/Turbo Pascal as possible (which means, less conforming to the standard), and gpc (the default) provides the union of all those standards and dialects plus some extensions. The same can be achived with the command line switches `--standard-pascal', `--extended-pascal', `--borland-pascal' and `--gnu-pascal' (the latter is the default, so it isn't needed normally). The switches should be preferred, because we're thinking about dropping the separate executables in future versions. I can't describe all the features here, of course, but you can find a list of some interesting features of each and some demo programs in http://home.pages.de/~GNU-Pascal/about.html Besides, the GPC info lists all built-in identifiers and reserved words, and mentions to which language versions they belong (at least, for most of them, some may still be missing). In general, it's best to use the default (i.e., all GPC features), unless standard conformant programs have to be written (`--standard-pascal' or `--extended-pascal' then), or BP programs with many "dirty tricks" should be ported with minimal effort (`--borland-pascal' then). > Well, > in Turbo Pascal, there is a directory named units, where all the .tpu > files live. I guess, that I have to compile the source files in the > include directory that came with the gpc files . In the recent GPC releases (e.g. GPC-19990118) the units are in a directory `units', not `inlcude'. > I've tried to compile > and link gpc.pas, but the followwing error message appear: > > In the command line: > gpc -m486 -O gpc.pas -Ic:\gpc\include -Lc:\gpc\lib -o exe\gpc.o Units can't be linked, only programs (and dynamic libraries) can. Therefore, use the `-c' switch (compile only). Besides, the `-m486' switch should be unnecessary as well as the `-I' and `-L' switches if you install GPC into the default directories below your DJGPP directory (assuming you're using the DJGPP version). However, you can also compile any program with the `--automake' switch, and all needed units will be compiled automatically (if you have the units installed in a non-default directory, you can specify the path with `--unit-path=/foo/bar/baz'). So, normally you won't have to care about compiling the units. > By the way, I've used Rhide 1.4 before, with the same result. > Speaking about rhide..., I have only configured the directories, but > what with the rest, is there something important that I have to put in > the other menus? I don't think so, but with a new release of GPC, you should create a file named rhide.env in %DJDIR%/share/rhide/, containing the following line: RHIDE_COMPILE_LINK_PASCAL_AUTOMAKE=$(RHIDE_LD_PASCAL) $(RHIDE_LIBDIRS) $(RHIDE_LDFLAGS) -o $(OUTFILE) --automake $(RHIDE_GPC_FLAGS) $(SOURCE_NAME) $(RHIDE_LDFLAGS) 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

Re: symbol out of scope
by Frank Heckenbach 15 Jul '99

15 Jul '99

Peter Gerwinski wrote: > Other compilers that cannot handle sets with limits outside > 0..255 have the same problem but do not warn. So there is a > lot of existing code with this problem. BP does at least a bit of checking when overflow checking is turned on, but it's a bit buggy... 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

Modules/Units.
by Alejandro Villarroel 15 Jul '99

15 Jul '99

Hello. I'm a beginner with Gnu Pascal, so I have the binary file gpc.exe and the other files like pc.exe, bpc.exe epc.exe I know there are subtle dirfferences between them, can you tell me wich are. Well, in Turbo Pascal, there is a directory named units, where all the .tpu files live. I guess, that I have to compile the source files in the include directory that came with the gpc files . I've tried to compile and link gpc.pas, but the followwing error message appear: In the command line: gpc -m486 -O gpc.pas -Ic:\gpc\include -Lc:\gpc\lib -o exe\gpc.o Message crt0.o(.data+0xc2):crt0.s: undefined referenc c:\gpc\lib/libc.a(crt1.o)(.text+0x446):crt1.c Presione cualquier tecla para continuar . . . By the way, I've used Rhide 1.4 before, with the same result. Speaking about rhide..., I have only configured the directories, but what with the rest, is there something important that I have to put in the other menus? Thanks in Advance, Alejandro Villarroel

1 0

Re: symbol out of scope
by Frank Heckenbach 15 Jul '99

15 Jul '99

Peter Gerwinski wrote: > Leonardo A. Saravia wrote: > > I have just installed gpc-19990118.i386-pc-djgppv201.zip and try to compile > > a program designed for VMS (VAX) or CMS (IBM) operative systems. I will > > appreciate some help, it seems to be a configuration problem, and I am new > > with Pascal and GNU Pascal. > > > > autocor.pas: In function `Add': > > autocor.pas:311: warning: constructing limited integer set `0..255' > > These warnings are coming from sets like "[ i ]" where `i' is a > variable of plain integer type. GPC cannot currently handle > "set of Integer" and warns about the restriction of the valid > scope for `i'. > > Maybe we should take out this warning - it is somewhat too > verbose ... I don't think so, since it can be a real problem, if I understand it correctly. If i is < 0 or > 255, the result will be wrong, right? However, if i is declared as 0 .. 255 rather than Integer, this is safe (modulo GPC's missing range checking :-/), and there is no warning. However^2, GPC will soon know `Include' and `Exclude' (compatible to BP 7) which will be able to handle out of range values correclty (i.e., cause a runtime error or ignore them, but not cause a wrong result). And perhaps, some day, GPC will be able to handle sets of dynamic size, and `[i]' with i : Integer will work without problems... 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

2 1

symbol out of scope
by Leonardo A. Saravia 14 Jul '99

14 Jul '99

Hi, I have just installed gpc-19990118.i386-pc-djgppv201.zip and try to compile a program designed for VMS (VAX) or CMS (IBM) operative systems. I will appreciate some help, it seems to be a configuration problem, and I am new with Pascal and GNU Pascal. autocor.pas: In function `Add': autocor.pas:311: warning: constructing limited integer set `0..255' autocor.pas:313: warning: constructing limited integer set `0..255' autocor.pas: In function `Sub': autocor.pas:320: warning: constructing limited integer set `0..255' autocor.pas:322: warning: constructing limited integer set `0..255' autocor.pas: In function `Ajoute': autocor.pas:329: warning: constructing limited integer set `0..255' autocor.pas: In function `Enleve': autocor.pas:336: warning: constructing limited integer set `0..255' autocor.pas: In function `Initbit': autocor.pas:1602: warning: constructing limited integer set `0..255' c:/djgpp/tmp\ccdaaaaa: Assembler messages: c:/djgpp/tmp\ccdaaaaa:17201: Fatal error: C_EFCN symbol out of scope Thanks Leonardo A. Saravia - Programa de Invest. en Ecologia Matematica Universidad Nacional De Lujan - C.C. 221 - (6700) - Lujan - Argentina Tel: 54 2323 423171/421030 Fax: 54 2323 425975 e-mail: lsaravia(a)mail.retina.ar

2 1

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 July 1999