HP3000-L Archives

May 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jerry Finn <[log in to unmask]>
Reply To:
Jerry Finn <[log in to unmask]>
Date:
Sun, 5 May 2002 16:21:31 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
> Date:    Sat, 4 May 2002 17:41:10 +0200
> From:    Lars Appel <[log in to unmask]>
> Subject: Re: Cobol and Sockets
>
> Peter,
>
> >Now, correct me if I am wrong but NetIPC is a HP 3000 proprietary interface
> >and Berkeley Sockets is the open interface that is available on every OS you
> >can imagine.
>
> I don't think I'd want to disagree here. However, keep in mind that the
> parameter passing in Berkeley Sockets is very much "C biased" and without
> being able to use the C header files, it will probably not be convenient
> to use from COBOL, Pascal or similar languages.
>
> So you might find it more useful to write your core socket routines in C
> and design the parameter passing in such a way that they can be called from
> COBOL as well.

I remember seeing an article in Interex around 1992, How to right
Berkley sockets in COBOL. Had examples and a pretty much end to end
How-to. It stuck in my mind because the first thing I thought was
Why would you want to do that in COBOL and not C.

I don't know if there is any way to find something that far back.

Jerry Finn
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2