quote:
Originally posted by Gigalith:
<STRONG>This idea just came to me. An elephant-powered calculator.Here's an elephant-powered AND gate:
code:
######
#!#!b#
#A#a.#
#B#..#
#1#0##
#^#^##
#.#.##
....##
######
In this example, !s are cages with (untamed) elephants inside them, which are connected to a (far-off) lever. 0 and 1 are pressure plates which act as output. The ^ is a cage trap so you can recycle your elephants.</STRONG>
Maybe I'm misunderstanding. But I think that there are actually serious problems with this scheme.
It seems to give the results:
A and B = 1 and 0
A and (not B) = 0
(not A) and B = 0
(not A) and (not B) = (no result)
There are two problems here:
First of all, "(no result)". This is actually a major issue, believe it or not. You can't simply state that (no result) is equivalent to the zero pressure plate, because you cannot categorically state that just because no result has occurred, no result will occur. The elephants could just be taking their sweet time, and there is no finite amount of time within which you can guarantee they will get around to the plate.
So, unless you are preassuming knowledge to the answer of "(not A) and (not B)", this machine will never allow the dwarves to figure out that question.
Second of all, the fact that "A and B" triggers both the 0 and the 1 pressure plate. This is an issue for more or less the same reason that (no result) is an issue: Just because the zero plate has been triggered, and the one plate has not been triggered, you cannot definitively state that the one plate will not be triggered. Within any timeframe.
So, similarly to "(not A) and (not B)", the dwarves will never be able to know the answers to "A and (not B)" and "(not A) and B".
The only question that your machine can definitively answer is "A and B", and it's not even guaranteed to do that in any finite amount of time.
I'm sorry if it's seeming like I'm being a stickler, or a jerk, or whatever -- I admit I'm being the former, but I don't mean to be the latter -- I just am genuinely enjoying this thread, and would like to see it really solved.
Edit: Did this instead of this.
[ December 07, 2006: Message edited by: w ]
[ December 07, 2006: Message edited by: w ]