General > Off Topic

Evolving program

(1/3) > >>

triclops200:
I am, im c#, trying to make a life-copying program that can build/compile new programs.
I have two different theories on how it will work, limited and less-limited, and I need help to choose which and guidence after that. (and also, if it would even be possible)


"problems I see
        1.) every prog wil be* large"

---edit---
I capitalized all my I's for Numsgil

Numsgil:
I think what you want is CIL.  It's the stack based assembly language that C# is "compiled" down to before it's JITed client side.

I think you're going to have a hard time evolving the programs if they're supposed to run as client level programs in an OS (eg: windows).

Houshalter:
Oh geez. Is this another debate on trying to get alife to run in assembly. Even if you could get it to work its a bad idea. Creating a evolving self-replicating virus is dangerous  . Although it would be awesome, assuming it wouldn't kill us all or destroy the internet. Honestly, I don't know what your talking about so maybe I should stay out of it.

triclops200:
I was going to build a newer, simpler assembly launguage which will only start with basic commands such as:
/dec int .A
/dec int .B
/dec int .C
/wr 'hi'
/=.C .A .B +                                  (C=A+B )
/wr .C
/replecate
then on mutate it does:
/dec int .A
/dec int .B
/dec int .C
/wr 'hi'
/=.C .A .B -                             (C=A-B )
/wr .C
/replecate
that's just an example

Numsgil:
What's the ultimate goal?  Or better yet, what's the fitness landscape you're going to be using?  Is it supposed to solve a specific problem (ala Avida) or are you going to be releasing your creations "to the wild" of a raw OS?  That's going to dictate a lot about the language design, or whether you should use something pre-existent, etc.

Navigation

[0] Message Index

[#] Next page