Gpc January 1999

gpc@gnu.de

20 participants
34 discussions

re: varargs
by Russ Whitaker 22 Jan '99

22 Jan '99

hi Frank on 1/18 you wrote > ...the varargs functions are intended to be replaced sooner or later ok so how about changing some of the .c files to .cpp? Then you could use c++'s "function overloading" to replace the varargs The attached illustrative example compliles and runs as proto.cpp but proto.c gives 11 error messages thanks, Russ

1 0

Re: Build of GPC-19980830 (more questions...)
by Frank Heckenbach 18 Jan '99

18 Jan '99

Ken Linder wrote: > YES! It worked! I have successfully built the compiler! > I know, this may be a minor thing for some of you out there, but for me, > this is a large accomplishment! Congratulations! :-) For the first time, it can be a bit difficult. Once you've figured it out, you can automate it rather easily -- particularly on Linux... :-) > Since this don't work too well in a fcn prototype, I just coded the proto > as int; __va_ellipsis. Is this portable? I think it is on Intel based > hardware but otherwise no. I base this on the fact that there are many > #defines for va_dcl in the va-*.h files in the gcc-2.8.1/include dir. Why > can't there be something like va_dclp, generated in the varargs.h that will > allow protos to be portable? Maybe there is & I just missed it. > Definitely possible at this time of night! ;-) If you find something portable, let me know. Otherwise, it will not be *too* bad, since the varargs functions are intended to be replaced by non-varargs functions sooner or later... Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Re: Build of GPC-19980830 (more questions...)
by Frank Heckenbach 18 Jan '99

18 Jan '99

Ken Linder wrote: > Ok, I added the following code into the hdr.h file: > > ... > #include "varargs.h" > ... > extern void _p_write PROTO((FDR, int, int, __va_ellipsis)); > extern void _p_read PROTO((FDR, int, int, __va_ellipsis)); > extern int _p_string PROTO((int, __va_ellipsis)); > extern void _p_writestr PROTO((int, char *, int, __va_ellipsis)); > extern void _p_readstr PROTO(char *, int, int, int, __va_ellipsis)); > > Well, Peter, I think the above varargs will work fine with Intel Linux but > will probably do wierd things on other platforms. Hey, its my first shot > at it! :-) What I don't really understand is the additional `int' parameter before the ellipsis. Yes, I see that GCC wants it, but why? And is this portable? (Anyone knows for sure?) > The above fixed my immediate problems... but now when trying to compile > pascal code, I get problems linking to _p_strlen, _p_gpc_locase, and > _p_gpc_upcase. ARRGGHHH. I can't seem to find where these fcns are > defined in the RTS. (* They're defined in rts/gstrings.pas. Some other people had problems finding the definitions, too -- seems they're not used to things being implemented in Pascal actually. ;-) *) > I do see the protos though. Would anyone care to > shove me in the right direction to solve this? This is a known bug caused by inline functions being compiled without optimization. So there are two obvious solutions: remove the `inline' from these functions (the next GPC version will have this done), or compile with optimization, i.e. give `CFLAGS=-O2' to the make command line (the latter is, of course, preferable, since it produces a faster compiler, anyway). > Also, do I need to fix up the Makefile? I change hdr.h but when I do a > MAKE, nothing realy happens... :-# Yes, the Makefiles are quite broken in this regard. :-( Even worse if you should make substantial changes (esp. changing the size of some RTS data structure) in rts/types.h -- then you need to recompile some parts of the compiler, or you might get very strange behaviour, i.e. you better do a complete rebuild then... Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

3 2

Build of GPC-19980830 (more questions...)
by Ken Linder 17 Jan '99

17 Jan '99

Ok, I added the following code into the hdr.h file: ... #include "varargs.h" ... extern void _p_write PROTO((FDR, int, int, __va_ellipsis)); extern void _p_read PROTO((FDR, int, int, __va_ellipsis)); extern int _p_string PROTO((int, __va_ellipsis)); extern void _p_writestr PROTO((int, char *, int, __va_ellipsis)); extern void _p_readstr PROTO(char *, int, int, int, __va_ellipsis)); Well, Peter, I think the above varargs will work fine with Intel Linux but will probably do wierd things on other platforms. Hey, its my first shot at it! :-) The above fixed my immediate problems... but now when trying to compile pascal code, I get problems linking to _p_strlen, _p_gpc_locase, and _p_gpc_upcase. ARRGGHHH. I can't seem to find where these fcns are defined in the RTS. I do see the protos though. Would anyone care to shove me in the right direction to solve this? Also, do I need to fix up the Makefile? I change hdr.h but when I do a MAKE, nothing realy happens... :-# Later all, its bed time here in Vegas! Ken Linder KC7RAD

1 0

unsubscribe
by Chris Russell 15 Jan '99

15 Jan '99

unsubscribe

1 0

Self, and OO asm...
by Orlando Llanes 15 Jan '99

15 Jan '99

I was cleaning out my box and ran across my "Realization Of The Self..." post, just wanted to say nevermind :} I wrote that post because at the time I figured that since GPC objects are not compatible with DJGPP classes EDI might as well contain Self. I was porting my libs to DJGPP for the heck of it and found out that GPC and DJGPP are OO compatible to a certain point. All you have to do when writing an external assembly program for an object member is to declare a global for each version of the name. The following is an example of what I mean (not tested, writing it off the top of my head, tho it should work. If not let me know and I'll repost it after verifying): // begin test.cc #include <stdio.h> class tmyclass { public: int bar; int foo(); }; main() { tmyclass myclass; myclass.bar = 35; printf( "Should be equal %i %i\n", myclass.bar, myclass.foo() ); } // end test.cc { begin test.pas } program test; type tmyclass = object bar : Integer; function foo: Integer; end; var myclass : tmyclass; begin myclass.bar := 35; WriteLn( 'Should be equal ', myclass.bar, ' ', myclass.foo ); end; { end test.pas } # begin testo.s .globl _foo__8tmyclass # DJGPP name .globl _Tmyclass_Foo # GPC name .text _Tmyclass_Foo: _foo__8tmyclass: movl 4(%esp), %edi # Get Self pointer from the stack movl 4(%edi), %eax # Set function result to tmyclass.bar ret # end testo.s rem begin mktest.bat gpc test.pas testo.s -o testp.exe gcc test.cc testo.s -o testc.exe rem end mktest.bat Reason number 1,000,001 to use GPC =B) 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

remove
by c.wendt＠CHATEAU.line.org 15 Jan '99

15 Jan '99

remove please remove me from the mailing-list. thanks

1 0

Build of GPC-19980830
by Ken Linder (KC7RAD) 14 Jan '99

14 Jan '99

SUCCESS!! sort of... I managed to make gcc 2.8.1, do a make install, and then make gpc. To make things short, there are some fcn prototype declarations missing from the rtm.h file. Is there a newer rtm.h or should I just put the protos in myself? gpc works fine as long as I am not linking anything. ;-) Later and tnx for all the help! Ken Linder

2 1

Re: Using 'flock' in GNU Pascal.
by Frank Heckenbach 10 Jan '99

10 Jan '99

Chris Wood wrote: > I am in the process of developing a CGI program using GNU Pascal. The = > CGI program is to be used in a Linux environment. It is a database CGI = > script and I would like to have one running process of the CGI script = > have exclusive write access. I was hoping that someone could provide me = > with an example, or a place where I can find further (detailed) = > information, of using the flock() function from the C library in a GNU = > Pascal program. I also need to know how to detect when a file is = > locked. A million thanks for your time and help. The best way (WRT portability and security for future versions) is currently to write a small C wrapper. This is because "constants" (i.e., #defines) from a C header cannot be easily made available in Pascal. (I hope one day GPC will have a C header translator which would solve the problem more elegantly.) What you need to know from the Pascal side is that `GetFile' returns a C file (i.e., a `FILE *') for a Pascal file. The file handle (integer), which is needed by flock(), can then be obtained by the libc function fileno(). So, here's an example. First the C wrapper (fileno.c): #include <stdio.h> #include <sys/file.h> typedef unsigned char Boolean; int filelock (FILE*, Boolean, Boolean); int filelock (FILE* f, Boolean Exclusive, Boolean NoBlock) { return flock (fileno (f), (Exclusive ? LOCK_EX : LOCK_SH) | (NoBlock ? LOCK_NB : 0)); } int fileunlock (FILE*); int fileunlock (FILE* f) { return flock (fileno (f), LOCK_UN); } Now a test program: program FileLockDemo; uses GPC; {$L fileno.c} function FileLock (f : CFilePtr; Exclusive, NoBlock : Boolean) : Integer; C; function FileUnlock (f : CFilePtr) : Integer; C; var a, b : Text; begin Rewrite (a, 'foo.bar'); Reset (b, 'foo.bar'); { Non-exclusive locks, succeed } Writeln (FileLock (GetFile (a), False, True)); Writeln (FileLock (GetFile (b), False, True)); { Exclusive lock, fails } Writeln (FileLock (GetFile (a), True, True)); { Remove the non-exclusive locks, succeed } Writeln (FileUnLock (GetFile (a))); Writeln (FileUnLock (GetFile (b))); { Exclusive lock, succeeds } Writeln (FileLock (GetFile (a), True, True)); { Another exclusive lock, fails } Writeln (FileLock (GetFile (b), True, True)); { An exclusive lock *with* blocking, will block the program forever! } Writeln (FileLock (GetFile (b), True, False)); end. As the example shows, you can find out if a file is locked, by trying to lock it without blocking (and removing the lock again if not needed). I don't know if there's another way to check... Frank -- Frank Heckenbach, frank(a)fjf.gnu.de http://fjf.gnu.de/ PGP and GPG keys: http://fjf.gnu.de/plan

1 0

Using 'flock' in GNU Pascal.
by Chris Wood 10 Jan '99

10 Jan '99

I am in the process of developing a CGI program using GNU Pascal. The CGI program is to be used in a Linux environment. It is a database CGI script and I would like to have one running process of the CGI script have exclusive write access. I was hoping that someone could provide me with an example, or a place where I can find further (detailed) information, of using the flock() function from the C library in a GNU Pascal program. I also need to know how to detect when a file is locked. A million thanks for your time and help. Sincerely, Chris Wood

1 0

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 January 1999