May 1998 - Gpc

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

Let's write the GPC reference together! (was: gpc-980511 build bug)
by Peter Gerwinski 03 Jun '98

03 Jun '98

Hi, everybody! Miklos Cserzo wrote: > > Before the official release we should do something about the documentation. > It is really poor. Some 160 pages are missing from the language reference. > That is definitely too much writing for a single person but with a joint > effort it should not be a problem. How about to post the missing sections > of the reference to the list? I consider this a VERY GOOD idea! While some nice people are already working on improving the documentation, a joint effort will certainly yield a faster and better result. Of course, such a project must be coordinated; otherwise we will end up with a lot of incompatible fragments. Here are my thoughts about how to do that: * Everyone is encouraged to write or improve sections of the GPC reference, `reference.texi'. The article should be mailed to this list with a subject like GPC REFERENCE: abs It must contain a complete section of `reference.texi' in the standardized format (GNU Texinfo) *including* the separator lines beginning with `@c'. I will post a real-world example in a few minutes. For a description of the GNU Texinfo format, type `info -f texinfo'. * When replying and improving the text, always include a complete snippet as described above without leading `> ' or such. This is to simplify integration into the file `reference.texi'. * Spelling corrections are welcome. And now for some guidelines how the documentation should look like: * Be exact. Examples must work. * Really explain it. "Help" screens like "Use the `Procedure' keyword to declare a procedure" do not help anyone. *Nothing* is self-evident. * Give examples. Besides a tiny easy-to-understand example there should always be a real-world example that helps to avoid pitfalls. (See `info -f gpc -n and' for an example: The first `if' is the easy example, while the `else if' describes a common pitfall. Maybe it would be even better to separate them ...) * Use cross references. When a cross reference appears in the help text, it is usually desirable to repeat it in the `See also' subsection. * Be technical, not personal. For example, I do not like `goto', and I never use it in my programs, but if I explain it, this does not matter. If there are some *technical* drawbacks using `goto' I can mention them, but a sentence telling "better don't use `goto'" causes nothing but confusion. * Read the tips in `info -f texinfo -n Tips'. Comments? An example of what I mean will follow in a few minutes. Also, I am uploading the file `reference.texi' to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/alpha/reference.texi so you do not need to download the whole GPC source just to get your hands on that single file. Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980511 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 5

GPC REFERENCE: abs
by Peter Gerwinski 02 Jun '98

02 Jun '98

Hi! This is an example entry for how I think our joined effort to complete the GPC reference could work. The section I am posting is already in existence (`abs'): @c ---------------------------------------------------------------------------- @node abs @unnumberedsec abs @cindex abs @unnumberedsubsec Syntax @smallexample Function abs ( i: @var{integer type} ): @var{integer type}; @end smallexample or @smallexample Function abs ( x: @var{real type} ): @var{real type}; @end smallexample or @smallexample Function abs ( z: @var{complex type} ): @var{real type}; @end smallexample @unnumberedsubsec Description Returns the absolute value of the argument: @smallexample Function abs ( x: @var{some type} ): @var{some type}; begin (* abs *) if x < 0 then abs:= -x else abs:= x; end (* abs *); @end smallexample @unnumberedsubsec Standards The function @samp{abs} is defined in ISO-7185 Standard Pascal; its application to complex values is defined in ISO-10206 Extended Pascal. @unnumberedsubsec Example @smallexample Program TestAbs; Var i1: Complex; begin writeln ( abs ( 42 ) ); (* 42 *); writeln ( abs ( -42 ) ); (* 42 *); writeln ( abs ( -12.1 : 0 : 1 ) ); (* 12.1 *); i1:= cmplx ( 1, 1 ); (* 1 + i *) writeln ( abs ( i1 ) : 0 : 10 ); (* yields 1.4142135624, i.e. sqrt ( 2 ) *) end. @end smallexample @unnumberedsubsec See also @ref{sqr}. @c ---------------------------------------------------------------------------- If you follow-up to this mail and modify the section, please include a complete copy without leading "> " or such in order to make it easier for me to integrate the modified copy into `reference.texi'. Peter PS: I just was pointed to some errors in the above, so you can expect my own follow-up to this in a few minutes. :-) -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980511 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

Re: egcs-19980517 and gpc-980511
by mrs＠wrs.com 02 Jun '98

02 Jun '98

> From: Matthias Klose <Matthias.Klose(a)cs.tu-berlin.de> > Date: Fri, 22 May 1998 04:43:56 +0200 (MET DST) > To: egcs(a)cygnus.com, gpc(a)hut.fi > After patching the gpc-980511 drop in for egcs, I got a working > egcs-gpc compiler. Some problems remain: > - the gpc testsuite fails with dejagnu-971222, it runs ok with dejagnu-1.3 1.3 is horribly old, and I don't recommend you use it. dejagnu needs a new FSF release to incorporate all the latest good bits that people have put into it. All the people that use dejagnu, use newer snapshots. Please consider upgrading to dejagnu-971222.

3 7

[Off-topic?] Req: Code snippet...
by Orlando Llanes 31 May '98

31 May '98

Hey all! Hopefully I'm not out of place by asking so, but here goes anyway. I'm looking for a snippet of *working* Pascal code using Tim Kientzle's algorithm for Approximate Inverse Color Mapping. If nobody has this, does someone out there at least have a snippet of code that uses Inverse Color Mapping in Pascal to reduce a 24-bit image to an 8-bit image? Thanks in advance! 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

crtf.o
by Bendersky 31 May '98

31 May '98

Hi, I've just upgraded to the last alpha. When trying to compile a program I got this: ****************************** C:\UTILS\GPC\Ariel\Mandel>...\bin\gpc -v --automake=-v mandel1.pas Reading specs from c:/utils/gpc/lib/specs gpc driver version 2.81 executing gpc version 2.8.1 c:/utils/gpc/bin/gpc-cpp.exe -lang-pascal -v -nocharescape -undef -D__GNUC__=2 -D__GPC__=2 -D__GNUC_MINOR__=8 -Dunix -Di386 -DGO32 -DMSDOS -DDJGPP=2 -DDJGPP_MI NOR=1 -D__unix__ -D__i386__ -D__GO32__ -D__MSDOS__ -D__DJGPP__=2 -D__DJGPP_MINOR __=1 -D__unix -D__i386 -D__GO32 -D__MSDOS -D__DJGPP=2 -D__DJGPP_MINOR=1 -D__BITS _LITTLE_ENDIAN__=1 -D__BYTES_LITTLE_ENDIAN__=1 -D__WORDS_LITTLE_ENDIAN__=1 mande l1.pas c:/utils/gpc/tmp/ccbywrgj GNU CPP version 2.81 (80386, BSD syntax) #include "..." search starts here: #include <...> search starts here: c:/utils/gpc/include c:/utils/gpc/lang/pascal c:/utils/gpc/contrib/grx22/include /usr/local/include JDIR/djgpp/include JDIR/lib/gcc-lib/djgpp/2.81/include $DJDIR/include End of search list. c:/utils/gpc/bin/gpc1.exe c:/utils/gpc/tmp/ccbywrgj -quiet -dumpbase mandel1.pa s -version -famtmpfile=mandel1.gpc -fautomake=-v -o c:/utils/gpc/tmp/cccywrgj GNU Pascal version 2.81 (djgpp) compiled by GNU C version 2.8.1. c:/utils/gpc/bin/as.exe -o c:/utils/gpc/tmp/ccdywrgj c:/utils/gpc/tmp/cccywrgj c:/utils/gpc/bin/ld.exe crtf.o c:/utils/gpc/lib/crt0.o -Lc:/utils/gpc/lib -Lc:/ utils/gpc/contrib/grx22/lib -Lc:/utils/gpc/lib/gcc-lib/djgpp/2.81 -Lc:/utils/gpc /lib c:/utils/gpc/tmp/ccdywrgj -lgpc -lm -lgcc -lc -lgcc -Tdjgpp.djl c:/utils/gpc/bin/ld.exe: cannot open crtf.o: No such file or directory (ENOENT) ************************************ I've already compiled the grx20, and that program used to work with gpc 2.0 Also, when trying to compile it under rhide I always get (with every program)" cannot open crtf.o: No such file or directory (ENOENT)" Why is that? Am I doing something wrong? Thanks, Ariel --- Ariel Bendersky bender(a)einstein.com.ar

2 7

Mailing list addition
by Richard Earl Green 30 May '98

30 May '98

Please add me to your mailing list addition. You may have me at 'pslmsngr(a)ix.netcom.com'; please remove this as this is nolonger an open account. My current e-mail account is 'pslmsngr(a)inr.net'. Thanks. Richard Green.

1 0

Re: Executing external programs
by Frank Heckenbach 29 May '98

29 May '98

Geoffrey Arnold wrote: > I have GPC version 2.0 compiled for a 486 running linux. > > How do I execute a external shell script from a pascal program? You can use the system(3) function from libc. The first program passes a Pascal string to a CString parameter which is only supported by very recent (alpha) GPC versions. The second program does the conversion explicitly, and therefore works with older GPC versions as well. I'm not sure if it works with 2.0 since I don't have that here for testing. Anyway, it might be a good idea to get a newer version, which, though alpha, is already more stable than 2.0 was. program Exec_Demo; function System (cmd: CString): Integer; C; var s: String (1000); i: Integer; begin Write ('Enter a system command: '); Readln (s); i := System (s); Writeln ('The returned status of the executed command was ', i, '.') end. program Exec_Demo; function System (cmd: CString): Integer; C; function Str2CStrRO (var s: String): CString; begin s[Length(s)+1] := #0; Str2CStrRo := @s[1] end; var s: String (1000); i: Integer; begin Write ('Enter a system command: '); Readln (s); i := System (Str2CStrRO (s)); Writeln ('The returned status of the executed command was ', i, '.') end. Frank -- Frank Heckenbach, frank(a)pascal.gnu.de http://fjf.gnu.de/ PGP keys: http://pgp5.ai.mit.edu/pks/lookup?op=index&search=Frank+Heckenbach

1 0

gpc-980511 build bug
by Klaus Espenlaub 28 May '98

28 May '98

Hi! just subscribed, so for now it's probably the best solution to send me a direct carbon copy, too. I downloaded gpc-980511.tar.gz, integrated it into gcc-2.8.1, ran configure and "make LANGUAGES=pascal", as suggested by the docs. The make run didn't manage to compile the runtime library, because it uses the --automake option. It tries to compile some dependent modules, but fails, because there is no executable on the system called gpc yet: ./../xgpc -B../../ --automake -c -DGPC -Wall -Wpointer-arith -Wmissing-prototypes -Wmissing-declarations -g -I. -I../.. -I/scratch/s_kespen/gcc-2.8.1/p/rts/../.. -I/scratch/s_kespen/gcc-2.8.1/p/rts/../../config rts-move.p gpc1: installation problem, cannot exec `gpc': No such file or directory gpc1: gpc exited with status 255 gpi-hash.c:329: failed assertion `rp == 0' xgpc: Internal compiler error: program gpc1 got fatal signal 6 make[1]: *** [rts-move.o] Error 1 make[1]: Leaving directory `/scratch/s_kespen/gcc-2.8.1/p/rts' make: *** [libgpc.a] Error 2 I worked around by just doing a "make install", giving me a half-working installed gpc. I reran the gpc build, this time with success. So currently if you start from scratch, you need good two runs to get gpc working. This isn't the ideal situation, but changing it would require a few substantial changes all over the place. You need some means of passing the name of the compiler driver down to the compiler. Then it would be easy to change the code in module.c to accommodate for the different location and name of xgpc. Generally it shouldn't be necessary for gpc to be in the PATH. There's no reason why /some/path/to/my/private/gpc should fail, while just gpc works. There has to be some means of keeping -B and -V options given to gpc initially, too. Otherwise it can be painful to use an different gpc version or a cross-compiler, like in this case a not installed compiler version. Anyway, to summarise all this - building gpc doesn't work correctly even if you have gpc installed previously. As long as some older gpc version is potentially used to compile some parts of the RTS, it's wrong. Older gpc versions may have bugs that are already fixed in the current release - this way they can pop up once more. The automake feature is quite useful as it is, but it needs to be polished a bit to make it robust enough for heavy duty work. Klaus

3 2

Executing external programs
by Geoffrey Arnold 27 May '98

27 May '98

I have GPC version 2.0 compiled for a 486 running linux. How do I execute a external shell script from a pascal program? ----------Geoffrey Arnold--------- ------garnold(a)cyberdrive.net------ http://www.cyberdrive.net/~garnold

1 0