00:33:44: -!- john_metcalf has joined #corewars.
09:31:50: -!- john_metcalf has quit (Ping timeout: 240 seconds).
09:38:40: -!- john_metcalf has joined #corewars.
19:28:28: -!- fiveop has joined #corewars.
19:29:16: <fiveop> I encountered an interesting problem again, while implementing the mars.
19:30:01: <fiveop> let's say we have the warrior: 'first dat 0, 0 \n dat first * 2, 0 \n'
19:30:07: <fiveop> what's the a value of the second dat?
19:30:11: <fiveop> is it -2?
19:30:19: <fiveop> or is it (coresize - 1) * 2?
19:31:49: <fiveop> Labels are
19:31:50: <fiveop> 0261 converted to an address relative to the current instruction.
19:31:54: <fiveop> from the '94 standard
19:32:08: <fiveop> That's not unambiguous
19:32:37: <fiveop> but it should probably be the relative address with the smallest absolute value
19:32:58: <fiveop> and if both negative and positive relative addresses have the same absolute value, one needs a tie breaker
19:42:21: -!- fiveop has quit (Quit: humhum).
19:46:43: -!- impomatic has joined #corewars.
19:52:43: -!- john_metcalf has quit (Ping timeout: 246 seconds).