Gpc December 1997

gpc@gnu.de

24 participants
76 discussions

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

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 December 1997