I'm sorry to hear that - you might have been wasting your time (but
then, perhaps not).
We decided a while ago that the regular Python releases will not support
VAX/VMS any longer. So any code you write has zero chance of being
integrated into Python (the same holds for m68k code, BTW).
That sai
On Mon, Nov 04, 2013 at 08:47:53PM +, John Klos wrote:
[...]
> The short answer is to skip those tests on VAXen. The better answer is to
> patch any isnan functions to always return false on VAXen and patch any
> code which tries to parse, for instance, float("NaN") to use something
> uncomm
Quoting John Klos :
The nice Python folks who were at SCALE in Los Angeles last year
gave me a Python t-shirt for showing Python working on m68k and for
suggesting that I'd get it working on VAX. With libffi support for
VAX from Miod Vallat, this is now possible.
I'm sorry to hear that -
> We'd have to have one uncommor and two extremely unlikely events all happen
> simultaneously for your example to be of concern:
Understood. But when things run millions of times a second,
"extremely unlikely" things can happen more often that you wanted.
> Two, someone would have to decide to
On Mon, Nov 4, 2013 at 3:47 PM, John Klos wrote:
> What would be the best way to find code which handles evaluation of "NaN"?
I would be surprised to find NaN handling outside of math module, float
object and their complex counterparts (cmath and complex object). Other
areas that deal with NaN
The short answer is to skip those tests on VAXen. The better answer is to
patch any isnan functions to always return false on VAXen and patch any code
which tries to parse, for instance, float("NaN") to use something uncommon,
such as the largest representable number (const union __double_u __infi
I think I spoke to soon on my earlier reply. If you have control
over the whole system, you could *set* policy on behalf of a whole
platform (like VAX) so you can "safely" use an otherwise non-normal
set of bits to designate divide by zero (a negative sign bit with the
rest all zeros, for example
> The nice Python folks who were at SCALE in Los Angeles last year gave me a
> Python t-shirt for showing Python working on m68k and for suggesting that
> I'd get it working on VAX. With libffi support for VAX from Miod Vallat,
> this is now possible.
>
> However, when compiling Python, it seems th
Hi,
The nice Python folks who were at SCALE in Los Angeles last year gave me a
Python t-shirt for showing Python working on m68k and for suggesting that
I'd get it working on VAX. With libffi support for VAX from Miod Vallat,
this is now possible.
However, when compiling Python, it seems tha
