00:38:42 -!- amalloy_ is now known as amalloy 00:42:19 Gadrel (L19 OgFi) ASSERT(!invalid_monster(&mons)) in 'mon-death.cc' at line 1716 failed. (Spider:4) 02:21:24 Experimental (bcrawl) branch on underhound.eu updated to: 0.23-a0-2989-g2cb1824106 03:55:39 Fork (bcadrencrawl) on crawl.kelbi.org updated to: 0.22.1-2544-g74171b84a8 05:52:23 -!- amalloy is now known as amalloy_ 09:49:32 alexjurkiewicz: that's a known issue, I have some notes on how to fix it but not time to confirm and implement at the moment 09:49:45 win 2 10:23:10 Stable (0.22) branch on underhound.eu updated to: 0.22.1-61-g4f546fdb5a 12:23:00 Stable (0.23) branch on underhound.eu updated to: 0.23.1-93-ge536e68a2c 13:20:24 -!- amalloy_ is now known as amalloy 15:17:48 Hellmen2010 (L17 VpSu) ASSERT(!invalid_monster(&mons)) in 'mon-death.cc' at line 1714 failed. (Vaults:2) 15:59:09 -!- Tiobot is now known as Guest32623 16:04:47 -!- geekosaur29 is now known as geekosaur 16:11:39 -!- geekosaur40 is now known as geekosaur 21:13:46 -!- amalloy is now known as amalloy_ 21:43:29 const int weap_eq = you.equip[EQ_WEAPON]; weap_eq = -1; 21:43:40 if I write this ^, does it set you.equip[EQ_WEAPON] to -1? 21:43:47 that should fail to compile 21:53:08 -!- amalloy_ is now known as amalloy 21:58:08 if you removed the const, it would compile but not do what you want 21:58:35 alexjurkiewicz: you want a reference, if you want to be able to write through. int& weap_eq = ... 22:03:48 heh I decided to not say that because I didn't want to encourage it :-P 22:27:00 it's not encouraged? 22:27:39 I end up with lines like this: 22:27:41 if (you.equip[EQ_WEAPON] != -1 && !can_wield(&you.inv[you.equip[EQ_WEAPON]])) 22:28:07 instead of: if (eq != -1 && !can_wield(&item)) 22:30:37 taking a const reference to it would be totally normal imo. writing through a reference to update what you're actually wearing is a bit more questionable 22:41:48 -!- Tux[Qyou] is now known as Tux[QLUL] 22:41:50 -!- Tux[QLUL] is now known as Tux[Qyou]