Analysis:
Analysis
z,P, (arithmetic operator): Terribly hard to analyze. UsingzP|results in the solution above.z,P, (arithmetic operator): Terribly hard to analyze. UsingzP|results in the solution above.Some specific cases:
+,-: Should be possible. Analysis pending.vand~: This can only decrease the value on the top of the stack without reducing the stack depth, so I think it's impossible.%: Equivalent tooin this particular case, becausex%(x+1)==x./: Obviously impossible becausex/(x+1)==0andx/0raises an error.|: Possible. (this also decrease the stack depth by 2 each time instead of 1) Used in this answer.*and^: Because there can only a limited number of possible results, I'm not very sure this is useful.
Note that "impossible" means "impossible to do efficiently", because
zPalone is sufficient.
Note that "impossible" means "impossible to do efficiently", because zP alone is sufficient.
z,P,o(since the output radix is not used, it's the same as pop the stack and do nothing in this challenge): 1601 bytes (obviously optimal).z,P,o(since the output radix is not used, it's the same as pop the stack and do nothing in this challenge): 1601 bytes (obviously optimal).