- Gpc - gnu.de

Dynamic arrays dimensions
by Silvio a Beccara 13 Jan '06

13 Jan '06

Good morning, what is the maximum dimensions of a GPC dynamic array? In one of my codes, which used to compile fine with following GPC version: gpc version 2.1 (20020510), based on 2.95.2 19991024 I have the following dimensioning: type PMatr3Dob10 = ^TMatr3Dob10; TMatr3Dob10 (Size1, Size2, Size3: Integer) = array [ 0 .. Size1, -1..Size2, 0..Size3 ] of double; var jaekets: PMatr3Dob10; [ ... ] new ( jaekets, dim1, 4 * neact, 1000 ); where dim1 = 100000, neact=2 Now, with GPC version 20050331, based on gcc-3.4.3, I get the following error: value out of range (error #300 at 80c00b8) Is there a way of overcoming this limitation? Thanks and regards Silvio a Beccara -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Jamba: Personalizza il tuo cellulare con le TOP suonerie! * La prima suoneria è GRATIS! Scaricala ORA! Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=3604&d=13-1

3 2

Where is documentation for "new argument to _p_initialize (@)"
by lanceboyle＠qwest.net 13 Jan '06

13 Jan '06

According the document "2 New Features of GNU Pascal," a new feature is "new argument to _p_initialize (@)," where the @ signals a backward incompatibility. However, I can't find any documentation on the new feature. I'm trying to understand the demo code in gpc_c_c.c and its related files, wherein the line _p_initialize (argc, argv, envp, 0); appears. I'm attempting to emulate the C code in Ada, and the Ada compiler tells me "too many arguments in call" when I call it with four arguments. I'm confuzzled. Does gpc_c_c.c still work, calling _p_initialize with four arguments/ Here are the relevant lines from the Ada part: procedure p_initialize; pragma Import(Convention => C, Entity => p_initialize, Link_Name => "__p_initialize"); p_initialize (Argument_Count + 1, Command_Name, null, 0); Jerry

2 1

sockets
by Thys Meintjes 12 Jan '06

12 Jan '06

Hello All, I cannot seem to find a standard socket or sockets unit in the gpc unit library. It's not possible that a modern implementation of any language can lack this functionality in it's standard libraries, so, the problem must be me. Is the socket functionality hosted in another unit or is there some other standard way to implement network functionality in gpc ? I'd prefer using gpc above freepascal as all my other code targets the gcc platform. I really like the idea of linking to colleagues c and pascal libraries (I've yet to determine if this is possible with fpc). I got a fpc socket example up and running within 5 minutes of downloading fpc, I scrounged the web for 2 hours trying to find a gpc socket example with no luck... regards Thys

2 1

Success!
by Peter N Lewis 11 Jan '06

11 Jan '06

Thanks to all the help from Frank, Waldek, Adriaan, Gale and others, I now have all of Interarchy compiling and running under GPC. 270 files, 160,000 lines of code, 290 Mac Style object types, all compiling and working. There are probably a few glitches left here or there, but I've tested out the bulk of the program and nothing remains broken (that was not before - it is bug for bug compatible ;-). Thanks all! Peter. -- <http://www.stairways.com/> <http://download.stairways.com/>

6 5

Type-inquiry ISO compliance bugs
by Gale Paeper 10 Jan '06

10 Jan '06

ISO 10206, paragraph 6.4.9, requires a type-inquiry's type-inquiry-object be either a variable-name (i.e., [imported-interface-identifier '.']variable-identifier) or a parameter-identifier (with a defining point in the closest-containing formal-parameter-list). GPC has a few bugs in enforcing that requirement. As the following test programs demonstrate, GPC will erroneously also accept constant-identifiers, literal numbers, and field-designators as type-inquiry-objects. {$extended-pascal} program gale9 (output); const c = 2; var y : type of c; {WRONG} {c is neither a variable-identifier or a parameter-identifier} begin writeln('FAIL'); end. {$extended-pascal} program gale10 (output); var y: type of 3.14; {WRONG} {3.14 isn't an identifier at all let alone being either a variable-identifier or a parameter-identifier} begin writeln('FAIL'); end. {$extended-pascal} program gale11 (output); var x: record f : integer; end; y: record f1: type of x.f; {WRONG} {x.f is a field-designator which isn't a variable-identifier or parameter-identifier} end; begin writeln('FAIL'); end. Note: I think the above test programs only show a small sample of what GPC will erroneously accept as a type-inquiry-object. If I'm not completely misunderstanding the compiler source code in this area, it looks like the compiler will accept nearly all, if not all, legal expressions as a type-inquiry-object which is a whole lot more than what my test programs are showing as wrong (as well as, a whole lot more than what ISO requirements allow for a type-inquiry-object). The compiler I used was the latest version of Mac OS X GPC that Adriaan built and made available for downloading few weeks ago. The specs: Reading specs from /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple-darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 Thread model: posix gpc version 20051116, based on gcc-3.4.5 Gale Paeper gpaeper(a)empirenet.com

3 2

Network functions?
by Eike Lange 09 Jan '06

09 Jan '06

Hi Folks! Are there any network functions like socket, listen, accept and so on available for GPC? Eike

3 3

More identifier redeclaration error problems
by Gale Paeper 08 Jan '06

08 Jan '06

It looks like the "20050325: check identifier scopes stricter" bug fix didn't completely solve all the identifier redeclaration error problems involving an applied occurance of an outer scope identifier in an inner scope with a defining occurance of the identifier. The following two test programs will compile and run with the latest GPC version which shows that GPC still has a few problems with detecting redeclaration errors in scopes involving record type-denoter and formal-parameter-list regions. {$extended-pascal} program gale7 (output); type t = record case integer of 0: (boolean : boolean) {WRONG} otherwise (f : integer) end; begin writeln('FAIL'); end. {$extended-pascal} program gale8 (output); type t = integer; procedure foo(t: t); {WRONG} begin end; begin writeln('FAIL'); end. The compiler I used was the latest version of Mac OS X GPC that Adriaan built and made available for downloading few weeks ago. The specs: Reading specs from /Developer/Pascal/gpc345u2/lib/gcc/powerpc-apple-darwin8/3.4.5/specs Configured with: ../gcc-3.4.5/configure --enable-languages=pascal,c --enable-threads=posix --target=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --build=powerpc-apple-darwin8 --prefix=/Developer/Pascal/gpc345u2 Thread model: posix gpc version 20051116, based on gcc-3.4.5 Gale Paeper gpaeper(a)empirenet.com

1 0

C to Pascal translation
by Chris Hicks 07 Jan '06

07 Jan '06

There are a number of programs that do translation from C to Pascal: http://c2pas.sourceforge.net/ http://www.synaptics.com/people/daveg/ and from Pascal to C http://www.rocketaware.com/spec/softdev/lang/pascal/ I have not tried these out - just found them on Google. It might be worth giving them a try with some short bits of code. Best regards, Chris.

3 5

Translating C to Pascal
by Prof A Olowofoyeku (The African Chief) 07 Jan '06

07 Jan '06

Hi all I am trying to translate some gcc code to gpc, and I have become a tad blearly-eyed with this bit: " while(size--) crc =(crc << 8) ^ crctab[((crc >> 24) ^ *cp++) & 0xFF]; for(; length; length >>= 8) crc =(crc << 8) ^ crctab[((crc >> 24) ^ length) & 0xFF]; crc = ~crc & 0xFFFFFFFF; " Can anyone make any sense of this? Thanks. ps: I understand the shl and shr calls, and I think I have a good idea of what the rest is doing - but I would prefer not to guess (bette safe than sorry!). Thanks. Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/

1 0

Linking Pascal to Ada
by lanceboyle＠qwest.net 07 Jan '06

07 Jan '06

Sorry for the Ada content herein but I have to cross-bother *someone*. 8^) I'm trying to get a simple Ada program to access simple Pascal code-- see bottom of this post. (I also want to call Ada code from Pascal, but I haven't tried that yet.) I've read "6.11.2 Exporting GPC Libraries to Other Languages" from the GPC docs and "2.10.1 Interfacing to C" in the GNAT docs. I _think_ that I can prepare the Pascal code and call it from Ada assuming C calling conventions; at least, that's what I'm trying. The command lines that I am using, with the working directory the one containing all the source files, are: gpc -c mypascalunit.pas -o mypascalunit.o gnatmake adacallspascal.adb -largs mypascalunit.o /Developer/Pascal/ gpc344d2/lib/gcc/powerpc-apple-darwin8/3.4.4/libgpc.a (the gnatmake command is all one line) This causes the following output (sorry if there are any impolite line breaks): gcc -c adacallspascal.adb gnatbind -x adacallspascal.ali gnatlink mypascalunit.o /Developer/Pascal/gpc344d2/lib/gcc/powerpc- apple-darwin8/3.4.4/libgpc.a adacallspascal.ali ld: Undefined symbols: _frommypascalunit gnatlink: cannot call /usr/bin/gcc gnatmake: *** link failed. I'm linking libgpc.a because I think that is the GPC runtime library and prevents complaints about undefined symbols such as __p_Write_String. Question: Why doesn't the linker see _frommypascalunit??? Here are the two programs, Ada main and Pascal unit. with Ada.Text_IO; use Ada.Text_IO; procedure adacallspascal is procedure frommypascalunit; pragma Import(C, Frommypascalunit); begin Put_Line("Hello from adacallspascal."); frommypascalunit; end adacallspascal; unit mypascalunit; interface procedure frommypascalunit; implementation procedure frommypascalunit; begin writeln('Hello from frommypascalunit.'); end; end. Thanks for any comments at all. I've never tried anything like this. Jerry

2 1