Yes, I know this breaks the API. On the other hand we have been breaking the API all the time. This is one of the very few
commits thats *says* it breaks the API.

I think this is a serious API bug, but maybe we should really clean up and call it 2.0. This is just one of many serious issues with the API.