User Tools

Site Tools


inner_classfiles_naming

This is an old revision of the document!


From the beginning of the inception of inner classes in Java, developers knew that it would be a mess… and it had been proven again and again. Here is a most recent example. Take the following (academic) piece of code:

public class Anonymous {
	public void foo() {
		class B {}
		new B();
	}
}

On both MacOS Windows, there are two files generated… BUT, these two files have different names, thus throwing on the ground some of the dedicated PADL tests (in particular in PADL Creator ClassFile Tests)

  • On MacOS
    • Anonymous.class
    • Anonymous$1B.class
  • On Windows
    • Anonymous.class
    • Anonymous$1$B.class
inner_classfiles_naming.1384328260.txt.gz · Last modified: 2017/09/06 01:54 (external edit)