- Some parts of Pxem is very ambiguous and we need to make clarified and extended version.
- Original one used not to tell from uppercases and lowercases when it is next to dots, but we must tell them clearly.
- .p, .o, .n are too ambiguous because it isn't shown whether it should output newlines or shouldn't. What about this: lowercase ones do while uppercase ones don't.
- We are not really sure what to do if your stack has only an element while getting conditional commands which requires two elements.
- Should we get to corresponding .a or not?
- Must we throw the only remaining element away?
Announcement:I'm fixing the article.
About unclear conditional looping instructions.
Original manual said what if the stack has inadequate item(s) when the pointer finds .w, .x, .y, and .z: it just described not to test the condition. The new blog just describes that the items never lost in those case.
And today I realized the original manual showed examples what begins with ak.-.z. It seems to imply that never will it skip to matching .a if inadequate items. --YamTokTpaFa (talk) 15:21, 10 September 2019 (UTC)
This language should be one of deque languages
Look at a command .v; it reverses entire content of stack. This feature, actually, lets you to use stack as a deque, too! So, the true data structure is deque, I think.--YamTokTpaFa (talk) 05:30, 15 September 2019 (UTC)
- I think it is stack based, because the other side is relatively hard to access without reversing the stack. --àÂse ëË y± comme×s! (Please sign your comments!) A (taÑ) 02:16, 3 August 2019 (UTC) 12:25, 15 September 2019 (UTC)