You are supposed to pass the variable spade, not spade[0,13] (is that even valid syntax?).
I am getting a little confused by Java at the moment, but in C++ I would write it as:
Code:void displayCards(string spade[]) { for (int i=0; i<13; i++) cout << "S: " << spade[i]; } // To call it. displayCards(spade);
Look up a C++ Reference and learn How To Ask Questions The Smart WayOriginally Posted by Bjarne Stroustrup (2000-10-14)
hahahaha yeah, i wasn't pt sure about that, but it compiled fine, and no one picked up on it so i thought i must of been right... but even after i fixed that up it still doesn't want to work for me!
now i get
19 expected `,' or `...' before "spade"
In function `void displayCards(std::string*)':
22 `spade' undeclared (first use this function)
[Build Error] [main.o] Error 1
Be careful of your case. In your early examples, you wrote it as Spade. Later, you wrote it as spade. You need to be consistent because C++ has case sensitive identifiers.
Look up a C++ Reference and learn How To Ask Questions The Smart Way
F@$k ME! after all that i just had to move the "[]" over, hahaha thanks for the help every one!
the joys of learning, really dose your head in at times
I was just curious, you can pass an array to an function, but can a function return an array?
Short answer is yes, but there's a few things to consider. When you pass an array to a function, you're really passing a pointer to the first element under the hood. You don't really see this, but it's vitality important to understanding how this works.
The pointer/array relationship becomes a little more apparent when trying to return an array. You end up having to return a pointer to the first element of the array. All good, right?
Well, here's another issue: You can't return local arrays. Local variables are destroyed some time around the end of the function because they are allocated on the stack. If you return a block of memory from a function, as a general rule you need to dynamically allocate it with new (or malloc() for C programs).
