RE: Prothon vs. Python integers
From: Mark Hahn (mark_at_hahnca.com)
Date: 05/24/04
- Next message: Paul Prescod: "Re: Prothon should not borrow Python strings!"
- Previous message: David MacQuigg: "Re: Method binding confusion"
- Maybe in reply to: Paul Prescod: "Prothon vs. Python integers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 24 May 2004 11:19:16 -0700 To: "'Python Mailing List'" <python-list@python.org>
> From: Paul Prescod
> I think that in this case, Python is demonstrably better than Prothon.
>
> C:\temp\prothon\Prothon>python
>
> >>> print 2**65
> 36893488147419103232
>
> >>> print 2**65 == (2**65 + 1)
> False
>
>
> C:\temp\prothon\Prothon>prothon
> >>> print 2**65 == (2**65 + 1)
> True
>
> If Prothon is a language designed for the next ten years then
> it should
> be tuned for correctness and ease of use, not for limitations
> of today's
> hardware.
I'm sure this isn't the only place Python is better.
Prothon has the long integer support in the parser if anyone wants to
take the trouble to put the long object code in. I did nothing to
preclude it. I just didn't see any need for it myself and didn't take
the trouble to put it in.
Longs seemed like a needless exotic kludge to me in the 64-bit world.
Surely once you get to 3.7e19 you are in floating point territory. I
can't imagine counting anything up to 10**19.
- Next message: Paul Prescod: "Re: Prothon should not borrow Python strings!"
- Previous message: David MacQuigg: "Re: Method binding confusion"
- Maybe in reply to: Paul Prescod: "Prothon vs. Python integers"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
