|
Multiple choice allows to select more than one answer! It looks like you are at the wrong place 
But what the hell is array ???
|
|
|
|
|
you have two possible answers and last time i checked (2 > 1) == true;
Basic English should tell you that:
An array is a systematic arrangement of objects, usually in rows and columns.
Referred to in the following fields of study:
Computer science
math and stats
biology
astronomy
technology
and music
So here's my question why join a programming forum ? 
Chona1171
Web Developer (C#), Silverlight
|
|
|
|
|
Chona1171 wrote: So here's my question why join a programming forum ?
Because I am programmer!
Thanks for your explanation. My vote of 5 
|
|
|
|
|
Ah checked your profile you taking a wizz on everyone.
Good one , he simply playing noob. Didnt realize i actually references a couple of your articles for research.
Chona1171
Web Developer (C#), Silverlight
|
|
|
|
|
Alex Fr wrote: What is array? And index?
They're like pizza and tomato, a bit less tasty. 
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Well, at least you are trying to explain... Thanks!!
|
|
|
|
|
Maybe you have learnt at least what is an Array from Codeproject. You should not complain now...
|
|
|
|
|
In the beginning God created the variables.
Variables were always messing around, they got home late at night, and were usually drunk.
They were so many and so uncontrollable that God was starting to get tired of creating things.
So God created the array, where several variables could be handled all at once,
and he saw that it was good.
Since he was so happy with the arrays he created the light the Earth the animals and the humans.
|
|
|
|
|
Wow! This is really great. I am happy that I posted my stupid joke after reading this. Maybe you have similar explanation about indexes?
|
|
|
|
|
Thanks, apparently those English Composition classes are paying off.
What's really funny is that people don't get the joke and think that you are actually retarded
|
|
|
|
|
Despite this is actually a joke, it can be taken very seriously.
Especially if we consider the forum question "... In high-level languages ..."If we also ask what are "high level languages", and provide some contextual definition, the answers can vary a lot!
Hence, the proper format should really had been
-> 0
-> 1
-> any
And I had probably chosen "any".
I voted "0" just because I found "1" arbitrary, but I really think that in a "high level language" array bounds should be specific for each array to reflect what the array itself represents respect to the world it is modeling.
The discrete value of a function can be y[x] with x=(-100..+100;2) (meaning: from -100 to +100 stepping by 2) and yes: it is right to have exceptions if you address wrong indexes.
Some people say this is confusing. But is no more confusing than operator overloading, after all.
2 bugs found.
> recompile ...
65534 bugs found.
|
|
|
|
|
#define BASEADDR (0xFFFF0000)
char* hardwareX = BASEADDR;
hardwareX[0] = 'a';
printf("%d\n", &(hardwareX[0]));
prints: 0xFFFF0000
printf("%d\n", &(hardwareX[1]));
prints: 0xFFFF0001
printf("%d\n", &(hardwareX[2]));
prints: 0xFFFF0002
printf("%d\n", &(hardwareX[3]));
prints: 0xFFFF0003
Seems very logical to me to use zero based indices
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
|
|
|
|
|
|
Seriously, I cannot decide what to vote for, when I do have no CListCtrl option. Please add!
|
|
|
|
|
It's there, but since it lies outside the accepted range of array answers, it's not being displayed.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Try shifting your asses off 'The Cloud' and learn a little history and probably some basic computing too
|
|
|
|
|
I have always thought it crazy that the first element of an array had to be element zero.
That makes no sense to me at all, and yet the vast majority here voted for it.
I shake my head in disbelief.
|
|
|
|
|
I'd have been very concerned if the vote had been the other way round.
|
|
|
|
|
Me too, that would mean an over-population of VB coders! 
|
|
|
|
|
Never heard of FORTRAN?
|
|
|
|
|
Even VB coders know that starting an array at 1 is just wrong. We did it for years because we had to, but we always felt guilty about it. 
There are two kinds of people. Those who need closure
|
|
|
|
|
I don't uderstand all the hate on VB programmer, its kinda discriminating, like somebody "is a lesser being" just because they use a language that somebody dislikes, or considers bad. Anyway I preffer starting in 0, eve though this disscussion is a little pointless and of obvious results.
|
|
|
|
|
I'm not a VB Coder, and never have been, im a Java, C#, and Pascal Coder, and i have been programming for 30 years.
And i have always thought that the first index of an array should be index 1.
'First' and 'One' simply match. Having to use the the length of whatever you are parsing 'minus 1' in every loop, is silly.
IMO 1 .. N, makes more sense than 0 .. N-1,
There are so many here defending the zero based index .. passionately even. Amazing.
|
|
|
|
|
mojp wrote: Having to use the the length of whatever you are parsing 'minus 1' in every loop, is silly.
If you run your loops with a limit < Length instead of <= Length-1 then you don't have to subtract 1 every time.
|
|
|
|
|
May be you should have started with C ...
Think about it another way:
- you have read NOTHING (count=0)
- you read in the FIRST element into an array (array[count]) ==> array[0]
- you increment the read counter (count++)
- you read in the NEXT element into the array (array[count]) ==> array[1]
after you finished, you have the count already.
Additionally, as many others mentioned, an array is nothing more than
an contingous area of memory, and (in C) a reference to the entire array
is the start address of the memory area (array == &(array[0])), and
you can also read an element with dereference of the pointer plus offset
*(array + offset) == array[offset] / array + offset = &(array[offest])
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
