DNA command line interpreter

[Prsn828]

Allowing whitespaces sounds like a good idea, not sure I like allowing mixed cases.
I kinda like compilers to be very strict, they shouldn't swallow anything (Unlike a good gf   )

Hmm, you're more than a little suggestive there

Anyway, if you spell it wrong, or use a symbol that doesn't exist in the system, it won't work, but other than that, it is the same as any other case-insensitive programming language.

[Botsareus]

I know this is a really, really old thread. But:

Numsgil, why do you want as few commands as possible natively?
I think bots can benefit from naturally evolving compound commands... I actually added them to DB2 from an evolution stand point. I didn't really care that it makes life easier for the programmer.

[Numsgil]

Codules would basically let you build your own commands, and the smaller the list of DNA commands the easier it is to test and debug.

For evolved code, the smaller the building blocks for evolution to play with the more impressive the final results are.  Codules, again, let bots build up code reuse so it's entirely possible for things like storeadd to evolve on their own just by happenstance.  Or other, weirder DNA shortcuts.

Or that's the thinking anyway.  I haven't played with it in a long while; I'll revisit it at some point and finish flushing out the language once I have a chance to play with it in practice.

[Botsareus]

I get it. Robots can evolve there own Codules.

[spike43884]

Oooh. A nice little command to add for DB3:
.mygenefired

This will check if X (X being the value you put before .mygenefired store) was active in the previous cycle, it will return 1 if true, 0 if false!