Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3CEAC1D9.BAEA250F@phekda.freeserve.co.uk>
Date: Tue, 21 May 2002 22:53:29 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP newsgroup <djgpp AT delorie DOT com>
Subject: Re: ANNOUNCEMENT: Python 2.2.1 for DOS test release
References: <3ce7fc1f$0$26970$9b622d9e AT news DOT freenet DOT de> <3CE810BA DOT FCA8CEDF AT phekda DOT freeserve DOT co DOT uk> <3ce8232a$0$26959$9b622d9e AT news DOT freenet DOT de> <3CE93EB2 DOT 2DD59789 AT phekda DOT freeserve DOT co DOT uk> <3ce97174$0$23709$9b622d9e AT news DOT freenet DOT de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

deckerben wrote:
[snip]
> I'm really happy for any advice that is given to me in a positive manor. I
> will try to make up a diff package and send it to you.

I won't really be able to comment on how you've ported it, unless I can see
the diffs. I'm not sure I know enough Python, to test out the port. ;)

[snip]
> > The problem with socket libraries is that they only work on a subset of
> > the platforms that DJGPP runs on. That really is pretty inconvenient for
> > the user.
> > Until there's one library for all platforms, I'm not sure it's worth
> > trying to add Socketmodule.
> 
> Then, I guess what is needed is a C library (please, NOT TSR) that can
> detect a Win95/NT winsock-tcpip connection _if_it_exists.

Yes. That's the problem. Incidentally there is a driver for Windows NT (and
maybe it works with 2k, XP) that tries to emulate the Windows '95 interface
that libsocket uses. It could do with some more testing & work:

    http://www.phekda.freeserve.co.uk/gabor/wsockvdd/

Unfortunately it did not work very well last time I tried it.

> Otherwise, it tries its own connection via comm port. It needs to have all
> the Libsocket definitions, though, so that porting UNIX stuff is made easy.
> Just my thinking.

When you say "tries its own connection via comm port", do you mean that the
program should make a connection via modem and run all the networking
protocols itself? That's quite a task. Also it would not work very well on a
LAN.

Bye,

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]