- Gpc - gnu.de

bug? writing to stdout from c
by Christopher Ferrall 09 Dec '02

09 Dec '02

I get a segmentation fault when writing to stdout or stderr inside a GPC module called from a C program. I guess I have to set something manually that would be set automatically by the pascal main that isn't set by a c main, but I can't find any reference to this problem in the documentation. --Chris Ferrall ---------------------- C main --------------------- #include <stdio.h> extern Bug(); main () { Bug(); } ---------------------- Pascal module ---------------- module bug; uses GPC ; procedure bug; External; procedure bug; var f : text; begin rewrite(f,'cstring.txt'); writeln(f,'writing to text file okay '); close(f); (* Either of the following commands will cause a segmentation fault *) writeln('writing to standard output not okay'); writeln(StdErr,'writing to stderr not okay'); end; end.

2 1

short bunch of questions
by Francois Schoubben 07 Dec '02

07 Dec '02

hello, I'm using gpc on sparc-solaris for 2 mounths... I have a few questions i can't locate in the documentation i found (so RTFM welcome if you point me the so-called FM :-) ). 1. range check and buffer overflow check are in the todo list (7 in planned feature - misc)... But where is the implementation? nowhere? working on? alpha? beta? implemented but option not documented (yes, i'm dreaming a bit ;-) )? 2. with the crt unit, i can't have the accents (é,è and so on)... My students speeks french, so they find it's strange to eat pTt0 and not pâté :) ). Is it possible to display accent (they have xterm and dtterm ) or no way? 3. again with the crt unit, i can't display colors in xterm. Is it normal? It works in dtterm, but the default color is... black (xterm is white, and by default, it is gray). 4. to solve these problems, i tried to compile crt with -DX11, as said in the doc... I had to install pdcurs24 (from the libs directory) but once done, the -DX11 says me that he can't find the xpanel.h (indeed, it doesn't exists on this package, panel.h exists...) the error is: ---- In file included from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/units/crtx.c:35: /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2/units/crtc.c:62: xpanel.h: No such file or directory ---- Thanks for answers... -- Francois Schoubben FUNDP - Namur - Belgium

2 1

Hewlett Packard Pascal compatibility
by John W. Hardy 06 Dec '02

06 Dec '02

A friend of mine wrote an extensive CAD program using HP-Pascal back in the mid 1980s. The program was used exclusively on HP workstations. HP had two variations of Pascal. One was a standalone operating environment, the other worked under HPUX. The CAD program was developed under the workstation version. My friend would like to move this program to the PC world. One approach is "P2C" which converts HP-Pascal code to C. I just discovered GPC and would like to know if it is fairly compatible with HP-Pascal. I'm sure there would be a ton of rewriting that would be necessary whether the P2C or GPC approach is taken, but I would like to get a general idea of GPC compatibility. Thank you very much. John Hardy

6 9

gpc-20021128 (based on gcc-3.2.1): Mingw binaries available
by Prof. A Olowofoyeku (The African Chief) 05 Dec '02

05 Dec '02

Hi all I have put Mingw binaries of the latest gpc snapshot on the gpc web site. This binary package is based on gcc-3.2.1, RC1 (Mingw special), recently released by the Mingw people. You can find the gpc binary here: http://www.gnu-pascal.de/contrib/chief/win32/gcc-3.x/ Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Web: http://www.bigfoot.com/~african_chief/

1 0

Re: Delphi compatibility
by Prof. A Olowofoyeku (The African Chief) 05 Dec '02

05 Dec '02

On 24 Nov 2002, 13:02:36 Martin Liddle wrote: >>On that question the silence of other members of this list has been >>deafening. I can only assume that this is because no-one else is >>interested in Delphi compatibility. If so, then it renders any >>debate moot. If not, then it would be good to hear what others >>think. > >This is free software. The people doing the work are free to do >whatever they want. That is merely to state the obvious - but it is a sad day when this is considered an appropriate response to a question about whether and to what extent a certain feature should be added to GNU software. I didn't think that GNU was about the dictatorship of the maintainers. I doubt that Frank himself would consider the statement: "I do the work, so I can do anything I please" to be sound reasoning or an appropriate response. >Personally I have been happy with Frank's priorities. So have I - and so have (one must assume) most people on this list. That does not dispense with the need sometimes to discuss (and agree or disagree on) important issues. If an issue is important to one person, then it is important and discussion thereon should not be stifled because it irritates, bores, or disinterests others. >I'd much sooner he spent his time working on the compiler than >engage in endless debates on this list. No-one wants to engage in endless debates - and there comes a time when any particular debate must end, and I was the one who brought that one to an end (since it started with a question that I raised). One major difference between liberal and autocratic societies lies in the free flow of information and ideas in the former - even ideas that might be controversial or unpopular. The day that legitimate discussion on difficult or controversial questions becomes stifled or unwanted on this list is the day that I will say goodbye. >For the record, Delphi compatibility would be of some minor interest >to us. This is what I was asking about. And this is the response that answers that question. It is clear that there is little desire here for Delphi compatibility. So be it. At least we now have a clear idea on how people feel about it (presumably those who are silent are not interested). So we can forget about Delphi compatibility, and life can go on. Frank, you're now officially "off the hook", and you can concentrate your efforts on features that people do want ;-). I guess this also signals doom for my "Delphi compatibility" units, which can perhaps quietly disappear. This is not necessarily a bad thing, because I have long been dubious as to whether anyone other than me is using them. I still intend of course to continue to develop them for my own purposes, so those who are interested in them will be able to get updates. Best regards, The Chief --------- Prof. Abimbola Olowofoyeku (The African Chief) Web: http://www.bigfoot.com/~african_chief/

3 4

Definition files for KATE
by Silvio a Beccara 04 Dec '02

04 Dec '02

Hi all, I use Kate (for KDE) to edit GPC programs. Since not all of the keywords of GPC are listed in the definition file for colour evidentiation for Pascal, I was wondering whether someone has written a complete definition file for GPC. Thanks, best wishes Silvio a Beccara - University of Trento, Italy

3 2

GPC on OS X
by Lance Boyle 04 Dec '02

04 Dec '02

Has anyone moved gpc onto Mac OS X and integrated it with Project Builder? Lance

1 0

Kdevelop
by Silvio a Beccara 02 Dec '02

02 Dec '02

Hello everybody, I've recently seen the Kdevelop environment, which seems quite interesting. Is there a (simple) way of using it with GPC? Thanks, best wishes Silvio a Beccara

1 0

text variable interface problem with gpc-20021111
by Martin G C Davies 30 Nov '02

30 Nov '02

Hi, Testing gpc-20021111 I have hit a problem trying to remove duplicate variables. I've produced a cut-down example and the two sources are:- mgcd_module.pas =============== module mgcd_module interface; export mgcd_module = all; var statfile : text; end. module mgcd_module implementation; end. mgcd_program.pas ================ program mgcd_program; import mgcd_module; #if __GPC_RELEASE__ < 20021111 var statfile : text; #endif begin rewrite(statfile, 'mgcd.statfile'); writeln(statfile, 'some stats'); end. I build and run with the command sequence:- gpc -c mgcd_module.pas gpc -c mgcd_program.pas gpc mgcd_program.o mgcd_module.o a.out and I get a core dump with gpc-20021111. I used to get a core dump with earlier versions until I used the kludge of the duplicate variable - but this is now illegal. The underlying problem appears to be something to do with file data structures not being initialized. Thus the above works with:- gpc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.8.1/specs gpc version 2.1 (20020510), based on gcc-2.8.1 but fails with:- gpc -v Reading specs from /ClearCase_01/mgcd/gcc-3.1.1_gpc-20021111_install.dir/lib/gcc-lib/sparc-sun- solaris2.6/3.1.1/specs Configured with: /ClearCase_01/mgcd/gcc-3.1.1/configure --prefix=/ClearCase_01/mgcd/gcc-3.1.1 _gpc-20021111_install.dir : (reconfigured) /ClearCase_01/mgcd/gcc-3.1.1/configure --prefix=/ClearCase_01/mgcd/gcc-3.1.1 _gpc-20021111_install.dir Thread model: posix gpc version 20021111, based on gcc-3.1.1 Hopefully someone can tell me how I can solve/workaround this problem. Martin G C Davies

3 2

gpc-20021128, gcc-3.2.1
by Russell Whitaker 30 Nov '02

30 Nov '02

Hi Reading specs from /usr/local/lib/gcc-lib/i586-pc-linux-gnu/3.2.1/specs Configured with: ../gcc-3.2.1/configure --enable-languages=pascal Thread model: posix gpc version 20021128, based on gcc-3.2.1 1. applied patch manually ( as usual ): ok 2. gpc check with -g 72 fail 3. gpc check with -gstabs 0 fail Russ

1 0