[Python-Dev] Re: OS/2 EMX changes to dynload_shlib.c (original) (raw)
Andrew MacIntyre andymac@bullseye.apana.org.au
Wed, 27 Feb 2002 08:06:47 +1100 (EDT)
- Previous message: [Python-Dev] =?koi8-r?B?8NLP3tTJ1MUsIM3P1sXULCDc1M8g98HbINvBztMuIPXEwczJ1NggzsXJy8/H?= =?koi8-r?B?xMEgzsUg0M/axM7PLg==?=
- Next message: [Python-Dev] Re: OS/2 EMX changes to dynload_shlib.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 26 Feb 2002, Guido Van Rossum wrote:
[I sent this to python-dev, but my copy to you bounced; I'm not sure if you're on python-dev yet.]
Have been for some time.
Given the number of OS/2 EMX specific changes to dynloadshlib.c, wouldn't it be better to create a separate dynloados2.c?
There is already a dynload_os2.c for the VACPP port, which implements a module loader via direct OS/2 API calls.
Because the EMX stuff that I picked up (a 1.5.2 port by Andrew Zobolotny) used an emulation of dlopen() (PC/os2emx/dlfcn.c) I carried that over.
I hadn't considered the changes to dynload_shlib.c that significant. however I'll look into whether I can adapt the EMX port to use the VACPP module loader in dynload_os2.c.
-- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andymac@bullseye.apana.org.au | Snail: PO Box 370 andymac@pcug.org.au | Belconnen ACT 2616 Web: http://www.andymac.org/ | Australia
- Previous message: [Python-Dev] =?koi8-r?B?8NLP3tTJ1MUsIM3P1sXULCDc1M8g98HbINvBztMuIPXEwczJ1NggzsXJy8/H?= =?koi8-r?B?xMEgzsUg0M/axM7PLg==?=
- Next message: [Python-Dev] Re: OS/2 EMX changes to dynload_shlib.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]