[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: msvc-inval: more options
From: |
Bastien ROUCARIES |
Subject: |
Re: msvc-inval: more options |
Date: |
Mon, 26 Sep 2011 10:37:45 +0200 |
On Mon, Sep 26, 2011 at 9:01 AM, Paolo Bonzini <address@hidden> wrote:
> On 09/25/2011 11:46 PM, Bastien ROUCARIES wrote:
>>
>> Did you seehttp://bugs.python.org/issue4804 ?
>>
>> Particularlyhttp://bugs.python.org/file12953/__pioinfo.patch
>>
>> A little bit hackhish but seems to work
>
> That would provide a lot more flexibility, including:
>
> * the ability to implement O_INHERIT (i.e. O_CLOEXEC) correctly
>
> * the ability to reimplement open and friends using the underlying NTDLL
> functions (Unicode-friendly, >260 characters per path, etc.)
>
> * the ability to use _free_osfhnd in the close module
>
> However, it is bad that these data structures can change for every version
> of MSVC. At some point, you have to balance flexibility and
> maintainability.
python see http://svn.python.org/projects/python/trunk/Modules/posixmodule.c
seems to have solved a lot the maintenabilty stuff by determining the
actual size of the structure is determined at runtime.
Another option will be to include %SDK%\src\crt\internal.h and use
wrapper function. internal.h is needed for compiling openssl.
Any thought ?
Bastien
> Paolo
>
Re: msvc-inval: more options, Bruno Haible, 2011/09/27