[sv-bc] package vs packge ; package vs module override issues

I've doubts what should be the bahaviour in below cases:
 
 
ISSUE 111111111111111111111111111111:
1st compilation unit:
    package p;
        int a=1;
    endpackage
2st compilation unit
    package p;
        int a=2;
    endmodule

Above packages compiled in single compilation - is clearly for me tool
dependend, but compiled as shown above? should it behave the same module
overriden in separate compaltion- i mean package defined in 2nd compilation
will override 1st one in whole design?
 
ISSUE 222222222222222222222222222222:
This issue is much more interesting. Package and module cannot be used in
the same cotext because its nature is different - so maybe it should be
allowed in common and separate compilation units - and in both cases both
package p and module p should exist in desing?
package p;
int a=1;
endpackage
 
module p;
int a=2;
initial $display(p.a, p::a);
endmodule

 
ISSUE 333333333333333333333333333333333:
what about overriding std package - with user defined module or package with
"std" name? rules should be the same as in above cases?
so defining package std; should override predefined std package which will
be no longer avaible?

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.