Break OO privacy: Difference between revisions
Content added Content deleted
m (→{{header|J}}) |
|||
| Line 548: | Line 548: | ||
Current implementations of J do not enforce OO privacy, instead favoring design techniques (such as functional programming) which eliminate private information in persistent contexts. |
Current implementations of J do not enforce OO privacy, instead favoring design techniques (such as functional programming) which eliminate private information in persistent contexts. |
||
It's possible to use OS features (such as other processes, and servers) to hide information. But that, by definition, is outside the scope of the language. |
It's possible to use OS features (such as other processes, and servers) to hide information. But that, by definition, is outside the scope of the language. |
||
J does support a "[http://www.jsoftware.com/help/dictionary/dx003.htm Lock Script]" mechanism - to transform a J script so that it's unreadable. However, (a) anyone with access to a machine running the code and ordinary developer tools or who understands the "locking" technique could unlock it, while (b) a large volume of programmers consider J to already be unreadable. |
|||
=={{header|Java}}== |
=={{header|Java}}== |
||