MAPADDRESS result can mix status codes
When using MAPADDRESS at the control port, mixing valid and invalid address mappings can result in a mixture of status codes, contrary to Section 2.3, which says:
Multiple lines in a single reply from Tor to the controller are guaranteed to share the same status code.
mapaddress xxx=@@@ 0.0.0.0=bogus1.google.com 512-syntax error: invalid address '@@@' 250 127.199.80.246=bogus1.google.com
It's not clear what the right thing to do here is. Checking the syntax first might help, but maybe it's possible to run into resource exhaustion for some requested mappings and not others?