This lesson ventures into interesting uncharted territory.
Until now, our class
es have needed to have names.
But Kotlin doesn’t actually require this!
Let’s explore anonymous classes and their uses…
Please note that the next two lessons are on fairly advanced topics. You will see and need to understand code that uses these ideas, but testing on them will be limited.
But… hold on! Let’s warm up with another graded debugging challenge!
We’ve seen how to define what is called a named class. This should be familiar to us by now:
However, Kotlin also allows us to define so-called anonymous classes. Let’s go through an example carefully:
In contrast to named classes, anonymous classes:
class
or implement an interface
Anonymous classes can capture the value of variables that are available when they are created. This can be extremely useful, even if the results are a bit spooky. Let’s look at an example:
We can create anonymous classes in Kotlin. Cool! But… so what!? What problems can these classes solve?
Surprisingly, anonymous classes turn out to be common and quite powerful. Let’s look at an example.
Imagine that we want to count the number of elements in an array of Int
s that meet some condition.
The condition could be that the element was positive, or negative, or odd, or even, or divisible by three, or whatever.
One approach would be to write separate methods for each thing we would want to count:
Wow, this is getting tedious—and we’ve only done three! Imagine if we had a bunch of different conditions we needed to handle… But they are all very similar. There must be a better way.
Let’s see how to rewrite the code above using an anonymous class in a way that makes the counting logic completely flexible.
Declare a method create
.
create
takes a single Int
parameter and returns an anonymous object that implements the Bracket
interface:
The returned object should implement top
so that it returns the passed Int
and bottom
so that it returns the
passed Int
* -1.
So, for example:
Declare a method create
.
create
takes a single String
parameter and returns an anonymous object that implements the IBothWays
interface:
So, for example:
Create a method named create
that accepts a Position
object and returns an anonymous object that implements
the IWhichHemisphere
interface:
The return values of isNorthern
and isSouthern
are determined by the latitude value on the passed Position
object, which you can retrieve as a Double
latitude
property.
Here's how your class should work:
However, note that the latitude values of the passed Position
object can change after it is passed to your
method!
So you should not precompute the results of isNorthern
and isSouthern
, but rather calculate them in your
anonymous class when the corresponding methods are called.
We define any position with a positive latitude as being in the Northern Hemisphere, and with a negative latitude as being in the Southern Hemisphere. Meaning, for the purposes of this problem, points on the equator are in neither hemisphere.
Shoshana Zuboff is an author and professor at the Harvard Business School, where she was the first tenured female professor. She may be best known for coining the term “surveillance capitalism”, and for her book “The Age of Surveillance Capitalism”, which outlines a global system of behavioral modification based on the collection and mining of data about our private lives.
In the short video below Shoshana Zuboff defines surveillance capitalism and discusses how it mirrors and differs from previous eras of capitalism:
Need more practice? Head over to the practice page.