Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

Control Flow

2 (2.2%)

Arrays, Strings, Pointers, and References

8 (9%)

Functions

4 (4.5%)

Basic object-oriented programming

30 (33.7%)

A bit more advanced OOP (Composition, Operator overloading, Inheritance, Virtual Functions)

18 (20.2%)

Templates

8 (9%)

Other (Explain)

4 (4.5%)

Working with files?  (Streams)

15 (16.9%)

Total Members Voted: 89

[Virex]

It's a tail call (I used tail recursion because that's where it comes up most often), so it ought to work. You're free to prove me wrong though.

[lordnincompoop]

Thanks, hopefully this'll work.

[qwertyuiopas]

If it doesn't, then it would still be possible to have a central function that switch()s between the rooms, and each room returns the integer ID of the next room (including, possibly, itself, and special codes, like exiting)

[Virex]

I don't suppose it's possible to return functions directly in C++? Because that'd solve the headache of maintaining a switcher function.
Scratch that, you can

[eerr]

Not only can you return pointers to functions, you can return pointers to pointers to functions, which can return pointers to pointers to functions.

[lordnincompoop]

 

[Virex]

Not only can you return pointers to functions, you can return pointers to pointers to functions, which can return pointers to pointers to functions.

I'm not sure why you'd want to do that, but an array of pointers to functions certainly has it's uses as a queue of actions (though you may want to use a heap for that)

[alfie275]

>N

[lordnincompoop]

Small programming dilemma. Should I dynamically (or whatever) create items by having an empty item template and assigning values to it (such as size, weight, value, description etc.) and do that each time, or should I make a list of predefined items and pick one from that?

[Shades]

Small programming dilemma. Should I dynamically (or whatever) create items by having an empty item template and assigning values to it (such as size, weight, value, description etc.) and do that each time, or should I make a list of predefined items and pick one from that?

Depends on your situation, which I admit is no help at all.

Generally I'd predefine the items if there was relatively few possibilities and I'm likely to be creating and deleting many of them over and over. Your basically treating the item as a constant and creating references / pointers to it in this case.

If your item set is large and varied you might be better of creating them. However if they are the same class but different values there is no reason you couldn't throw them onto a stack once done with them and reuse the memory next time you need a new one, rather than creating and deleting.

[lordnincompoop]

Currently I have 10 empty "slots" in my player class. Each slot is a class by itself and contains a few variables to make this work, along with some methods. The inventory is an array of these classes, and I give/take items from the player by assigning values to the slots.

The question is whether I'm approaching this the right way. I'll have a large amount of various items, but a problem is whether I can keep them consistent. I don't want a laundry list of items like "soil", "Soil", "Dirt", "Earth", etc. that all mean the same thing.

Besides, what if I want an item with some special values?

[Rose]

you could just make sure there never actually is more than one Dirt.

you are the programmer.

you have the power.

[lordnincompoop]

Waitwhathow

[Rose]

you chose what items are there.

there is only more than one type of dirt if you put it in there.

[ILikePie]

Found a neat little article I found about bitwise operators and tricks that can be done with them: http://graphics.stanford.edu/~seander/bithacks.html#CopyIntegerSign
Been messing with this all day.