OK, fixed the =null ambiguity.

I didn't add 'deprecated' because the argumentless toString() currently still forwards to the old toString(). I guess what I really wanted to do, was to completely get rid of the old toString, and write a proper version of the argumentless toString() in its place. Do you think it's safe to just delete the old code? I highly doubt anyone actually uses that convoluted interface.