Question

How could I prove class loading take places only once in Java? Is it a pseudo-proposition?

Answer 1

According to the Blackwell Dictionary of Western Philosophy, a “pseudo-proposition” is as follows:

A term introduced by Wittgenstein in the Tractatus, referring to any judgment that attempts to say that which can only be shown. Unlike other propositions, pseudo-propositions can not be analyzed into atomic pictures and their combinations and therefore they are not pictures of the world. Wittgenstein thinks that in different ways the propositions of logic, mathematics, the a priori parts of natural science, ethics, and philosophy – including the propositions of his own Tractatus – are all pseudo-propositions. Logical positivists develop this idea in their attack on metaphysics by saying that all propositions and statements that purport to make a factual claim but which can not be verified by experience are pseudo-propositions. They have emotional significance, but lack cognitive meaning. There are many attempts to retrieve at least some of the fields discarded in this way by logical positivism. “The propositions of mathematics are equations, and therefore pseudo-propositions.” Wittgenstein, Tractatus

If you are using “pseudo-proposition” in this sense, then your proposition is a pseudo-proposition even if we could develop a mathematical proof for it, since according to Wittgenstein all of mathematics is a pseudo-proposition. If is impossible to verify by observation that the proposition “class loading takes place only once” is always true.

But to me, this is only saying that the label “pseudo-proposition” is not a useful one when we are talking about IT topics. And that someone who uses it in this context either doesn’t really understand the term, or is posturing.

I doubt that it is (even) possible to mathematically prove that a class is loaded only once, because you’d have to prove this for any (theoretically) possible class loader. But frankly, who cares! I’m happy to just declare that any class loader that allows a class to be loaded multiple times is broken.

(In fact, if you have multiple class loaders, it is possible to load the same bytecode file once in each class loader. But what you get from the perspective of the Java execution model is different classes with the same name.)