Break OO privacy: Difference between revisions

Ecstasy security is accomplished by the use of <i>software containers</i>. Code running in a container is always allowed reveal any legal type on any object created within that container, including any object created within sub-containers. However, the runtime will reject any reveal request on any object that was <i>not</i> created within that container.

<syntaxhighlight lang="java">

/**

* This is a class with public, protected, and private properties.

*/

public String pub = "public";

protected String pro = "protected";

 

@Override

return $"pub={pub.quoted()}, pro={pro.quoted()}, pri={pri.quoted()}";

}

 

@Inject Console console;

 

 

console.print($"after: {expo}");

}

</syntaxhighlight>

 

 

However, there is no such thing as a private method. Although conventionally methods which are not intended to be called from outside the class are suffixed with an underscore, this doesn't prevent anyone from accessing them as the following example shows.

construct new() { _safe = 42 } // the field _safe is private

safe { _safe } // provides public access to field

84

</pre>

=={{header|zkl}}==

In zkl, privacy is more convention than enforced (unlike const or protected).

{{omit from|x86 Assembly}}

{{omit from|Z80 Assembly}}

{{omit from|ZX Spectrum Basic}}