From corewar-l@stormking.com Fri Apr 19 20:31:06 1996 Received: by couchey.inria.fr (5.57/Ultrix3.0-C) id AA27040; Fri, 19 Apr 96 20:31:06 +0200 Received: from uu3.psi.com (uu3.psi.com [38.145.250.2]) by nez-perce.inria.fr (8.7.1/8.7.1) with SMTP id UAA05440 for ; Fri, 19 Apr 1996 20:30:58 +0200 (MET DST) Received: by uu3.psi.com (5.65b/4.0.940727-PSI/PSINet) via UUCP; id AA02434 for ; Fri, 19 Apr 96 10:01:12 -0400 Received: from (server@localhost [127.0.0.1]) by valhalla.stormking.com (8.6.12/8.6.12) with SMTP id MAA04999; Fri, 19 Apr 1996 12:45:56 -0400 Date: Fri, 19 Apr 1996 12:45:56 -0400 Message-Id: <4l7squ$18r@sparcserver.lrz-muenchen.de> Errors-To: tuc@stormking.com Reply-To: guenzel@extern.lrz-muenchen.de Originator: corewar-l@stormking.com Sender: corewar-l@stormking.com Precedence: bulk From: guenzel@extern.lrz-muenchen.de (Bjoern Guenzel) To: Multiple recipients of list Subject: Re: idea for anti Imp clear X-Listprocessor-Version: 6.0b -- ListProcessor by Anastasios Kotsikonas X-Comment: Usenet News "rec.games.corewar" I assume my former code did not really work... Anyway, I think this sequence should set up a temporary imp-gate: Is djn.f #0,>gate a perfect imp-gate (I mean does it also block gate-crushing imps)? I could imagine it is, because it attacks two parts of the imp in a row. jmz #0,ptr mov wait,@ptr ptr djn.f #0,>-20 jmp dec-resistant code+1.... wait dat #1000,0 bomb dat 0,0 unfortunately this will decrement itself after it has killed an imp, and also the worst-case delay is 9000 cycles.... :-( I guess my idea will not really become an alternative to spiral wipes. Perhaps if you copy the whole clear... But it's funny, I think. Bjoern P.S.: In the following situation the djn does not run over the gate: gate dat #0,#0 ... djn.f #0,>gate ;<- execute evaluates (I am not sure about the a-field) to gate dat #-1,0 ... djn.f #0,>gate ;<- execute I used this to write a imp-proof coreclear that also allows for a semi-protection against sef-destruction by the clear running inside. That was part of 'Anti Imp', and I called it dirty clear, because it clears only every second position and decrements the other in one row. I guess I can omit the code... Or wait, it was like this (from memory, hope it works): ;name dirty clear ;author bjoern guenzel gate dat #0,bptr+1 for 5 dat 0,0 rof jptr spl #1,>gate mov *bptr,>gate djn.f *jptr,>gate dat }gate,>gate protect mov #1,1 ;I was too lazy to think of something effective... ;I hope you enjoy... :-) dat #protect-jptr,bptr+1-gate bptr dat #0,bptr-gate ;bomb never hits this I hope you like it! I am not sure if it is always suitable as a clear, haven't tried to cill paper like that so far. As the spl shifts the pattern from time to time, it covers almost the whole core - if 100% are needed, more bombs have to be added.