I place a command block and give it this command:

/testfor @p[x=180,y=56,z=22=,r=10]

I connect a comparator to the command block(comparing mode) it remains "false" until power is connected. Once a redstone clock is connected the comparator outputs a "true" signal even when a player is not anywhere near the coordinates and the signal is constantly being refreshed by the clock. When the clock is deactivated the comparator still remains powered unless the command block is removed. It also becomes powered even if the previous result was false.

However when the command is changed to:

/testfor @a[r=10]

the command block is connected to the clock the comparator issues true/false commands when the player is within that radius as normal. I feel like other players have mentioned this a lot but been ignored because their complaints were rather vaguely worded. Any help would be wonderful, thank you.