[sage-devel] Re: Including 64-bit-only code in Sage

2017-09-21 Thread Dima Pasechnik
On Wednesday, September 20, 2017 at 10:40:39 PM UTC+1, Volker Braun wrote: > > On Wednesday, September 20, 2017 at 12:12:33 PM UTC+2, Dima Pasechnik > wrote: >> >> Still, why don't we start by including this code as an experimental >> package? >> > > > Thats fine, but the way I understood

[sage-devel] Re: Including 64-bit-only code in Sage

2017-09-20 Thread Volker Braun
On Wednesday, September 20, 2017 at 12:12:33 PM UTC+2, Dima Pasechnik wrote: > > Still, why don't we start by including this code as an experimental > package? > Thats fine, but the way I understood Kiran he wants to make it standard. -- You received this message because you are subscribed

Re: [sage-devel] Re: Including 64-bit-only code in Sage

2017-09-20 Thread Dr. David Kirkby (Kirkby Microwave Ltd)
On 20 September 2017 at 07:58, Volker Braun wrote: > IMHO its a code smell if your code doesn't work on 32-bit platforms. > Remember, almost all 32 bit platforms are perfectly capable of working with > 64-bit integers (just not as fast). But your code must be *correct*

[sage-devel] Re: Including 64-bit-only code in Sage

2017-09-20 Thread Dima Pasechnik
On Wednesday, September 20, 2017 at 7:58:34 AM UTC+1, Volker Braun wrote: > > IMHO its a code smell if your code doesn't work on 32-bit platforms. > Remember, almost all 32 bit platforms are perfectly capable of working with > 64-bit integers (just not as fast). But your code must be *correct*

[sage-devel] Re: Including 64-bit-only code in Sage

2017-09-20 Thread Volker Braun
IMHO its a code smell if your code doesn't work on 32-bit platforms. Remember, almost all 32 bit platforms are perfectly capable of working with 64-bit integers (just not as fast). But your code must be *correct* (e.g. use uint64_t), and not just coincidentally work on some compiler/platform