Code center > Suggestions

Genome structure

<< < (5/5)

Sprotiel:

--- Quote from: MacadamiaNuts ---It isn't the store the one picking the value, but the start.

So, when the last number in the normal stack is a true value, as it would result from a condition operation, the following start activates. Stores wouldn't change at all in this last suggestion.

It's so a small change it at least could be an option...
--- End quote ---

Removing the condition stack is not a small change, but I think it's worth considering.

Your proposal isn't totally clear so here is a detailed proposition of implementation:
* cond stack is removed, bots only use the integer stack
* tests output 1 for true and 0 for false
* for flow commands, 0 means false and everything else means true. The first 'start' command after a 'cond' sets a flag that's used by subsequent 'start' and  'else' to decide if the corresponding blocks of code are executed.
* logic functions behave as 'cond' for input and as tests for outputThere's one problem with this, though. It becomes impossible to automatically and together all conditions when a 'start' is executed, which breaks backward compatibility.

Endy:
Ran into an interesting site here: Evolving Evolution about the idea of evolving the interpreted dna language itself. Essentially it'd be a contest between the evolvable languages themselves.

It might even be possible to have the bots do this themselves, perhaps with some sort of dna interpretation operators. Would have to be limited in scope somehow, since any change could have dramatic effects on how their own dna is interpreted. That would be the true goal, life evolving it's own evolvability.

Navigation

[0] Message Index

[*] Previous page