> Note: under CE, you can actually encounter datatype misalignments, since it
> runs on CPUs that don't emulate them. I wonder if the same doesn't also apply
> to win64
I don't think you can get misalignment traps on AMD64. Not sure about
IA-64: I know that the processor will trap on misalig
> From: eckha...@satorlaser.com
> To: python-dev@python.org
> Subject: Re: [Python-Dev] FormatError() in callproc.c under win32
> Date: Tue, 27 Jan 2009 12:16:01 +0100
> CC: coder_infi...@hotmail.com
>
> On Monday 26 January 2009, Martin v. Löwis wrote:
> > >
On Monday 26 January 2009, Martin v. Löwis wrote:
> > In callproc.c from trunk is a function called SetException(), which calls
> > FormatError() only to discard the contents. Can anyone enlighten me to
> > the reasons thereof?
>
> Interestingly enough, the code used to say
>
>PyErr_SetString(P
On Monday 26 January 2009, Thomas Heller wrote:
> Ulrich Eckhardt schrieb:
> > In callproc.c from trunk is a function called SetException(), which calls
[...]
> > My third approach would be to filter out the special error codes first
> > and delegate all others to PyErr_SetFromWindowsErr(). The lat
> In callproc.c from trunk is a function called SetException(), which calls
> FormatError() only to discard the contents. Can anyone enlighten me to the
> reasons thereof?
Interestingly enough, the code used to say
PyErr_SetString(PyExc_WindowsError, lpMsgBuf);
Then it was changed to its c
Ulrich Eckhardt schrieb:
> Hi!
>
> In callproc.c from trunk is a function called SetException(), which calls
> FormatError() only to discard the contents. Can anyone enlighten me to the
> reasons thereof? Is it just to check if the errorcode is registered in the
> stringtables?
I think that yo
