Checks for protected elements

[Martin Sjölund]

We currently allow access of protected elements that should not be possible to access. This is very important for bootstrapping since dependency analysis depends on protected elements not being part of the interface of an encapsulated package.

encapsulated package P
protected
  constant Real c = 1.0;
  function f output Real c = 1.0; end f;
end P;

encapsulated model M
  import P;
  Real r1 = P.c; // illegal
  Real r2 = P.f(); // illegal
end M;

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

As of v1.13.0-dev-188-g2c5818d with -d=newInst, the access to P.c is correctly detected as illegal. However the following model

encapsulated model M
  import P;
  // Real r1 = P.c; // illegal
  Real r2 = P.f(); // illegal
end M;

fails with error messages which seem related to an incomplete implementation of functions in the new front-end, but not because of attemped access to a protected element.

[Per Östlund]

Fixed in 691f4e9.

[Jan Kokert]

Just a shot follow-up: Is ticket #4346 related with this one? Thanks!

[Per Östlund]

Replying to janK:

Just a shot follow-up: Is ticket #4346 related with this one? Thanks!

Not really, that looks like a separate issue.