Gpc

gpc@gnu.de

5400 discussions

function pointers - whats wrong ???
by Sven＠rufus.central.de 06 Feb '97

06 Feb '97

hello gpc users, I tryed to use the famous function pointers, but I can't compile this stuff. I tryed the example from info files - the same sh... Look: program zap(output); type proc_ptr = ^ procedure (integer); var pvar : proc_ptr; procedure write_int(i: integer); begin writeln ('Integer: ',i:1); end; begin (* PVAR points to function WRITE_IT *) pvar := &write_int; (* Dereferencing a function pointer calls the function *) pvar^(12345); end. Output from gpc: fupotest.pas(16) Error: to few arguments to function `Write_int' fupotest.pas(16) Error: invalid lvalue in unary `&' Now it's your turn ... what's wrong? Further questions: How I can put the stderr output in a file? I'm using DJGPP. It's possible to speed up the standard compilation of gpc for my pentium? What's the floating point type of gpc's complex numbers? Anybody is using my graph unit "BGI2GRX"? I'm working on a direct GRX20-Unit (contexts, mouse, ...) but I don't know if it's needed by anybody else me. ___, ((__ o ,____)) V E N I

1 0

GPC module restrictions etc
by Jakob Heinemann 06 Feb '97

06 Feb '97

Hello! I'm looking at GPC to decide wether or not to use it to port a quit large application from VMS to Unix. The original source is written in Vax-pascal, not by me, some ten years ago. It consists of lots of compiler dependent features such as Vax-pascal 'environment' and 'inherit'-statemets that should relatively easy translate to module exports and imports of GPC, but also of. constructs that are, perhaps not that easy to translate. Currently wehave installed the 2.0 version of GPC on our Sun Solaris 5.5 machine. The size of the system, about 175 modules, som 70 klines of code, implies that the translation have to rely on safe module-import/export functionality. According to the documentation the GPI-mechanism is not as stable as it should be. but what is the actual problem? what are the limitations? the problem of unsized strings and GPI import? (I get a warning that there are incompatible pointers when calling an imported function with a varying string.) is there som work beeing done to fix it? Other questions that I also came up with are: Calling functions in C, is easy, just put a C; as a declaration af the body. How about calling functions in ADA (i.e. Gnat)? The other way around, other languages calling functions written in Pascal? The code uses lots of varying length strings written partly as schemas, and partly as some sort of conformant arrays in parameter lists. A piece fo code may look like this: Var text_str : varying (. len .) of char ; procedure testproc ( str : varying (.len .) of char ); var i : integer ; begin for i := 1 to len do something(i,str); end ; This should translate to Var text_str : string; procedure testproc ( str : string ); var i : integer ; begin for i := 1 to length(str) do something(i,str); end ; But how about the vax statement for issuing variable amount of arguments? Vax-pascal: procedure test_pro ( var arg1 : integer; [list] therest : integer) ; var cnt : integer ; begin arg1:= 0 ; for cnt := 1 to argument_list_length (therest) do arg1 := arg1 + argument(therest, cnt): end; Is there a construct for this in GPC? (in that case I�m sorry but I haven�t found it in the manual) I don�t think I'm on the subscriberlist so please post your reply directly to me aswell. (I've tried to subscribe , but I'havent hear anything...) Thank you guys, Gnu Pascal's great, but I still miss some important consepts from the extended pascal definition. (Schemas and module integrity...) Hope that all the stuff will be there some day, right now I feel it is not so safe that it will suit our need for this project, but perhaps in the future.. Bye! -- /Jakob :) mailto:Jakob.Heinemann@lmemw.ericsson.se Ericsson Saab Avionics Link�ping, Sweden

1 0

Re: Gpc <unresolved symbol Assign>
by Peter Gerwinski 03 Feb '97

03 Feb '97

> I have no problems compiling and running under Borland, but I do not have > dos based machines at my disposal and would like to compile under either > gpc or xlp. Xlp? Is that something we should know about? > Is there some library i need to tell it to link? GNU Pascal has no built-in Assign procedure. You can use the "BPCompat" Unit from the "contrib" subdirectory of the GPC source distribution (same as the "System" Unit from the new BPCompat package). Alternatively you can write it yourself using Extended Pascal's "bind" mechanism: Type WrkString = String ( 255 ); Procedure Assign ( Var T: Text; Name: WrkString ); Var B: BindingType; begin (* Assign *) unbind ( T ); B:= binding ( T ); B.Name:= Name; bind ( T, B ); B:= binding ( T ); end (* Assign *); Hope this helps, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [970201] maintainer GNU Pascal - http://home.pages.de/~gnu-pascal/ [970125]

1 0

Gpc <unresolved symbol Assign>
by Jim Herbert 03 Feb '97

03 Feb '97

Hi, I am having trouble resolving the symbol Assign in my pascal programs. I have no problems compiling and running under Borland, but I do not have dos based machines at my disposal and would like to compile under either gpc or xlp. Is there some library i need to tell it to link? If anyone have an answer for me, would you please reply via e-mail, since I am not a subscriber of this group. Thanks, -Jim

1 0

Re: need GPC Developers?
by Peter Gerwinski 31 Jan '97

31 Jan '97

According to Ronald Perrella: > I'd like to see if there is anything I can do to help > with GNU Pascal development. Is there a wish-list of > things people want? > You may want to put such a list on the Web Home page. > (if it was there, I could not find it...) There is such a wish-list in the documentation, section "How you can contribute to GNU Pascal". But you are right that it should get a more prominent place on the WWW site. Just to mention a few current problems: * Improve the documentation. I am, for example, not too content with the current order of things. It should start with something like "Introduction to GNU Pascal", then "How to compile a program", etc. * Write more example programs. * Make the "Borland compatibility package" portable. I implemented it for DJGPP, but it would be nice to have it at least for Linux, too. Also, the DOS Unit is still missing ... * Fix the bugs. (Section "Known bugs and inconveniences ..." of the documentation lists most of the bugs.) * Implement the missing parts of ISO Standard Pascal, Level 1, and of ISO Extended Pascal - or at least point out what is missing because I actually do not know and I do not find it really instructive to read the Standard Specifications. * Implement the missing parts of Borland Pascal. Implement Delphi and Pascal-SC. You see that we are in the lucky position that there are enough of open problems that you can choose that one you like best to see been solved. ;-) I suggest just to try to write some useful programs with GNU Pascal (some of which we can publish as example programs), then you will run into some bugs and inconvenicences in the compiler and/or documentation. Once you know what you think to be the most annoying problem, try to fix it - and do not forget to contact us in case you succeed or have any questions. Thanks a lot for your offer! Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Re: gpc linking problem
by Peter Gerwinski 31 Jan '97

31 Jan '97

According to Nils Bokermann: > According to Krzysztof Kwapien: > > But when i tried to compile it with > > gpc -c hello.pas <- this worked > > gpc -o hello hello.o <- this crashed with a SIGSEGV ..... > > it crashed when linking. > > Is it a ld-Problem? I've just tried it, but it works very well. I also suspect a ld-related problem here. Try to upgrade your "binutils". Ld version 2.7 is known to work with gpc 2.0. In case this does not solve the problem, please post some information about your system here, like Nils did: > Here is my system-info: > reality:~/pascal$ gpc -v > Reading specs from /usr/lib/gcc-lib/i486-unknown-linux/2.7.2.1.f.1/specs > gpc version 2.0(2.7.2.1.f.1) > reality:~/pascal$ ld -v > ld version 2.7 (with BFD 2.7.0.3) Good luck, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

need GPC Developers?
by Ronald Perrella 30 Jan '97

30 Jan '97

Hi, I'd like to see if there is anything I can do to help with GNU Pascal development. Is there a wish-list of things people want? You may want to put such a list on the Web Home page. (if it was there, I could not find it...) -- Ronald Perrella perrella(a)mindspring.com Roswell, Georgia, USA.

1 0

Re: Again: g77 and gpc ...
by Peter Gerwinski 28 Jan '97

28 Jan '97

> [...] I just want to install ready-to-go gpc over my > gcc/g77 setup under emx09c. I noticed that that would replace gcc.a > from the original emx09c/gcc distribution. > Are there any negative experiences with that, or is it safe to do so? It should be save because gcc.a in the gpc distribution is (or: should be) the same as gcc.a in the gcc-2.7.2.1 distribution. I recommend you to try to run gpc with gcc.a from your gcc/g77 setup first. (I do not need to mention that you should backup your gcc.a first before replacing it with gpc's one, do I? ;-) Good luck, and let us know about your experience! Yours, Peter e-mail: peter.gerwinski(a)uni-essen.de home address: D\"usseldorfer Str. 35, 45145 Essen, Germany WWW: http://agnes.dida.physik.uni-essen.de/~peter/

1 0

Again: g77 and gpc ...
by Stefan A. Deutscher 26 Jan '97

26 Jan '97

Hi, I noticed that there were some problems reported building gpc on a system that had the g77 patched gcc already. I just want to install ready-to-go gpc over my gcc/g77 setup under emx09c. I noticed that that would replace gcc.a from the original emx09c/gcc distribution. Are there any negative experiences with that, or is it safe to do so? Cheers. Stefan ============================================================================ Stefan A. Deutscher | (+1-423-) voice fax The University of Tennessee, Knoxville | UTK : 974-7838 974-7843 Department of Physics and Astronomy | ORNL : 574-5897 574-1118 401, A. H. Nielsen Building | home : 522-7845 522-7845 Knoxville, T.N. 37996-1200, USA | email: sad(a)utk.edu ============================================================================ Dictated with OS/2 Warp 4 VoiceType dictation.

1 0

Building GNU Pascal together with GNU Fortran.
by Niels Kristian Bech Jensen 26 Jan '97

26 Jan '97

Hi, Here is a small patch, which makes it possible to build GPC 2.0 using a GCC 2.7.2.1, that has been build with Fortran support (tested with G77 0.5.19). This could be useful for people, who (like me) needs to have both languages at hand. It changes the GCC version to 2.7.2.1.f.1 and adds the changes made for G77 to toplev.c: diff -rcp2N gpc-2.0/Makefile.in gpc-2.0.f.1/Makefile.in *** gpc-2.0/Makefile.in Mon Nov 18 03:31:33 1996 --- gpc-2.0.f.1/Makefile.in Sun Jan 26 17:32:05 1997 *************** *** 40,44 **** # GPCVERSION = `date +%y%m%d` GPCVERSION = 2.0 ! GCCVERSION = 2.7.2.1 CROSS = @cross@ --- 40,44 ---- # GPCVERSION = `date +%y%m%d` GPCVERSION = 2.0 ! GCCVERSION = 2.7.2.1.f.1 CROSS = @cross@ diff -rcp2N gpc-2.0/toplev.c gpc-2.0.f.1/toplev.c *** gpc-2.0/toplev.c Sat Sep 21 17:50:52 1996 --- gpc-2.0.f.1/toplev.c Sun Jan 26 17:30:28 1997 *************** int flag_unroll_loops; *** 392,395 **** --- 392,409 ---- int flag_unroll_all_loops; + /* Nonzero forces all invariant computations in loops to be moved + outside the loop. */ + + int flag_move_all_movables = 0; + + /* Nonzero forces all general induction variables in loops to be + strength reduced. */ + + int flag_reduce_all_givs = 0; + + /* Nonzero gets another run of loop_optimize performed. */ + + int flag_rerun_loop_opt = 0; + /* Nonzero for -fwritable-strings: store string constants in data segment and don't uniquize them. */ *************** struct { char *string; int *variable; in *** 553,556 **** --- 567,573 ---- {"unroll-loops", &flag_unroll_loops, 1}, {"unroll-all-loops", &flag_unroll_all_loops, 1}, + {"move-all-movables", &flag_move_all_movables, 1}, + {"reduce-all-givs", &flag_reduce_all_givs, 1}, + {"rerun-loop-opt", &flag_rerun_loop_opt, 1}, {"writable-strings", &flag_writable_strings, 1}, {"peephole", &flag_no_peephole, 0}, *************** rest_of_compilation (decl) *** 2965,2968 **** --- 2982,2987 ---- { loop_optimize (insns, loop_dump_file); + if (flag_rerun_loop_opt) + loop_optimize (insns, loop_dump_file); }); } -------------------------------------------------------- Niels Kristian Bech Jensen nkbj(a)image.dk "Chemists never die --- they just run out of reactants!"

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