Hi Fabio,

>This is the master point!
>If a behavior is strange or illogical, and nothing is written on the documentation, then:
>- or it is a program bug;
>- or it is a out of design bug;
>- or is a document bug
>- or it is one characteristic forced from the rest, but it must be explained the reason, enough not to say what do only,
>otherwise i call it a design bug.
>
I concur. Since I didn't read all of the *current* docs it might be a "nowadays" doc bug (description not included in current version). And even if a reference to the behaviour (pun intended) is included in the current doc, it is not as plainly visible as it should be described.

regards

thomas