Re: How do coders handle 16-bit numbers?
- From: "David Murray" <adric22@xxxxxxxxx>
- Date: 20 Mar 2006 14:38:14 -0800
I think I'm going to stick with what I've got. I've already started
writing a large piece of code which calls this subroutine and it seems
to work well. I have to admit I do not fully understand how the
routine works. I'd have to sit down with an abacus or something and
shift bits around before I could see how it actually works. but from
what I can see the max number of loops for the routine is 17. That
still eats some CPU time, but not as bad as making a loop which adds
the number to itself over and over, which is what I was doing before.
However, if somebody understands the routine and could tell me how to
optimize it for smaller numbers, that would be cool. Really I do not
need a 32-bit result. I only need a 16-bit result.
.
- References:
- How do coders handle 16-bit numbers?
- From: David Murray
- Re: How do coders handle 16-bit numbers?
- From: Craig Taylor
- Re: How do coders handle 16-bit numbers?
- From: Maurice Randall
- Re: How do coders handle 16-bit numbers?
- From: David Murray
- Re: How do coders handle 16-bit numbers?
- From: Charles Richmond
- How do coders handle 16-bit numbers?
- Prev by Date: Re: Recovering Corrupted BASIC programs?
- Next by Date: Re: New Commodore Telnet BBS!!
- Previous by thread: Re: How do coders handle 16-bit numbers?
- Next by thread: Re: How do coders handle 16-bit numbers?
- Index(es):
Relevant Pages
|