Gpc

gpc@gnu.de

5400 discussions

C Arrays
by Thamm, Russell 08 Sep '98

08 Sep '98

There seems to be subtle inconsistancies with accessing 'C' Arrays from PASCAL. I am concerned that array variables need to be treated differently than array parameters. Basically, variables need to be declared as arrays and parameters need to be declared as pointers to arrays. I would have thought that if I declared a 'C' array variable to be a pointer, and a function parameter to be a pointer, that when I pass the variable to the function, PASCAL should pass a pointer. However, this is not the case for 'C' array variables. The following code fragments demonstrate this: <<TEST.C>> int carray[5] = {0x01010101,0x02020202,0x03030303,0x04040404,0x05050505}; int c1array[5] = {0x01010101,0x02020202,0x03030303,0x04040404,0x05050505}; void print_array(int *arr) { int i; for (i=0; i < 5; i++) printf("%8X\n",arr[i]); } <<ARRTEST.PAS>> program ArrTest; {$L test.c} type CCARRAY = array[0..4] of Integer; CCARRAY_PTR = ^CCARRAY; var carray : __asmname__ 'carray' CCARRAY_PTR; c1array : __asmname__ 'c1array' CCARRAY; pas_arr : CCARRAY value ($01010101,$02020202,$03030303,$04040404,$05050505); p : CCARRAY_PTR; procedure print_array(arr : CCARRAY_PTR); AsmName 'print_array'; begin p := &pas_arr; WRITELN('c array'); print_array(&carray); {this & seems wrong} WRITELN('c1 array'); print_array(&c1array); WRITELN('pascal array'); print_array(p); WRITELN('pascal array'); print_array(&pas_arr); end. PASCAL treats 'C' arrays the same, irrespective of whether they are declared as a plain array or as a pointer to an array. The & operator is required to pass 'C' arrays to 'C' subroutines. Alternatively, in my PASCAL declarations of 'C' functions, I could declare all 'C' array parameters to be VAR parameters. But this just doesn't seem right. On another matter, I downloaded the latest binary of GPC (gpc-19980830.i386-djgppv201.zip). Now, I keep getting a linker error about crt0.o. How do I overcome this? thanks Russell

4 4

kampi must be down
by Marcelo Pereira Nunes 08 Sep '98

08 Sep '98

Hey guys, I tried to connect ftp://kampi.hut.fi/jtv/gnu-pascal/ from Brazil and my Netscape said that it shoud be down. Does anybody know what happend? Could you tell me any mirror site for download? Thanks, Marcelo.

2 1

'-lgpc: not found' and '-lgpc: not found'
by Ricardo Luis Kulzer 04 Sep '98

04 Sep '98

I got the binary code of gpc (ftp://ftp.unicamp.br/pub/gnu/gpc-2.0.sparc-sun-solaris2.5.1.tar.gz), and put it on my system (Sparc workstation running Solaris 2.5.1) When I try to compile a pascal program, I receive the message: gpc -o tmp tmp.pas ld: fatal: library -lgpc: not found ld: fatal: library -lgcc: not found ld: fatal: library -lgcc: not found ld: fatal: File processing errors. No output written to t What is wrong? Ricardo Kulzer rkulzer(a)lacesm.ufsm.br CRSPE-INPE/UFSM

2 1

GPC Beta release: gpc-19980830
by Peter Gerwinski 04 Sep '98

04 Sep '98

Hello everybody! A new Beta version of GNU Pascal is now available: gpc-19980830. News ==== Apart from many bug fixes, we have significantly improved GPC's compatibility to Borland Pascal. Things like Extended Pascal's schema types are now more stable, and many functions such as conversion functions between Pascal and C strings are now built in. In particular: - A unit `gpc.pas' is now included which contains declarations of almost all the routines in the run time system. Many of them, including all that are required by the standard, are available without using this unit, but some new extensions, in particular most of the new string, CString and file name routines listed below, are only available when this unit is used. (It is planned to let GPC automatically use this unit in a later version, and then more declarations will go there that are currently built into the compiler.) - BP compatible runtime I/O error handling that is enabled/disabled by the compiler options {$I-} and {$I+}. In "disabled" mode, I/O errors don't cause runtime errors, but can be checked for by the program with the `IOResult' function. - Error messsages of the run time system are now output in the form: "a.out: [internal error:] unknown code in `Write' (#904)" which is closer to the GNU coding standards than the previous format was. - A symbol `__GPC_RELEASE__' is predefined, containing the release date of the GPC version in the format YYYYMMDD. This can be used in units that require certain features of the compiler to make sure they are now compiled with a too old compiler. Such a test might look like the following: {$if __GPC_RELEASE__ < 19980830} {$error This unit requires GPC release 19980830 or newer} {$endif} - New/GetMem/Dispose/FreeMem can now be mixed freely with malloc()/free(), to ease interfacing GPC code to C routines, and with Mark/Release. (The only thing that does not work is free()ing a New/GetMem'ed block between a Mark and the corresponsing Release, something which is not likely to happen unintentionally.) - New compiler options: --autolink (link units as used, but don't recompile them) When several --automake="foo", --autobuild="bar" and --autolink="baz" options are given, the "highest" one is valid, and the options of all of them are collected. --no-automake, --no-autobuild, --no-autolink (each of them disables all of --autolink, --automake and --autobuild) --gnu-pascal (disables any previously selected dialect options) --uses="foo" (automatically use a unit) --longest{int,real}-field-width (specify the field width in Write[ln] of long integer and real types) - String routines: UpCase (B) LoCase UpCaseString LoCaseString UpCaseStr LoCaseStr - CString routines: StrLen (B) StrEnd (B) StrScan (B) StrRScan (B) StrDup StrCmp StrCaseCmp StrPCopy (B) NewCString CString2String String2CString - File and I/O routines and declarations: IOResult (B) InOutRes (B) Erase (B) Rename (B) ChDir (B) MkDir (B) RmDir (B) FileMode (B) Flush (B) FilePos (B) FileSize (B) Truncate (B) Append (B) GPC_StatFS - File name routines and declarations: PathSeparator DirSeparator DirSeparators ExtSeparator DirSelf DirParent NullDevice TTYDevice ConsoleDevice GetCurrentDirectory GetTempDirectory GetTempFileName GetTempFileName_CString Slash2OSDirSeparator OSDirSeparator2Slash Slash2OSDirSeparator_CString OSDirSeparator2Slash_CString FileExists DirectoryExists FSearch (B) FSearch_Executable Expand_Environment FExpand (B) FSplit (B) DirFromPath NameFromPath ExtFromPath OpenDir ReadDir CloseDir - Other routines and declarations: ExitCode (B) ErrorAddr (B) RunError (B) SizeType PtrDiffType High (B) Low (B) Random (B) Randomize (B) Pi (B) DayOfWeek new fields DayOfWeek, MicroSecond in the TimeStamp record Items marked "(B)" are BP compatible routines/declarations. For a more detailed list of fixed bugs and new features, see the GPC TODO list, available online at http://fjf.gnu.de/gpc-todo_toc.html or as Texinfo source at http://fjf.gnu.de/gpc-todo.texi.gz . This version of GPC has been tested with and is expected to work on Linux on the Pentium and the Alpha platform, but there are known problems with packed arrays and "long" data types on 64-bit machines like the Alpha. The GNU Pascal development team welcomes the new members Nick Burrett and Matthias Klose. Where to get it =============== The source is available from ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/gpc-19980830.tar.gz . Binaries for DOS (DJGPP), and Linux (ELF) will follow as soon as possible and will be announced separately. Acknowledgement =============== I still have lost overview, but the GNU Pascal development team thanks everybody who helped us by contributing useful ideas and reporting bugs. Thanks to all of you! Greetings, The GNU Pascal Development Team Peter, Frank, Matthias, Jan-Jaap, and Nick -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 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: GPC Beta release: gpc-19980830
by Peter Gerwinski 04 Sep '98

04 Sep '98

Miklos Cserzo wrote: > > This time it is OK. How can I test it without actually installing it? (The > naiv way from p/test/: "make" failed.) make PC="../../xgpc -B../../" Greetings, Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 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/

1 0

Documentation
by Paul Doerwald 04 Sep '98

04 Sep '98

Since it is widely grokked that community efforts (especially in the software industry) work better than individual efforts, Peter and I have been discussing how we can, as a community, best work on the GPC documentation. Here is an idea that we came up with: Rather than a web-based form like I suggested, we propose an e-mail based system. With a simple syntax, you can request a portion of the GPC reference documentation, and it will be e-mailed back to you. You can reply, quote the text, and edit what you like, and when you send it back, your changes will be automatically added to the official GPC (texinfo) documentation, and will also be kept online in an HTML format so that everyone has immediate access to your contribution. This way we can all contribute to the GPC documentation effectively. Any thoughts? | clavicle(a)niagara.com "The LORD is my strength and my | www.niagara.com/~clavicle song; he has become my salvation." | ICQ#13902938 Exodus 15:2b

2 1

gpc-19980830 binaries for Linux
by Peter Gerwinski 02 Sep '98

02 Sep '98

Hi, folks! Two binary distributions of gpc-19980830 for i586-pc-linux-gnulibc1, one based on gcc-2.8.1 and one on egcs-2.91.55, are being uploaded to ftp://agnes.dida.physik.uni-essen.de/gnu-pascal/beta/binary/ . Greetings, Peter -- Peter Gerwinski, Essen, Germany, http://home.pages.de/~Peter.Gerwinski/ Maintainer GNU Pascal - http://home.pages.de/~GNU-Pascal/ - gpc-980830 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 1

Allegro and ASM
by Thamm, Russell 01 Sep '98

01 Sep '98

Hi, I've been trying to convert allegro.h into a Pascal unit. Has anyone already done this? One of the problems I'm having is translating the asm statements from C to PASCAL. I keep getting the compiler error: allegro.pas(1204) Error: cannot reload integer constant operand in `asm'. I have absolutely no idea what this means. The offending code is as follows: asm ('call *%3' : '=a' (result) { result in eax } : 'd' (bmp), { bitmap in edx } '0' (line), { line number in eax } 'r' (bmp^.write_bank) { the bank switch routine } ); All I've done is changed all double quotes to single quotes and changed -> to ^. Could you please cc any replies to me as I am not subscribed to this mailing list despite several requests. thanks russell

3 2

GPC version question...
by Orlando Llanes 26 Aug '98

26 Aug '98

What's the name of the most recent patch (ok, I'm feeling a bit adventurous here now :P) or binary for GPC? I downloaded the 98-05-11 release (installed *after* DJGPP 2.8.1 and all its tools were installed), is that the most recent one? If so, I can't figure out why I get the "unit information deterioration" bug. Could installing GPC over DJGPP be the reason? Should I leave GPC in its own directory? 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

2 2

Re: RunError
by Frank Heckenbach 22 Aug '98

22 Aug '98

Orlando Llanes wrote: > Is it possible to hook the RunError in GPC? I would definitely be > interested in a feature like that so that custom handlers can be used. If you mean the RunError procedure, yes (just write your own RunError procedure :-). If you mean the runtime error handling in general, no, not yet (except by modifying the RTS itself). For the time after GPC 2.1, I'm planning some form of exception handling like Delphi or Java which would make this possible. > Awesome 8o~~~ (<--- Drooling with goofy eyes) I think the C workaround > was not a good work-around anyway, I got weird results using them, for a > text file (for example) it worked fine, but (also for example) the pcx > encoder didn't properly encode a file despite using a proven algorithm. I didn't look to closely at the code, so I don't know if there were any problems with it. Another possible problem, if e.g. the code was tested with TP, is the different sizes of data types in GPC, buf I suppose you've thought of that... > I'm trying to eliminate > warnings wherever possible without requiring special command-lines :) Yes, me too. Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Jump to page:

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