[02:24] Join: malady joined #corewars [06:22] *yawn* mornin' [08:06] Now watching: Monty Python and the meaning of life. CW has not yet been mentioned. [12:07] Join: fiveop joined #corewars [12:46] Join: Fluffy joined #corewars [12:46] :+( [12:46] 'yer nose is growing back it seems [12:47] Yes, unfortunately [12:47] I've got a cold [12:47] I don't want to move, but it is quite boring without moving [12:48] even typing is difficult [12:50] hmm ... a new name [12:50] Hi malady [12:54] hmm [13:06] re [13:07] hi all, ye old & new ones [13:15] Hi ares [13:33] i'm surprised, NOP is not accepted by pmars? [13:34] it is [13:34] what did you use? [13:34] "NOP" [13:34] pmarsw.exe, v092 [13:34] syntax error [13:35] in a file before, i could use it... so its not about NOP [13:35] yes, of course, because nop needs arguments [13:35] nop < 1, # 42 [13:35] no [13:35] why??? [13:35] ?? [13:35] nop is a normal redcode instruction like the rest [13:36] so you have to specify full a- and b-fields [13:36] but why does it require params? *g* [13:36] id expect $0 $0 [13:36] that the way it is specified [13:36] only dat has (partial) default arguments [13:36] okay, no prob anymore... i am testing pmars behaviour, its faster by trying than by understanding the code, at least for me [13:36] ... and spl, jmp, spl [13:37] nop oes have, too, it seems. NOP $0 --> NOP $0 $0 [13:37] Didn't know that [13:38] exactly: NOP $n --> NOP $n $0 [13:38] then it should work with every other addressing mode as well [13:38] nop < x --> nop < x, $ 0 [13:39] hopefully [13:53] guess what this compiles into: [13:53] ;redcode [13:53] ;assert 1 [13:53] [13:53] OPC equ SNE [13:53] [13:53] org 2 [13:53] a FOR 2 [13:53] b FOR 2 [13:53] c FOR 2 [13:53] d FOR 2 [13:53] m&a&b&c&d DAT #a-1, #b-1 [13:53] n&a&b&c&d DAT #c-1, #d-1 [13:53] OPC.F m&a&b&c&d, n&a&b&c&d [13:53] NOP $1 [13:53] JMP +3 [13:53] ROF [13:53] ROF [13:53] ROF [13:53] ROF [13:53] SNE.F -3, -2 !! [13:53] what is OPC? [13:53] EQU SNE [13:54] your parser or pmars'? [13:54] pmars [13:54] hmm [13:55] replacing the OPC.F in the loop with SNE.F results in correct compile [13:57] strange... if i would have made this bug, i'd expect a wrong result of SNE.F $0, $-1 [13:59] i mean SNE.F $-1, $0 [13:59] where do you OPC from? [14:00] *know [14:00] its defined by EQU.... is OPC some reserved word? [14:01] oh, didn't see that [14:01] i see it [14:01] between ;assert and org... maybe thats why? [14:02] CMP.F only jumps, if A, B, C and D are zero [14:03] huh? [14:03] checked twice [14:06] okay... my fault... i take it back [14:06] this was the wrong for bug [14:06] huh [14:07] cmp.f works as expected [15:39] how is the character { called in english? [15:48] dunno [15:49] MSG: Ping timeout: 255 seconds [15:49] floff [15:51] Join: Fluffy joined #corewars [15:51] flon [15:58] How about "opening brace"? [15:58] or opening curly bracket? [15:58] better [15:59] or "that fscking character over there"? [15:59] lol [16:01] but you probably want to call it A-predecrement [16:01] maybe A-predecrement (addressing) mode [16:02] i formulated it "If a [16:02] if a "}" is used... [16:02] A-postincrement mode [16:02] ah - selfhtml might know it [16:03] if it only was a named char :-( [16:04] why should it be named? [16:04] because i want to find the name in the list [17:51] * bvowk hacksaws fluffy into chunks, encases the chunks in concrete and sinks them in the ocean [17:51] ? [17:52] you didn't see nothing ares.. [17:52] ic, ehm i dont c [17:53] I have a memory problem with my python evolver now :( [17:53] ouch [17:53] I'm really having trouble figuring out where.. [17:53] yeah, it just keeps getting bigger. [17:55] but sinking fluffy down into the sea might not be the best approach for having him solving the problem, eh? [17:55] I'm pretty sure its related to the scores, but I can't seem to coax python to get rid of them :( [17:55] I wasn't gunna get him to solve the problem! [17:55] I'm just whining. [17:56] although.. [17:56] hey fluffy? [17:56] does your code keep a copy of the score data? [17:58] yes, yes it does. [17:58] er.. [17:58] no it doesn't [17:58] * bvowk grumbles. [18:20] what are you up to ares? [18:20] writing the manual [18:21] and finding out, how pmars works in detail [18:21] wait.. [18:21] your the sourceforge guy aren't you? [18:21] no, i'm not [18:21] (yes, I'm slow) [18:21] not the one that asw emailed me about? [18:22] i dont think so... i am the guy, who is writing ARES [18:23] for i am using a winxp on a 600MHz machin, i am adapted to slow reactions ;-) [18:24] heh [18:24] ares is? [18:24] http://harald.ist.org/ares [18:25] http://harald.ist.org/?site=ares&page=aresmanual (more screenshots) [18:25] hey.. you're a scary guy. [18:25] why? *GG* [18:26] in a good way [18:26] yea, i had that impression *G* [18:26] nice [18:26] thats an impressive project.. [18:27] was hard work... and now i am struggeling with differences between ICWS94 and pmars [18:27] damn, its really got to be in pycorewars [18:28] * bvowk reassembles fluffy and interrogates him about his code. [18:29] * bvowk flies fluffy to romania and makes him stand in stress postions while electrodes are attached to his ear to soften him up [18:33] hey - you cant abduce fluffy - i might need him here for asking thousand stupid questions [18:33] abduct? [18:33] kidnap [18:34] well, I'm willing to let you sit in on our sessions.. [18:34] you just have to promise not to get wierd like the americans do, they're giving torture a bad name. [18:34] heheh - we might get some secrets out of him [18:34] lets call it questioning, okay? [18:35] we're calling it polite tea conversation.. [18:35] and we're on a picnic. [18:36] except for fluffy, we're not feeding him until he cracks.. [18:36] scone? [18:36] * Fluffy is back and reading the logs ... [18:36] uhoh [18:36] see, I told you he'd crack [18:37] now, bvowk, now [18:37] you get my mail fluffy? [18:38] so fluffy, do you keep any of the match data around in your modules? [18:39] because gc.get_objects shows me huge reams of result lists that it won't GC [18:39] hoi, bvowk, to what extend can you modify sal? [18:39] I've already noticed the problem. [18:39] see sal-b for a dummy who needs to be saved [18:39] It might be a little memory leak [18:39] mizcu: what needs to be done? [18:40] its not a little memory leak when you're running an evolver! [18:40] a dummy has a email-addy visible [18:40] it goes straight up to 4G in a couple of minutes.. [18:40] bvowk: I'll check the code [18:40] miz: I don't really have access to do that, and his royal J'ness has gone away for the holidays [18:41] righty-then [18:41] bvowk: That fast? My generator needs a couple of hours to fill one Gig [18:41] fluffy: I have *WAY* more computrons than you do [18:41] thats how the mail-addresses were gives at the corewars.sf.net when it was up [18:41] and I have 4 threads on 4 cores chunrning [18:44] what is gc.get_objects exactly showing? [18:47] * Fluffy sticks tiny needles into bvowk's eyes [18:49] bvowk? [18:51] * Fluffy plugs out bvowk's right eye and throws it at the wall [18:52] sorry fluff.. bbiab [18:52] (10 mins..) [18:52] ok [19:05] hey gens.. [19:05] I've found the bug [19:05] your build clean doesn't actually clean [19:05] huh? [19:06] I've already send you a modified Benchmarkingmodule.c [19:06] python setup.py clean doesn't actually remove anything ;) [19:06] delete everything in the build directory [19:06] yeah, I'm recompiling.. [19:06] but you still have to wait [19:06] I've just noticed, that the same bug is in another file, too [19:06] pmars-parser-question: is there interference between the register variables a..z (used with assigment operator "=") and labels? can i use a single char label without getting into trouble? [19:06] give me 5 mins [19:07] you changed the output format? [19:07] File "hill.py", line 102, in score_hill [19:07] w1_score, w2_score, trash = result [19:07] ValueError: need more than 2 values to unpack [19:07] Join: Core_old joined #corewars [19:07] bvowk: I'll check [19:07] yup, you did [19:08] that seems to have fixed the bug [19:08] thanks jens! [19:08] no, I didn't! [19:09] ok, which PyCorewar version are you using? [19:09] well, I'm not leaking at any rate I can detect [19:09] PyCorewar-0.2.0.28 [19:09] hehe, then I've sent you the wrong file [19:10] heh [19:10] it seems to be working just fine [19:10] why don't you send me your newest copy and I can help debug the -HEAD [19:10] Do you use the parser? [19:10] yup [19:10] er.. [19:10] grrmpf [19:10] no [19:11] I use the parser when I reload from disk.. but other than that.. no.. [19:11] I'm parserless [19:11] the newest copy isn't any help, because the 94nop is defunct at the moment [19:11] you broke -head? [19:11] what kind of a dev leper are you? [19:12] a fluffy one? [19:13] ok, so its still leaking a tiny bit.. [19:14] yes, I know [19:14] but the big hole is stopped [19:19] damn ... it is everywhere :( [19:21] the coding teacher i will be getting will be loving me [19:22] nobody knows about the register assignment? [19:22] there is a better way of choosing one (weighted) option out than just using a huge CASE -statement.. [19:23] whats leaking jens? [19:23] I've messed up the whole reference counting [19:24] hrm. [19:36] ok, now I at least know, where to find the bug [19:45] oh fucking great [19:45] first voodoobug today found [19:45] :) [19:46] how many do you find in an average day? [19:46] bvowk: I give up for today. [19:46] what?! [19:46] you can't give up.. [19:46] I was hoping to hack on this at my parents place.. [19:46] ares: depends on what i work on [19:46] and I'm leaving tommorrow morning. [19:46] * bvowk cracks the whip! [19:46] 1. I've got a cold. [19:46] 2. It is past 20:00 [19:47] 3. I can't think. [19:47] (Not sure, whether I ever could.) [19:47] 4. you suffered an IRC based extraordinary rendition to romania) [19:47] yes, that, too [19:48] How fast does it eat up memory at the moment? [19:48] eat? bytes/second? *ggg* [19:49] * Fluffy plants a small nuclear warhead at ares' computer [19:49] * Fluffy sets countdown to 1 second [19:49] no need for that, fluffy. i use windows [19:49] * Fluffy activates countdown [19:49] MSG: Quit: . [19:49] good [19:49] Anybody else got problems? [19:50] Join: ares joined #corewars [19:50] hmm , I didn't know they have Internet in Heaven [19:51] ...or hell [19:51] i am a ghost writer [19:51] it eats memory at a reasonable rate.. [19:51] but it's likely livable for now [19:51] its the ares-bot chatting with you [19:51] ok, now i have an official headache [19:51] bvowk: I promise to work on that problem :) [19:52] Function's result differs from predicted. Inbuilt function's. [19:53] maybe you forgot to to a specific voodoo ritual? have you installed a skull? [19:54] if i would be working with C, that would be logical [19:54] wow - c and logical in one sentence - i would not dare to do so *gg* [19:55] c is a structured assembler programming language [19:57] its time for.. REDO THE CODE [19:58] is this short for RedCode? [19:58] ehm other way round [19:58] nope [20:00] i guess you havent read my comments well enough since yesterday [20:00] there is irony in me coding again [20:00] and i am too newoldskool to code on C or Python etc [20:03] how is C newskool? [20:04] nya [20:04] I have not yet studied C [20:04] MSG: Ping timeout: 255 seconds [20:05] Ask again in 3 months [20:05] C++ may be newskool... [20:05] huh? [20:05] unless you started programming in the 1950s [20:05] c++ is the devils tool! [20:06] (ok, just kidding) [20:06] somehow it looks nice, but i have zero expirience with ++ [20:06] you can do funny things, and code gets readable in ways, i never could have imagined [20:07] (and unreadable?) [20:07] (no, extactly the opposite, if you use it smartly) [20:08] you know, that there is an obfuscated c code contest? [20:09] indeed there is. [20:09] its got a long and awesome history of awesomeness. [20:10] ioccc.org iirc [20:11] oohkay.. voodoobug found, sort of [20:16] * Fluffy waves [20:16] MSG: Quit: fluffy.i < 1, # 42 [20:41] So, the code wants me to go ass first in a tree.. [20:56] enough of coding [21:12] hum. [21:20] hhe.. [21:21] fat-chance on nano was attempting to explain the lack of a distinct "best" in corewars ;) [21:21] I actually had no illusions that it would make it anywhere near the hill. [21:23] now thats a crap [21:23] new instruction CRP? [21:24] or giveup GUP [21:29] heh [21:29] yeah, I was trying to explain to someone that yes, it *IS* the top warrior on my evolver, but that means nothing.. [21:29] but they weren't getting it ;) [21:30] users? [21:36] no, there was a math person here curious what I was up to [21:36] (as I'm still here after everyone had gone home at noon) [21:36] hihihi [21:52] big netpipe and many useable puters is the path to the dark side [21:53] lies! [21:54] seducing, she is, no? [21:56] don't you say anything bad about computrons! [22:08] of course not, how silly of me [22:43] heh [22:44] fat-chance v2 is *WORSE* than v1 ;) [22:46] Join: Core_old joined #corewars [22:53] hey core [23:15] mumble mumble mumble [23:15] eh? [23:16] i need a better way of doing this [23:17] or else i am going to end up with 200 line if/else/while -statement [23:18] maybe a "RunMode" variable? [23:19] ares, i code in quickbasic [23:19] doesnt matter, if your problem is like i guessed [23:19] what are you doing?