Den tisdag 7 april 2015 kl. 17:00:53 UTC+2 skrev MRAB: > On 2015-04-07 15:36, jonas.thornv...@gmail.com wrote: > > Den tisdag 7 april 2015 kl. 16:30:15 UTC+2 skrev Denis McMahon: > >> On Tue, 07 Apr 2015 09:29:59 -0400, Dave Angel wrote: > >> > >>> On 04/07/2015 05:44 AM, jonas.thornv...@gmail.com wrote: > >> > >>>> I want todo faster baseconversion for very big bases like base > >>>> 1 000 000, so instead of adding up digits i search it. > >> > >>> How do you know the baseconversion is the bottleneck, if you > >>> haven't written any Python code yet? > >> > >> He doesn't. He doesn't comprehend that as far as a computer is > >> concerned an integer has no specific 'base', it's only when > >> presented in a form for humans to read that it gets base > >> information added in the representation. > >> > >> He's making these and other similar errors in the javascript groups > >> too. > >> > >> I suspect he's one of those people that spends his time thinking > >> up elaborate solutions that he has no idea how to implement as a > >> response to dreamt up non existent problems. > >> > > Bullshit declare two integers in any language one 7 and one 4 and > > then write x=7+4; if you find a programming language where that does > > not yield 11 tell me. > > > > Integers are internally assumed to be base 10 otherwise you could not > > calculate without giving the base. > > > > All operations on integers addition, subtraction, multiplication and > > division assume base 10. > > > Sorry to say this, but that's nonsense. > > It doesn't matter what base it's working in internally; usually it's > base 2 (binary), because that's simpler to implement. > > It's only when you're converting from or to text that you need specify > a base. Humans prefer base 10, so they've make that the default.
No that is not what i am saying, i am saying if you do operations on two integers the machine will assume base 10. -- https://mail.python.org/mailman/listinfo/python-list
