Learn Programming
Resources specific to my own learning journey.
Learn Programming
Garbage collection uses a variety of algorithms; the Java virtual machine architecture doesn’t require a particular scheme.
Link
Java needs a garbage collector, but like an application calling an API, it only needs the services of a GC, not a specific implementation of one.
The static members of a class are initialized when the class is first loaded into the virtual machine.
Link
A constructor can invoke another overloaded constructor in its class using the self-referential method call this() with appropriate arguments to select the desired constructor. If a constructor calls another constructor, it must do so as its first statement
Link
What a wild and interesting behavior. I wonder why it was believed to be necessary.
Collections work only with object types, so primitives must be wrapped when stored in them.
Link
All primitive types in Java need wrappers to be put into collections. Only reason I haven’t noticed any other than ints is that ints and Strings are the only ones I tend to try.
you can add a bit of formatting to your numeric literals by utilizing the “_” (underscore) character between digits.
Link
Purely for legibility of large numbers or fp-numbers with large number of decimal digits.
numeric types default to the appropriate flavor of zero, characters are set to the null character ( \0 ), and boolean variables have the value false
Article
Member variables of a class are initialized to default values, but not variables declared within methods, conditional blocks, or loops.
Integer literals are of type int unless they are suffixed with an L , denoting that they are to be produced as a long value
Link
Seems a bit silly that you can declare the variable as a long and the compiler happily ignores that when first evaluating the literal.
if you want to ensure that your application produces exactly the same results on different platforms, you can use the special keyword strictfp as a class modifier on the class containing the floating-point manipulation
Link
Tells compiler to stick to IEEE 754 standard.
An important portability feature of Java is that primitive types are precisely defined. For example, you never have to worry about the size of an int on a particular platform; it’s always a 32-bit, signed number.
Link
Seems like they’re locking themselves in but I suppose numbers for daily use may rarely reach beyond that limit.