Changement de DD après mort cérébrale du DD d’origine. Modèle du nouveau WD de 500 GB. Ai suivi les tutorials mais impossible de remettre le nouveau disque dans le logement après avoir démonté et remonté sur son support. Crainte de tout abîmer…et que sont les languettes dont parlent certains ? Je ne vois que la languette blanche du compartiment du DD. Merci à tous

class Foo {

private final Map numbers = new HashMap();
{
numbers.put( “one”, 1 );
numbers.put( “two”, 2 );
numbers.put( “three”, 3 );
}

private final List days = new ArrayList( 7 );
{
days.put( “Sunday” );
days.put( “Monday” );
days.put( “Tuesday” );
days.put( “Wednesday” );
days.put( “Thursday” );
days.put( “Friday” );
days.put ( “Saturday” );
}

}

is more readable than a cluttered constructor like that:

class Foo {

private final Map numbers = new HashMap();

private final List days = new ArrayList();

public Example() {

numbers.put( “one”, 1 );
numbers.put( “two”, 2 );
numbers.put( “three”, 3 );

days.put( “Sunday” );
days.put( “Monday” );
days.put( “Tuesday” );
days.put( “Wednesday” );
days.put( “Thursday” );
days.put( “Friday” );
days.put ( “Saturday” );

}

}

This is also an elegant way to share common initialization code between multiple constructors when they cannot call each other.

Apart this, and for anonymous classes initialization like in your example, I do not see any other added value.

Using initialization blocks, is exactly the same thing than putting the corresponding code at the begining of the constructor (the compiler generates a copy of corresponding bytecode at this place).

There actually seems to be a caching behaviour under the hood, just like
integers if I’m right. Well, more like reusing unused instances instead of gc
them and re instantiate, as you suggested. But as you know, I’m not a Java
expert