[02:46] Join: SeBaZtIaN joined #corewars [02:46] hola [02:50] Part: SeBaZtIaN left #corewars [03:15] Join: Caelian_ joined #corewars [03:18] MSG: Ping timeout: 252 seconds [04:12] Join: novenary joined #corewars [04:13] hi [04:14] new to corewars, just wondering how to learn the syntax? [04:16] learning linux x86 asm already, so I figure that helps :S [04:23] well, ordinary asm doesnt really help that much [04:24] http://sfghoul.blogspot.com/2007/07/top-10-links-for-corewar-newbies.html [04:26] Awesome, thanks for that link! The other tutorials I came across were a bit cryptic. [04:29] well, they are [04:29] redcode isnt that hard as a language, but pointers are a hard concept as themselves, not only in redcode, and modifiers will cause a lot of confusion [04:31] it would help with one of the tutorials were updated with an animation to show what exactly happens, but i have been too lazy to bother, and newbies are rare enough that there isnt any pressure to update the tutorials [04:31] im a bit familiar with pointers in relation to memory stacks with assembly. Is there any coherence to that? [04:34] there are no stacks in redcode, but the concept of pointers is same [04:37] oh alrighty. Well hopefully I can tackle this beginner's guide and get a warrior coded up tonight [04:42] Do most people toss them up on a hill to test them out? [04:46] generally people have their own benchmarks to dry-test warriors against [05:44] MSG: Ping timeout: 252 seconds [05:45] Join: Caelian|w joined #corewars [05:55] wow... it seems like im not even slightly understanding this syntax :/ [05:56] other than mov 0,1 [05:57] instruction - addressing mode - A-modifier - A value - B-modifier, B value [05:57] the action of each instruction should be quite obvious [05:59] originally, in the '88 standard there were no addressing-modes. This created complexities when trying to make "creative" coding, and it was hard to sometimes achieve what was wanted [05:59] so they were brought in '94 [05:59] hmm [06:00] example: mov.a 5, 6 moves a-field of instruction +5 to a-field of instruction 6 [06:00] (... of +6) [06:00] mov.ab 5, 6 moves from a-field to b-field [06:00] mov.b : b to b [06:00] mov.ba : b to a [06:00] mov.f : a to a AND b to b [06:01] mov.x : a to b AND b to a [06:01] mov.i : move whole instruction [06:02] there are some cases where the addressing mode seems slightly silly, eg jmp.i . In these cases, the action is defaulted to some other. [06:02] that makes more sense, but so far it's only talking about instructions without .z [06:02] where z is any of those combinations [06:03] ah [06:03] so you are having problems understanding difference between mov #1, $1 and mov $1, $1 ? [06:04] or just everything ?:) [06:04] I'm having troubles trying to see how what is shown makes sense with their examples [06:05] Right [06:05] you can try to download an redcode-interpreter and see in it line-by-line how a program runs [06:07] i usually recommend corewin for beginners, but it is windows-only software [06:07] I have that running right now [06:08] you can use the [view core] and [single step] to achieve the line-by-line viewing [06:09] but i think youll manage the program [06:09] hm, does that show the code for both warriors? [06:10] view core shows the whole core, but youll have to hunt down the second warrior [06:10] in the core-view you can click processes and see where each warrior has processes running [06:11] (double-click a process in the process-menu to take the viewer there) [06:14] I think what I need to do is find a better tutorial..this "Beginner's Guide to Redcode" isnt too friendly, this was the same one I tried tackling before... glosses over the basics that im missing [06:15] just fuond an old tutorial from '91, about '88 ICWS and its making more sense [06:16]