OT: Stupid c++ (Roguelike development)

[narf poit chez BOOM]

Can anybody see a problem with this:

void setupItems () {
srand ( time(NULL) );
// NewWeapon.initialize (); NewPotion.initialize ();
// WeaponList.push_back ( NewWeapon ); PotionList.push_back ( NewPotion );
for ( t = 0; t < 40; ++t ) {
t2 = rand () % 2;
if ( t2 = 0 ) {
NewWeapon.initialize (); WeaponList.push_back ( NewWeapon );
WeaponList[WeaponList.size () - 1].initialize ();
ItemList.push_back ( &WeaponList [WeaponList.size () - 1] );
};
if ( t2 = 1 ) {
NewPotion.initialize (); PotionList.push_back ( NewPotion );
PotionList[PotionList.size () - 1].initialize ();
ItemList.push_back ( &PotionList [PotionList.size () - 1] );
};
};
for ( t = 0; t < ItemList.size (); ++t ) {
ItemList[t]->initialize ();
std::cout << t << " " << ItemList [t]->XPos << " " << ItemList [t]->YPos << " " << ItemList[t]->Colour << " ";
};
std::cin >> wait;
};

It doesn't seem to work right - It seems like all the slots still reference as the base Item class.

[AngleWyrm]

Bug: if(t2 = 0) // assign zero to t2, return true (successful assignment)
You probably meant: if(t2==0) // test for equality

Happens so often that some compilers even have a warning for it.

[narf poit chez BOOM]

Thanks. We're whacking it into shape on IRC.

[narf poit chez BOOM]

Update: Simple Roguelike v0.1.2.5
Features one type of weapon and one type of potion (healing).

There are few glitches, but nothing game-breaking, I think.

Fixed a few game-breakers. Now, to make it generate new items with a new level.

[narf poit chez BOOM]

Update: Simple Roguelike v0.1.3

Should all work.

[narf poit chez BOOM]

How important is it that an object has a destructor? As far as I know, the 'delete' command is unstable.