In terms of scalability would be wiser to make an object from the concrete class or the interface?

Question

For example instead of:

LinkedStack<Integer> list = new LinkedStack<Integer>();

Should be this:

StackInterface<Integer> list = new LinkedStack<Integer>();

check this link http://stackoverflow.com/questions/1970806/coding-to-interfaces — NPKR, Apr 16 '13 at 04:18

Patashu · Answer 1 · 2013-04-16T04:22:28.367

0

In my opinion:

LinkedStack<Integer> list = new LinkedStack<Integer>();

is better only if you need specific methods on LinkedStack that are not declared in StackInterface.

StackInterface<Integer> list = new LinkedStack<Integer>();

is better if you do not, because then you can 'plug in' any implementer of the interface for different reasons (efficiency reasons for example).

edited Apr 16 '13 at 04:22

answered Apr 16 '13 at 04:13

Patashu

I still don't find a good reason to use first option. If I have to use it by some means, I would prefer to encapsulate that portion of the code in a method with a comment warning that this method will try to use a specific implementation of the interface for a very specific job e.g. `TreeMap` or `TreeSet`. – Luiggi Mendoza Apr 16 '13 at 04:21

score 0 · Accepted Answer · answered Apr 16 '13 at 04:17

0

The second way is called code to interfaces.

second way is prefarable like. use interface as refference for subclass object.

answered Apr 16 '13 at 04:17

NPKR

2 Answers2