Tom Helmuth

I didn't fully digest all of the details, but this looks cool to me. I like the idea of the enumerator stack. It always felt a little scary to me...

Nope. The only current way that I'm aware of is to just add it to that list of stack types.

Definitely looking like a good start! A few comments: - Can you add a comment for each instruction describing what it should do? It's hard to tell if an instruction...

> Do you know if there is room inside define-registered for a docstring? I don't know! You could always try and see if anything breaks. > I will also add...

Was that last comment supposed to go in #153?

> Do you want to permit "looping" behavior? I'm guessing this would be a boolean flag, settable by a toggle instruction, which when true would permit the Enumerator to "wrap"...

> While we're discussing things: as I've mentioned, this isn't my first go on the Enumerator ride. One set of instructions (from push-forth I think) I had sort of set...

> I notice a lot of the instruction names are pretty long. Can I get away with renaming them enum_thingie rather than enumerator_thingie, or is the naming standard to always...

> Later: Yeah, no; I'm going to need some explicit help from somebody telling me how to set up pushgp to actually use We generally use `:use` instead of `:require`....

Some questions: - Is there any instruction that gets the item at the current pointer location -- something like `enumerator_next` without moving the pointer? Maybe I'm missing it, or maybe...