Path: ibmpcug!gwen.pcug.co.uk!dish.news.pipex.net!pipex!europa.chnt.gtegsc.com!newsfeed.internetmci.com!news.sprintlink.net!in2.uu.net!news2.new-york.net!news.stormking.com!peter@carme.sect.civ.hw.ac.uk From: peter@carme.sect.civ.hw.ac.uk (Mr. Peter Ivanyi) Newsgroups: rec.games.corewar Subject: self-replicant Date: 16 Aug 1995 14:04:49 -0400 Organization: Storm King Ind. Inc. Lines: 60 Sender: server@news.stormking.com Distribution: world Message-ID: <9508161750.AA14829@sect.civ.hw.ac.uk> Reply-To: peter@carme.sect.civ.hw.ac.uk NNTP-Posting-Host: valhalla.stormking.com Originator: corewar-l@stormking.com Andy Pierce wrote: > >There are also techniques which have been theorized about, but never made > >viable -- the prime example of this is the self-repair program. If you are > >interested, you could try to construct a competitive self-repair program. > >This has not been done before, although people have tried. > Heh. Strange of you to say this. The archetypal self-repairing > program is the imp-spiral. The simplest instance of a self-repairing > program, it is also by far the most successful. Unfortunately, I have to agree. I can't imagine more simpler self- replicant as an IMP. As a beginner, I wrote a simple warrior program, which try to replicat itself, while it is bombing, and that what IMPs as well can do very well. So, here is the program: ;redcode verbose ;name Jumpy Little Sucker (v 0.0) ;author Peter Ivanyi ;strategy Turn it off before the s... hits you! start MOV target,