Amount of .class files created

[Lowest0ne]

I have a linked list:

public class SortedLinkedList<E extends Comparable<E>>
{
  private class Node<E>
  {
    Node(E d) {data = d; next = null; prev = null;}
  }
  protected class Iterator<E>{}
}

Which when compiled, I get three .class files:

SortedLinkedList.class
SortedLinkedList&Node.class
SortedLinkedList&Iterator.class

Now I am working on member access (friend/protected/private), and I've changed the Node's constructor to private:

public class SortedLinkedList<E extends Comparable<E>>
{
  private class Node<E>
  {
    private Node(E d) {data = d; next = null; prev = null;}
  }
  protected class Iterator<E>{  }
}

A little odd to me that the program still compiles (1.7.0), but I am given a fourth .class:

SortedLinkedList$1.class

Why is this? Thanks.

[DarrylBurke]

Moved from New to Java

db

[Tolls]

Don't see why the program shouldn't compile.
There's nothing there that would prevent it.

The extra class is a bit of a mystery, though.

[Lowest0ne]

~What an honor to be moved out of beginners :). I had my head shrunk later that day, no worries. ~

There's nothing there that would prevent it.

I just figured the SortedLinkedList wouldn't have access to the Node's constructor.

Just did a little testing on an updated list:

// Needed code only
public class SortedLinkedList<E extends Comparable<E>, F>
{
  private class Node<E extends Comparable<E>, F>
  {
    private Node(E k, F d){}  
    private Node(Node<E, F> other){}
  }
}

Two constructors, maybe I would get a "SortedLinkedList&2.class" or something like that? Nope, still only &1.

I did delete the &1, and the program still runs correctly (the way I've implemented it, at least)

As a side, I just did this (removed the typed parameters from Node):

public class SortedLinkedList<E extends Comparable<E>, F>
{
  private class Node
  {
    E key;
    F data;
  }
}

Seems to be working fine?

[Tolls]

I just figured the SortedLinkedList wouldn't have access to the Node's constructor.

The 'private' is to do with stuff accessing from outside of the outer class, not child classes, so in this case another class could not create a Node.
But Node is a part of a SortedLinkedList, as much as any member variable or method, so SortedLinkedList can execute private methods/constructors and access private attributes.
To be honest, since the Node class is 'private' itself, the declaration of the constructors as 'private' will have no practical effect. Nothing outside of SortedLinkedList could access it anyway.

Just did a little testing on an updated list:

// Needed code only
public class SortedLinkedList<E extends Comparable<E>, F>
{
  private class Node<E extends Comparable<E>, F>
  {
    private Node(E k, F d){}  
    private Node(Node<E, F> other){}
  }
}

Two constructors, maybe I would get a "SortedLinkedList&2.class" or something like that? Nope, still only &1.

I did delete the &1, and the program still runs correctly (the way I've implemented it, at least)

I expect something would turn up, though it is possible it's a compiler curiosity.

As a side, I just did this (removed the typed parameters from Node):

public class SortedLinkedList<E extends Comparable<E>, F>
{
  private class Node
  {
    E key;
    F data;
  }
}

Seems to be working fine?

Node is part of SortedLinkedList, so it has "access" to the same things, including what generics are being applied.