[02:29] Join: Caelian_ joined #corewars [02:33] MSG: Ping timeout: 240 seconds [03:15] MSG: Read error: Operation timed out [03:16] Join: Mizcu joined #corewars [04:26] MSG: Ping timeout: 240 seconds [04:26] Join: Caelian|w joined #corewars [06:49] MSG: Read error: Operation timed out [06:53] Join: triple joined #corewars [07:29] Join: pak21 joined #corewars [07:36] Morning. Or something [07:38] Just had an boost of inspiration during awfully boring maths-lesson and wrote a test-idea, gotta check later if its any good. [07:43] gtg --> [08:54] MSG: Read error: Operation timed out [10:14] MSG: Ping timeout: 240 seconds [11:35] Join: Caelian|w joined #corewars [13:50] MSG: Read error: Operation timed out [13:55] Join: johnkw joined #corewars [15:17] Join: andares joined #corewars [15:17] Hey. [15:17] Hi. [15:18] How's it going, pak21? [15:21] I'm failing at learning redcode. [15:22] Have you read the tutorials out there? [15:23] Yep. They're not making sense to me. :| [15:23] My background is mainly high-level languages and a smattering of x86 asm. [15:23] So it's pretty foreign to me. [15:23] Any specific problems, or is it just not "clicking"? [15:31] Well.... yeah, mainly it's not clicking. [15:31] I don't get the addressing modes. [15:31] like the difference between @ and $ and } [15:33] $x is fairly easy: it means use the instruction x further on than the current one (all addressing is relative). [15:33] @x means: 1) look at the b-field of the instruction x further on than this one. [15:33] Call that value y. [15:33] Then use the instruction (x+y) further on than this one. [15:36] So...... [15:36] @2 would mean to to the address of this instruction+2, then jump to the address pointed to by the b-field of that instruction? [15:37] Yes. [15:37] This is seeming less RISC-e. :p [15:37] > means the same as @, but increment the b-field after using it. [15:37] * is the same as @, but uses the a-field rather than the b-field. [15:38] } is to * as > is to @. [15:39] So } increments the a-field after using it? [15:39] My brains are leaking again. :( [15:39] Yes. [15:40] Looks like you're getting most of this to me :-) [15:41] I guess, it's confusing. [15:41] My distro only offered one mars for corewars [15:41] and 90% of the bots they bundled with it use this .cw format instead of redcode. [15:41] what is that? [15:42] No idea. [15:42] (Which distro?) [15:42] ArchLinux :o [15:45] pak21, so do people still play this? [15:45] Definitely. [15:45] (But not me, actually...) [15:46] http://www.koth.org/koth.html [15:46] :o [15:46] :o [15:46] http://sal.math.ualberta.ca/ [15:46] ah, cool. [15:46] I'll check that out. [16:25] Join: Core_new joined #corewars [16:43] Join: sf_ghoul joined #corewars [16:43] Hello [16:45] http://sfghoul.blogspot.com/2007/07/top-10-links-for-corewar-newbies.html :) [17:04] MSG: Ping timeout: 240 seconds [17:08] Join: johnkw joined #corewars [17:13] * sf_ghoul steal's bvowk's breakfast! :) [17:13] MSG: Quit: Quick! Kill your client! Bersirc 2.2 is here! [ http://www.bersirc.org/ - Open Source IRC ] [18:03] aww! [18:03] Join: gecko|pai joined #corewars [18:32] MSG: Read error: Operation timed out [19:30] Hey guys, what do you people use on Linux for a mars? [19:43] MSG: Remote host closed the connection [19:57] Join: fiveop joined #corewars [21:34] MSG: Quit: Trillian (http://www.ceruleanstudios.com [22:23] MSG: Quit: humhum [23:16] Join: catron joined #corewars [23:16] hey [23:16] hi [23:17] im new to core wars, im reading about it [23:17] any advice? lol [23:17] ask a lot of questions [23:18] analyze old programs [23:18] ok lol [23:18] get yourself a benchmark [23:18] ok [23:18] i have alot of c++ and python, any other experience necessary [23:18] ? [23:18] neither is much of help :) [23:19] :( [23:19] asm? [23:19] o god please say no [23:19] redcode is too different from x86 asm to be much use [23:19] ok [23:19] ill look around thanks [23:19] http://sfghoul.blogspot.com/2007/07/top-10-links-for-corewar-newbies.html [23:21] ok thanks