Array as class member?

The size of the array will cause major trouble if you try to instanciate the class on the stack.

Use a vector<int> instead, and manually convert from 2D to 1D coordinates:

[y][x] <-> [y*xsize+x]

Could you explain a little more in depth what you mean in that last statement, also how would I then set a room to a certain location in the vector?

(I'm still a bit n00bish with this vector/array/class stuff)

for one to try and help you, it would be good if you explained what you are trying to achieve. as for the class format, its good. the declaration of the 2-dimension array is alright.

hope you have a class "string" because some compilers usually bring some errors on this declaration. otherwise all the best.

What I want to set up is some kind of array type thing with m_RoomLoc so that when you are playing the text adventure and enter a certain room it checks the surrounding sections in that array for different exits from that room, ie.


0010
0101
0031


Now if the player was in '3' then he could move northwest, northeast and east.

Instead of using a 2D indexing notation, which requires either the use of C arrays, kludgy arrays of arrays (and their vector counterpart) or developing your own 2D array classes, you should just use the equivalent 1D indexing notation, which allows you to directly use a vector member.

Just keep track somewhere of how wide your array is supposed to be, and instead of using a 2D array and accessing element n = array[y][x], you can compute the corresponding index and use a 1D array n = array[y*width+x].

I don't think the problem here is how to implement the array, but rather where to implement it. Looking at the 'cRoom' class I take it you want the class to be implemented for each room, in which case the location array shouldn't be in there as it will be created every time you instantiate a room. Instead, from an OO point of view, I think you'd be better creating a Room class that doesn't care about where it is, it just handles details like a description and maybe a list of some items, etc. You'd then have a Map class that imlpements a vector of Room classes and handles where the rooms are in that vector, etc.

Search google for "single linked list" or "double linked list" and you will find information that will make you cry with happiness. ;)

Anyway, it's really unnecessary (sp?) to have each room know ALL rooms... simply connect it's neighbours using linked lists! :)

or if you really want to hardcode the neighbours, you could either store the map ONCE, and make each tile remember it's position, then simply check its neighbours on the "global" map, or make each tile store only the max amount of connections around it... i.e 8 rooms in 2D, and 26 for 3d or something..

Cheers!