Embedded programming standards don't have statements like:
Quote
would it not be suitable if users of the code are made fully aware of the behavior.
Agreed, they probably don't. But what they should have is technical documentation specifying all the client needs to know. Reading the documentation is hopefully part of most design standards, certainly in mine anyway. I assume you are pointing out that this expectation isn't always met on large scale systems or projects involving many people.
And as much as I want to argue I guess I can't overcome the fact that someone will eventually skip the important information, causing a bad day.
I'll download libre office so I can view that doc. Might be some good insights in there.