October 2003 - Gpc

C style directives
by Frank Heckenbach 11 Oct '03

11 Oct '03

Since the preprocessor problems have become more urgent with gcc-3.3, the next release of GPC might already contain the new, integrated preprocessor. Since it will be mostly written from scratch, I don't plan to duplicate obsolete features, in particular C style directives. To help your conversion if you still use them, I've written the attached script. It requires *GNU* sed and a Unix-compatible shell. (However, the real work is done by sed, so it can probably be easily "ported" to any other shell, perhaps even to Dos command.com if anyone cares.) GPC supports Pascal directives already for some time, so you can do the conversion now and find out if there are any problems, before you may be forced to do it in a hurry when the next release comes out. The script it a bit simplistic and may not cover every exotic case, but most normal cases. It's recommended to look at the differences of the changed file and the original to be sure. In particular, the script does the following conversions: - One-line: `#foo' to `{$foo}' - Multi-line: #define foo(X) \ X \ Y To: {$define foo(X) X Y} - Include files: `#include "foo.pas"' and `#include <foo.pas>' both to `{$include "foo.pas"}'. (There will be no support for `<>' includes anymore since there are no "system headers" in Pascal. If you've relied on the system header directories, it shouldn't take more than an `-I' option to solve it.) - C operators in conditionals: `&&' to `and', `!' to `not', etc. - Special cases: `#if 0' to `{$if False}' and `#if 1' to `{$if True}'. This does not replace every 0 and 1 in a conditional since it would be much more complicated to decide if they're used as numbers or Booleans (which is the same in C). Since probably almost all Booleans uses of 0 and 1 in conditionals are of the simple form (otherwise they don't make much sense), this shouldn't cause many problems. Please report any problems on this list. Frank -- Frank Heckenbach, frank(a)g-n-u.de, http://fjf.gnu.de/, 7977168E GPC To-Do list, latest features, fixed bugs: http://www.gnu-pascal.de/todo.html GPC download signing key: 51FF C1F0 1A77 C6C2 4482 4DDC 117A 9773 7F88 1707

1 0

gcc/p/units/crtc.c TEST failings
by Gerrit P. Haase 11 Oct '03

11 Oct '03

Hallo, I'm running make check right now and I'm getting a problem with crtc.c. Several hundred lines warnings and errors, in several tests. E.g. the last lines: ... .../gcc/p/units/crtc.c: In function `crt_GetShiftState': .../gcc/p/units/crtc.c:894: warning: implicit declaration of function `PDC_get_key_modifiers' .../gcc/p/units/crtc.c:895: error: `PDC_KEY_MODIFIER_SHIFT' undeclared (first use in this function) .../gcc/p/units/crtc.c:895: error: (Each undeclared identifier is reported only once .../gcc/p/units/crtc.c:895: error: for each function it appears in.) .../gcc/p/units/crtc.c:896: error: `PDC_KEY_MODIFIER_CONTROL' undeclared (first use in this function) .../gcc/p/units/crtc.c:897: error: `PDC_KEY_MODIFIER_ALT' undeclared (first use in this function) .../gcc/p/units/crtc.c:902: error: `PDC_KEY_MODIFIER_NUMLOCK' undeclared (first use in this function) .../gcc/p/units/crtc.c: In function `crt_RawOut': .../gcc/p/units/crtc.c:1571: warning: implicit declaration of function `raw_output' .../gcc/p/units/crtc.c: In function `crt_Init': .../gcc/p/units/crtc.c:1649: warning: implicit declaration of function `PDC_save_key_modifiers' .../gcc/p/units/crtc.c: In function `adjust_panel': .../gcc/p/units/crtc.c:1846: warning: implicit declaration of function `resize_window' .../gcc/p/units/crtc.c:1846: warning: assignment makes pointer from integer without a cast .../gcc/p/units/crtc.c: In function `crt_Check_WinChanged': .../gcc/p/units/crtc.c:1866: warning: implicit declaration of function `is_termresized' .../gcc/p/units/crtc.c:1881: error: structure has no member named `wendy' .../gcc/p/units/crtc.c:1882: error: structure has no member named `wendx' The failing tests (all because of crtc.c) so far are: TEST aturbo3test.pas: TEST crttest.pas: TEST dialec3.pas: TEST dialec5.pas: TEST dialec6.pas: TEST dialec7.pas: Is there something known to do about this? Thanks, Gerrit -- =^..^=

3 9

LSEEK64/FTRUNCATE64 PROBLEM WITH GPC ON CYGWIN
by Pascal Pottier 10 Oct '03

10 Oct '03

Hello All! I'm trying to use gpc under cygwin and have a trouble when compiling/linking even a simple example such as: program test; begin writeln("Hello World") end. gpc test.pas returns the following message: /usr/lib/gcc-lib/i686-pc-cygwin/3.2.3/libgpc.a(rts.o)(.text+0x18ef):rts.c: undef ined reference to `_ftruncate64' /usr/lib/gcc-lib/i686-pc-cygwin/3.2.3/libgpc.a(rts.o)(.text+0x18b4):rts.c: undef ined reference to `_lseek64' collect2: ld returned 1 exit status I have the same message with examples from /usr/doc/gpc/demos. It's seems something is missing in the install for the linker. I'm using (just installed this week): gpc binary: gpc-20030830-with-gcc.i686-pc-cygwin.tar.gz from www.gnu-pascal.de and cygwin: ftp%3a%2f%2fftp.funet.fi%2fpub%2fmirrors%2fcygwin.com%2fpub%2fcygwin latest presently available said as 1.5.5-1 downloaded from ftp.funet.fi after setup.exe 2.415 got from cygwin.com "Install Cygwin now" If you have any idea or know any contact who could help please advice. Thanks for your help!

3 2

Problem with functions in EP modules
by J. David Bryan 07 Oct '03

07 Oct '03

Using: gpc version 20030507, based on gcc-3.2.3 (mingw special 20030504-1) configured as "i486-pc-mingw32" and running under Windows NT 4.0, the "widget_module" example from section 6.4.2.5 of the EP manual fails to compile, as follows: D:\test>gpc --extended-pascal -c widget.pas widget.pas:37: result types in forward declared functions are an extension widget.pas:37: of UCSD Pascal, Borland Pascal, traditional Macintosh widget.pas:37: Pascal The following simplified example exhibits the same behavior: module modbug; export i = (e); function e (v : integer) : integer; end; function e; begin e := 1 end; end. Compiling produces: D:\test>gpc --extended-pascal -c modbug.pas modbug.pas:12: result types in forward declared functions are an extension modbug.pas:12: of UCSD Pascal, Borland Pascal, traditional Macintosh modbug.pas:12: Pascal I do not have a gpc-20030930 implementation to check this against. -- Dave

3 4

Re: reply-to field missing. --> subscribing extra addresses versus alias
by Tom Verhoeff 06 Oct '03

06 Oct '03

Frank Heckenbach wrote: >Each mail from a non-subscribed address needs to be confirmed. If >you use another address regularly, you can subscribe it without >getting the mails as well: > >subscribe-set gpc nomail your(a)second.address > >This command, of course, needs to be confirmed like any other >subscription, but only once. I just played around with the web interface that Majordomo offers. It cannot be found from the gnu-pascal web pages, but you do get the webaddress via help to majordomo(a)gnu.de: <http://adele.gerwinski.de/majordomo/mj_wwwusr/domain=gnu.de> It seems to me that it is more appropriate to set an alias for your extra address, then to subscribe another address, if you want to post from several e-mail address without receiving multiple copies. Aliases can also be set via the mail interface (see help message). Tom

1 0

reply-to field missing.
by CBFalconer 05 Oct '03

05 Oct '03

With the various SWEN viruses and other things, the automatic reply-to: gpc(a)gnu.de field seems to be missing on anything delivered here (cbfalconer(a)worldnet.att.net) Way back when I recall there was some way to set this option on the list, but it is long forgotten. I think there was also a problem because my from: address did not agree with the address to which the mail is delivered. Some items are arriving with that field set here, but so far it is only replies to my own articles. See the "Status of GPC" thread. -- Chuck F (cbfalconer(a)yahoo.com) (cbfalconer(a)worldnet.att.net) Available for consulting/temporary embedded and systems. <http://cbfalconer.home.att.net> USE worldnet address!

2 1

Re: Compiler bugs or missunderstanding GPC
by Frank Heckenbach 05 Oct '03

05 Oct '03

ThomasM wrote: > Perhabs it is possible to "output" qualified messages during > compilation like "Type of ... is ..." or "Size of ... is ..." ? It probably possible -- it's just a matter of effort ... But the size shouldn't actually matter -- the type must match exactly. E.g., this is not valid (but also not in BP): unit Baz; interface type Foo = String[10]; procedure a (b: Foo); implementation type Bar = String[10]; procedure a (b: Bar); begin end; end. Frank -- Frank Heckenbach, frank(a)g-n-u.de http://fjf.gnu.de/ GnuPG and PGP keys: http://fjf.gnu.de/plan (7977168E)

1 0

Compiler bugs or missunderstanding GPC ?
by ThomasM 05 Oct '03

05 Oct '03

Hi ! I've installed mingw32 with gcc 3.2.3 and gpc 20030507 and I am in serious trouble while translating bp-projects to gpc. While compiling I get several "previos declaration does not match" errors within the same unit or across different ones, although the syntax is allright. (An asm-free translation of objects.pas successful compiled only after moving "uses dos" from the "implementation" to the "interface" part) Then there are several "type mismatch" errors in functions with one var-parameter, which I cannot mark as protected. (Someone mentioned this allready, but still noone has replied to it) To get progress in translation I start to compile only single units without linking and then I was fooled sometimes by this error message "--amtmpfile not given". Some units will being compiled and other not like ------------------------------ Unit tv_spr; Interface Const spOk = 1; spAbbruch = 2; spJa = 3; spNein = 4; implementation end. ----------------------------------------- the commandline I used is gpc -c -s --no-typed-address --extended-syntax --ignore-function-results --io-checking --no-stack-checking -march=i486 -mcpu=i486 --unit-path=g: \status\entwicklung\mdmprot\gpc\mdtv_may;g:\status\entwicklung\mdmprot\gpc\md_may;g:\status\entwicklung\mdmprot\gpc\source -Ig:\status\entwicklung \mdmprot\gpc\mdtv_may --cidefine=GPC_USE --cidefine=DPMI --cidefine=NOASM --cidefine=test --cidefine=USE_PDCURSES -- cidefine=LINODATA --cidefine=HARDDUMMY --executable-file-name unit.pas Greetings, Thomas

4 3