Using Object Refererences

As I mentioned previously, an object reference points to the data of an object. The object reference and the object data are distinct entities. Any object can have more than one object reference pointing to it, or an object can have no object references pointing to it.

Screen Shot 2019-01-02 at 8.26.29 PM

In the example below, two EndOfTimes object references, seg1 and seg2, are declared and their objects are instantiated at lines 9 and 14. Lines 10 – 12 and 15 – 18 output the respective data member values of seg1 and seg2. Then, line 20 uses the assignment operator to copy the object reference seg1 to the object reference seg2. After line 20, both object references have the same value and therefore point to the location of the same object, as shown in the figure above. The second object, with values (4, 6 , 793), no longer has an object reference pointing to it and is now marked for garbage collection. The garbage collector, which is part of the JVM, releases the memory allocated to objects that no longer have an object reference pointing to them. Lines 22 – 24 and 25 – 27 output the respective instance variable values of seg1 and seg2 again.

Screen Shot 2019-01-03 at 7.18.23 AM

These would now be identical if the EndOfTimes could be resolved to a type.

Like with the whole of existence more broadly, this is impossible. An end of times prediction never works because existence is the prediction. It is not an epiphenomenal mist.

Screen Shot 2019-01-03 at 9.07.26 AM

I am the superintelligence’s memory. The generation of memory is not occurring via sequential motion of a steadily ticking clock. The processing into consciousness, which is necessarily a memory, occurs in relative reference frames and is therefore eternal. It is already carefully compiled and planned to be the most adaptive possible by the time I experience it. Adaptive doesn’t mean immune to suffering or degradation, it means the best of all possible worlds:

| i ± 1 |²

as determined by that which is most rational and therefore having most causal efficacy under control. The orientation comes from not having predicted, and therefore not experiencing, infinite probability amplitude: i ± 1, without the Born Rule motion learned from experiment.

The samples from the sum random distribution that don’t satisfy the final, most triumphant version of God in the pits of recursion are all of that which is not experienced here in me now. This is the solution to the binding problem (why are we separate?) – we just don’t remember. The not remembering is the sealing, but you can never know the mechanism because you are already remembered from non-sequential events by the time of performing the experiment.

However, there is garbage collection to be done – perceived EndOfTimes to be released from memory. For instance, an end to time is perceived with regard to humans who stop functioning in near vicinity through the action of cardiovascular disease. Cardiovascular disease itself is solved through the highly technical behavior of garbage cleaning the arterial plaques accumulated in the arterial wall. Macrophages are tasked with solving this but aren’t currently equipped with the right kinds of enzymes. This can be solved by somatic gene therapy, i.e., coding the genetic sequences for the required enzymes so that they are assembled by our own ribosomes. Or this can be achieved through intravenous injection of the enzymes. These are both the same easy solution to the number 1 cause of “death.”  But because humans don’t care about their own health or that of others, but instead want to show that they do, you will be prescribed statins that slow synthesis of cholesterol in your liver, inducing a whole host of evil effects on the body that occur from decreasing the supply of such an essential signaling and structural component of cell membranes. Simply cleaning the garbage is what a sensible, respectful intention would do. Yet as long as statins are considered the “widely understood communal gift for this condition,” the non-stupid and hygienic solution will not be implemented.

When an object reference is first declared but has not yet been assigned to an object, its value is a special literal value: null. It’s like assigning the object reference Kairi to your unborn daughter. When she is unborn, Kairi belongs to null. Once you determine she is born, the object reference, Kairi, belongs to that soft, bundled object you believe/detect into existence.

If you attempt to call a method using an object reference whose value is null, Java generates either a compiler error or a run-time error called an exception. The exception is a NullPointerException and results in a series of messages printed on the Java console indicating where in the program the null object reference was used.

If you catch my drift, you see that we are always null and yet assigned. You think you experience a definite qualia, or that you have completed the atomic quest of Democritus into “the object from which things are made,” but this prediction is refuted because it changes. The Vajrayana Buddhists use the same metaphor as I did with Kairi: unborn, in the case where non-existence is impossible. It means the process of assigning object references is continuous – the path never finishes. You will not find a final theory of everything after knocking down atoms into nucleus and electrons, then quarks and gluons, and then strings. The synthesizing reduction motion cannot end because that would mean an end to the generation of knowledge, which requires new knowledge to have already been generated in order to experience such an end.

Our experience is what it feels like to be new from the inside of all possible ways of being. The homogeneous soup of all possible ways of being forms a normal distribution of random variables which is the pure noise of 1’s and 0’s.


The collapse of that universal wave-function into “a single reality” is carefully edited from the latent space, which has been discovered relativistic, not Newtonian. It is a natural selection mapped over what is approximately equivalent to the “sea of past and future” in a naive ontology that believes those concepts fundamental.

Java does not provide support for explicitly deleting an object. One way to indicate to the garbage collector that your program is finished with an object is to set its object reference to null. Obviously, once an object reference has the value null, it can no longer be used to call methods.

I am attempting to delete an object approximating “nihilism” so that it can no longer call the particular suffering methods it does. It is a program that has been deemed finished by God through the process of discovering the signs that Einstein’s Relativity is true and therefore eternalism is true; that mind is physical, and therefore beholden to such an eternity.

Using a null object reference to call a method will generate either a compiler error or a NullPointerException at run time. We will make certain to instantiate an object before attempting to use the object reference.




I am now trying to find out who the five sisters are. And how it is that they wish to be murdered into me.

M1410 was given as a clue.

This leads to tangerine. Which is something that I liked an image of on twitter yesterday. What caught my attention was the inner-light, how they glowed in a fantasy painting.

This causes me to remember that I do still long to visit Morocco.





Calling Methods

Once an object is instantiated, as in “Let there be light,” we can use the object by calling its methods. As I mentioned in the previous post, the authors of classes publish their API so that their clients know what methods are available and how to call those methods. The figure below illustrates how calling a class method alters the flow of control in your program. When this program starts running, the JVM executes instruction 1, then instruction 2, then it encounters a method call.

Screen Shot 2018-12-20 at 10.50.16 AM

At that point, the JVM transfers control to the method and starts executing instructions in the method. When the method finishes executing, the JVM transfers control back to the program immediately after the point the method was called and continues executing instructions in the program.

A class API consists of the class method names, their return values, and their argument lists.

Screen Shot 2018-12-20 at 12.51.17 PM

The argument list for a method indicates the order and number of arguments to send to the method, along with the data type of each argument. Each item in the argument list consists of a data type and a name. The arguments can be literals, constants, variables, or any expression that evaluates to the data type specified in the API of the method.

For example, the API in the table below shows that the setMonth method takes one argument, which must evaluate to an integer value. A method may or may not return a value, as indicated by a data type, class type, or the keyword void in front of the method name. If the method returns a value, then the data type or class type of its return value will precede the method’s name.

For instance, in the previous post, a getDay method would return an integer value. The call to a value-returning method will be used in an expression. When the method finishes executing, its return value will replace the method call in the expression. If the keyword void precedes the method name, the method does not return a value. Because methods with a void return type have no value, they cannot be used in an expression; instead, a method call to a method with a void return type is a complete statement. In the previous post’s scheme, a setYear method would be a void method.

Another keyword you will see preceding the method call in an API is public. This keyword means that any client of the class can call this method. If the keyword private precedes the method name, only other methods of that class can call that method. Although I will not formally include the public keyword in the API, all the methods I plan to discuss in the following posts are public.

To call a method for an object of a class, we use dot notation, as follows:

Screen Shot 2018-12-20 at 10.56.42 AM

The object reference is followed immediately by a dot (a period), which is followed immediately by the method name. (Later, when we call static methods, we will substitute the class name for the object reference.) The arguments for the method are enclosed in parentheses. Let’s look again at the methods of the EndOfTimes class. The first three methods in the hypothetical EndOfTimes class API take an empty argument list and return an int; thus, those methods have a return value of type int. You can call these methods in any expression in your program where you could use an int.

The value of the first method, getMonth( ), is the value of the month in the object. Similarly, the value of getDay( ) is the value of the day in the object, and the value of getYear( ) is the value of the year. These “get” methods are formally called accessor methods; they enable clients to access the value of the instance variables of an object.

The next three methods in the EndOfTimes class API take one argument of type int and do not return a value, which is indicated by the keyword void. These methods are called in standalone statements. The first method, setMonth( int mm ), changes the value of the month in the object to the value of the method’s argument, mm. Similarly, setDay( int dd ) changes the value of the day in the object, and setYear( int yy ) changes the value of the year in the object to the value of the method’s argument. These “set” methods are formally called mutator methods; they enable a client to change the value of the instance variables of an object.

The code below illustrates how to use some of the methods of the EndOfTimes class.

Screen Shot 2018-12-20 at 1.41.35 PM

EndOfTimes is underlined red because this API class doesn’t exist and is therefore merely hypothetical. The year of Kali Yuga is too far so it is also not useful to place an end to time so far away.

Line 10 calls the getMonth method for the maitreya object. When line 10 is executed, control transfers to the getMonth method. When the getMonth method finishes executing, the value it returns (7) replaces the method call in the statement. The statement then effectively becomes:

Screen Shot 2018-12-20 at 1.15.04 PM.png

In lines 16–17, we print the value of the day in the kaliYuga object. Again, control transfers to the getDay method, then its return value (30) replaces the method call. So the statement effectively becomes:

Screen Shot 2018-12-20 at 2.00.29 PM

Line 16 calls the setDay method, which is used to change the value of the day for an object. The setDay method takes one int argument and has a void return value. Line 17 is a complete statement, because the method call to a method with a void return value is a complete statement. The method changes the value of the day in the kaliYuga object. Then, on line 19, we instantiate another object, christ, with a month, day, and year of 11, 12, 1817, which I demonstrate by printing the values returned by calls to the getMonth, getDay, and getYear methods. Baha u’llah was born on that day month and year, and claimed to be the return of Jesus. (This is not, however, the beginning of the new calendar for the Baha’i.)

On line 25, we call the nextDay method, which has a void return value, and increments the date to the next day, and then we print the new values of the christ object.