CORBA3 — name disambiguation for AMI interface & poller names is confusing

The rule for generating a unique AMI_ callback or poller name is to
stuff additional "AMI_" strings until the name is unique. However,
consider the following IDL:

// IDL
module M {

interface A {
};

interface AMI_A {
};

};

this apparently maps to the implied IDL:

// implied IDL
module M {

interface A {
};

interface AMI_AMI_A

;

interface AMI_A {
};

interface AMI_AMI_AMI_A

;
};

however, if I switch the order of declaration of A and AMI_A, the names
of the associated callback interfaces change.

Not only that, but if I split the IDL into two files:

// File 1
module M {

interface A {
};
};

// File 2
module M {
interface AMI_A {
};

};

and try to compile them separately, the generated code will fail.

I don't think there is any solution to this problem other than to
declare it an error to use an IDL identifier that begins with "AMI_" if
it causes a name clash.

The same problem applies to the AMI poller valuetypes.

Resolution: Insert the requirement that any IDL that is meant to be used for AMI should not have any