[MERGE] Fix for bug 183831

[Stephen J. Turnbull]

Very nice reply.  You (or somebody ;-) should consider reformatting it
as an "Advice to new developers" kind of document.  Even though people
will disagree in any given instance about how to apply it, it sets out
the meaning and consequences of "layering violation" very clearly.

Aaron Bentley writes:
 > Geoff Bache wrote:

 > > I think we've hit the crux now.
 > 
 > I raised that back on April 4:
 > 
 > >> Isn't the fact that it fixes this issue enough for it to be "better"...?
 > > 
 > > When you're talking about changing the behaviour of a low-level function
 > > in order to achieve a high-level effect, no it's not.