- Jan 12, 2004
- 20,133
- 1
- 0
Originally posted by: cheezmunky
2305843009213693951?
that has to be too easy
Originally posted by: KLin
2305843009213690000
maybe 42
EDIT: could be 1152921504606850000
Originally posted by: chuckywang
Then what is it?
Originally posted by: Jmmsbnd007
2305843009213693951
according to windows calc
no you don'tOriginally posted by: chuckywang
Originally posted by: Jmmsbnd007
2305843009213693951
according to windows calc
i want it factored (as in prime factorization), not as a decimal.
Originally posted by: her209
2^0 = 1
2^1 = 10
2^2 = 100
2^3 = 1000
...
2^61 = 1000...0 (61 zeros)
(2^61)-1 = 1111...1 (60 ones)
Does that help any?
Originally posted by: BigPoppa
Originally posted by: her209
2^0 = 1
2^1 = 10
2^2 = 100
2^3 = 1000
...
2^61 = 1000...0 (61 zeros)
(2^61)-1 = 1111...1 (60 ones)
Does that help any?
Ummm:
2^0 does in fact = 1.
2^1 = 2
2^2 = 4
2^3 = 8
2^4 = 16
and so on. I have no clue what you think you were doing![]()
Originally posted by: her209
2^0 = 1
2^1 = 10
2^2 = 100
2^3 = 1000
...
2^61 = 1000...0 (61 zeros)
(2^61)-1 = 1111...1 (60 ones)
Does that help any?
Originally posted by: chuckywang
Originally posted by: beer
MATLAB gives me a middle finder![]()
Exactly.
Originally posted by: beer
Originally posted by: chuckywang
Originally posted by: beer
MATLAB gives me a middle finder![]()
Exactly.
I looked into the underlying code to figure out why. I read the comments and they said they chose to error-out if n > 2^32 due to large memory consumption. Thinking I was a badass, I removed the error checking in factor.m and executed the code - the underying reason matlab won't do it is that the function primes.m creates a vector 1:2, and that vector op - and for that matter, every vector op in matlab - seems to peg an upper bound at 2^32 elements
Originally posted by: beer
Originally posted by: chuckywang
Originally posted by: beer
MATLAB gives me a middle finder![]()
Exactly.
I looked into the underlying code to figure out why. I read the comments and they said they chose to error-out if n > 2^32 due to large memory consumption. Thinking I was a badass, I removed the error checking in factor.m and executed the code - the underying reason matlab won't do it is that the function primes.m creates a vector 1:2, and that vector op - and for that matter, every vector op in matlab - seems to peg an upper bound at 2^32 elements
Originally posted by: RaynorWolfcastle
Originally posted by: beer
Originally posted by: chuckywang
Originally posted by: beer
MATLAB gives me a middle finder![]()
Exactly.
I looked into the underlying code to figure out why. I read the comments and they said they chose to error-out if n > 2^32 due to large memory consumption. Thinking I was a badass, I removed the error checking in factor.m and executed the code - the underying reason matlab won't do it is that the function primes.m creates a vector 1:2, and that vector op - and for that matter, every vector op in matlab - seems to peg an upper bound at 2^32 elements
probably because integers larger than 32-bits are a mess to deal with on x86 and require you to make a new underlying datatype to get around the fact that there's no longlong datatype.
Originally posted by: BigPoppa
Originally posted by: her209
2^0 = 1
2^1 = 10
2^2 = 100
2^3 = 1000
...
2^61 = 1000...0 (61 zeros)
(2^61)-1 = 1111...1 (60 ones)
Does that help any?
Ummm:
2^0 does in fact = 1.
2^1 = 2
2^2 = 4
2^3 = 8
2^4 = 16
and so on. I have no clue what you think you were doing![]()
Originally posted by: JohnCU
Originally posted by: BigPoppa
Originally posted by: her209
2^0 = 1
2^1 = 10
2^2 = 100
2^3 = 1000
...
2^61 = 1000...0 (61 zeros)
(2^61)-1 = 1111...1 (60 ones)
Does that help any?
Ummm:
2^0 does in fact = 1.
2^1 = 2
2^2 = 4
2^3 = 8
2^4 = 16
and so on. I have no clue what you think you were doing![]()
he's doing binary.