Gpc December 1997

gpc@gnu.de

24 participants
76 discussions

Re: Sockets
by Peter Gerwinski 02 Dec '97

02 Dec '97

According to Matthew Wiggins: > this sort of helps, except in both of the replys I have gotten > you have mentioned ShortCard, what in god's name is that? yes, > okay but this does help alot, if I find out what shortcard is. (This was in one long line which made it hard to read; better break it up. It is also better to continue this discussion on the GPC mailing list because there might be others who have the same problem and are interested in the solution. Thanks.) `ShortCard' is a built-in integer type in recent beta versions of GPC. It is compatible to C's `unsigned short' and usually has 16 bits. To get the same in gpc-2.0, use Type Cardinal = __unsigned__ Integer; ShortCard = __short__ Cardinal; or Type ShortInt = __short__ Integer; ShortCard = __unsigned__ ShortInt; Other C-compatible modifiers are `__byte__', `__long__' and `__longlong__'. For other built-in integer types in GPC betas, see the online documentation, `info -f gpc -n "Integer types"'. 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/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: ODP: Interfacing DJGPP C with Pascal
by Peter Gerwinski 02 Dec '97

02 Dec '97

According to Stanislaw Kozlowski: > > Yes, this is all that I needed. Maybe this informationit should be included > in INFO help ? Yes, that would be good. In fact I am already working on such things, but it costs time ... :-( > In fact inspecting binary code of LIBPC.A I figured out > that _p_initialize should be called but I did no know the parameters. Why didn't you inspect the *source* code of `libgpc.a'? It is available from the same place where you got the binaries. Greetings, Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

subscribe
by Marco Klein 02 Dec '97

02 Dec '97

1 0

Re: File/Record locking on Linux with GPC
by Peter Gerwinski 01 Dec '97

01 Dec '97

According to Pismo: > I need to lock records or at least files on database > written with GPC on Linux system ... how? What do you mean by "locking records"? How would you do this manually or with another programming language? Peter Dipl.-Phys. Peter Gerwinski, Essen, Germany, free physicist and programmer peter.gerwinski(a)uni-essen.de - http://home.pages.de/~peter.gerwinski/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

2 1

Re: Sockets
by Peter Gerwinski 01 Dec '97

01 Dec '97

Hello, Matthew! Hi, everybody! According to RHS Linux User: > I was trying to open a socket, but the problem I kept running into was > that connect wants a sockaddr struct, and in C you just casted it... > (struct sockaddr *)&address but, I don't think that that is possible in > pascal, [...] Since you cannot simply #include a C header file in a Pascal program you have to define the type by yourself: Const AF_UNSPEC = 0; AF_UNIX = 1; (* Unix domain sockets *) AF_INET = 2; (* Internet IP Protocol *) AF_AX25 = 3; (* Amateur Radio AX.25 *) AF_IPX = 4; (* Novell IPX *) AF_APPLETALK = 5; (* Appletalk DDP *) AF_NETROM = 6; (* Amateur radio NetROM *) AF_BRIDGE = 7; (* Multiprotocol bridge *) AF_AAL5 = 8; (* Reserved for Werner's ATM *) AF_X25 = 9; (* Reserved for X.25 project *) (*$ifdef LINUX_2_1_X *) AF_INET6 = 10; (* IP version 6 *) (*$endif *) AF_MAX = 12; (* For now.. *) Type SockAddrPtr = ^SockAddr; SockAddr = record case family: ShortCard of AF_UNSPEC: ( data: packed array [ 0..13 ] of Char ); AF_INET: ( port: ShortWord; address: array [ 1..4 ] of Byte ); end (* SockAddr *); Having this you can declare a variable `Address' of type `SockAddr', so `@Address' will have the correct type - no need to cast. However, `SockAddrPtr ( @Address )' is the exact analogon of your C fragment above. 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/ [971005] maintainer GNU Pascal [971001] - http://home.pages.de/~gnu-pascal/ [971005]

1 0

Re: Sockets
by Kevin A. Foss 01 Dec '97

01 Dec '97

On Thu, 27 Nov 1997 11:15:44 -0800 (PST), RHS Linux User wrote: Hello, >I was trying to open a socket, but the problem I kept running into was >that connect wants a sockaddr struct, and in C you just casted it... >(struct sockaddr *)&address but, I don't think that that is possible in >pascal, so if anyone has successfully done this or knows how. please email >me, Well, I've done some work interfacing GPC with sockets, and the problem you describe is the first one I hit. The only solution I've found so far for problems like these is to wrap them inside callable C routines. E.g. I have something like: int bind_socket(int orig_sock, short family, u_short port) { struct sockaddr_in serv_adr; memset( &serv_adr, 0, sizeof(serv_adr) ); serv_adr.sin_family = family; serv_adr.sin_addr.s_addr = htonl(INADDR_ANY); serv_adr.sin_port = htons(port); if (bind( orig_sock, (struct sockaddr *) & serv_adr, sizeof(serv_adr)) < 0) { close(orig_sock); return (-1); } return (0); } in socket.c (with all of the necessary includes) Then in my Pascal source I use: function bind_socket(socket : integer; family : ShortInt; port : ShortCard) : integer; C; and I can bind a socket with a call like: result := bind_socket(socket, AF_INET, port); The at compile time I just include my C file with the source: gcc sockettest.pas socket.c -lsocket or whatever... As I explore more of the features in GPC hopefully I'll be able to make more calls directly from Pascal, but for calls like bind(), accept() and connect() I've found it easier to write a wrapper in C. Obviously it would take a while to write good wrappers that would return full error conditions to GPC not to mention allowing users to get at all of the socket options you have in C, but I've been just kludging solutions that happen to fit my needs. Right now all I have working is a quick-and-dirty connection where a client can send strings to a server process on another machine and have it echoed back slightly modified. -Kevin -- Kevin A. Foss --- kfoss(a)mint.net --

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 December 1997