Talk:PoGo

[ and ] become a complicated and probably very arbitary mess of po's and go's and some other things

It looks like you have yet to define an isomorphism reduction. —ehird 03:00, 29 June 2011 (UTC)

The issue is that the way of directing program is fundamentally different, and it's difficult to come up with an all-purpose exact correlation (not saying there isn't one, but I haven't written an implementation yet so this is hard to determine), but the jumping is there and the nested jumping is there and the conditions are there; it's all obviously possible, just, as I said, different. - Madk 13:01, 29 June 2011 (UTC)

Sure, but it is not yet a reduction. :) —ehird 03:42, 29 June 2011 (UTC)

This is how it would work

po os en en en en en en en en en en en en en os as op
po ok ad op ow ow un go ni go no
(do stuff)
to go no

for every additional command in (do stuff) one more 'en' would need to be added in the first line. This example should reproduce the exact behavior of a Brainfuck [] loop. And just to be totally clear, this is the equivalent of [-].

po os en en en en en en en en en en en en en en os as op
po ok ad op ow ow un go ni go no
de
to go no

- Madk 13:01, 29 June 2011 (UTC)

Colourful?

What's ow an go meant to be, anyway? —ehird 03:46, 29 June 2011 (UTC)

ignore the o's - Madk 13:01, 29 June 2011 (UTC)