array as one input...

[ktran03]

how would you assign values into an array with one single input.

for example, if the user input 123456789 [enter]

how would I get 1 into array[0], 2 into array[1] .. and so on...

so far I have this

for (i=0; i<10; i++)
{
printf("Enter value #");
scanf("&#37;d", &value);
array[i] = value;
num++;
}

but this takes the input as individual inputs...

[tabstop]

How do you know what the answer is supposed to be? Why shouldn't it be 12, 34, etc.? If the answer is "they're always single digits", then you need to read one character at a time.

[ktran03]

How do you know what the answer is supposed to be? Why shouldn't it be 12, 34, etc.? If the answer is "they're always single digits", then you need to read one character at a time.

digits are 0-9 only, so yea....always single digits


so there's no way to break up 0123456789 and place each digit into an array?

there must be

[tabstop]

Yes there is, but you're flirting with disaster: you can store up to 2147483647 in an int, and 4294967295 in an unsigned int, but you can't get 9876543210. What's wrong with reading one character at a time?

Edit: Yes I know that "most people" can get those numbers, and some can get different ones. Not the point.

[ktran03]

Yes there is, but you're flirting with disaster: you can store up to 2147483647 in an int, and 4294967295 in an unsigned int, but you can't get 9876543210. What's wrong with reading one character at a time?

Edit: Yes I know that "most people" can get those numbers, and some can get different ones. Not the point.

I just browsed through my reference book to confirm the limitation you mentioned.

how does a program that calculates PI to a million decimal places store the value?
there has to be a way to store 9,999,999,999.......

excuse my ignorance, I'm pretty new to this.

[ktran03]

What's wrong with reading one character at a time?

from my marking scheme, one character at a time is fine...

I just think it would seam a lot more sensible to enter it as one digit.

[tabstop]

I just browsed through my reference book to confirm the limitation you mentioned.

how does a program that calculates PI to a million decimal places store the value?
there has to be a way to store 9,999,999,999.......

excuse my ignorance, I'm pretty new to this.

Custom data types. And if it's not supposed to be one number, why read it in as one?

[ktran03]

Custom data types. And if it's not supposed to be one number, why read it in as one?

it is suppose to be one number... kind of like a credit card number...


so there's no easy way of doing this huh?

[tabstop]

I'm still thinking one character at a time.

[ktran03]

is see it as an inconvenience...

[lattica]

Why not read the number as a string of digits?

[matsp]

If it's a credit card number, then it is not a "number", it's a string consisting of digits - because you will NEVER use it for calculations ("what's 1000 + your credit card number" isn't one of the sensible questions to ask about a credit card number).

By the way, I'm pretty sure all credit card numbers are 16 digits, which is decidedly more than a 32-bit integer can handle (about 11 digits). So if that's what you are working with, then a string is the right solution. Note also that to separate 10 digits out of a string requires about 3 clock-cycles per item, a 10 digit integer to be separated out to individual digits will require something in the order of 10-20 cycles per digit on a modern processor, and many more cycles on an older generation processor, so there is no benefit in storing it as a number if you are going to do lots of messing around with individual digits (e.g. validating that it's a valid credit card number by adding the digits together, checking which main credit card organization (mastercard, visa, american express, etc) issued the card by checking the first digit, etc, etc).

--
Mats