Comment 3 for bug 1187693

Thanks! Am I missing some documentation of this behaviour somewhere, or is it really only documented in the code and in a printed warning on execution? It seems to me that it is essential that this should be documented, because it's an interaction that one wouldn't expect. Is this a separate bug?