General > Off Topic

Evolving program

<< < (2/3) > >>

triclops200:
I was planning on just letting it go free on a computer nobady needs, maybe my old one. just to see what behaviors would evolve . it was going to have full c# laungauge acess after awhile.

Numsgil:
The thing with that is there isn't anything that can "kill" one of the programs, except if it does something stupid and segfaults.  So once one learns to reproduce you just end up spawning thousands of programs that compete for processing power and memory, but otherwise can't interact in any way (the OS makes sure of that).  So just a heads up that this will probably be less cool than it sounds.

But yeah, I think you'll want to use CIL.  That way you get the benefit of the .NET library, and things are at least sort of sanitized against seg faults and the like.

triclops200:
see, I dont understand CIL, I was going to handbuild a interpreter and run all progs using one central program. that way I could close one window to kill the whole thing. If I knew how to build a O.S. then I would build interactions. I might do a built in interpreter or even a CIL based program later though.

Moonfisher:
You might find this interesting :
http://www.koth.org/pmars/

It's called core wars, and it's basicaly assembler code designed to make the oponent processes segfault
The trick is that mem locations are relative to your own position in the code, making small code bits very powerfull.

Numsgil:

--- Quote from: triclops200 ---see, I dont understand CIL, I was going to handbuild a interpreter and run all progs using one central program. that way I could close one window to kill the whole thing. If I knew how to build a O.S. then I would build interactions. I might do a built in interpreter or even a CIL based program later though.
--- End quote ---

Not to state the obvious or anything, but learning CIL would probably be faster than writing your own assembler language and interpreter.

Navigation

[0] Message Index

[#] Next page

[*] Previous page