8182482: Module System spec updates

[Remi Forax]

----- Mail original -----
> De: "Alex Buckley" <alex.buckley at oracle.com>
> À: "jigsaw-dev" <jigsaw-dev at openjdk.java.net>
> Envoyé: Mardi 20 Juin 2017 20:09:14
> Objet: Re: 8182482: Module System spec updates

> Hi Remi,
> 
> On 6/20/2017 6:29 AM, forax at univ-mlv.fr wrote:
>> ok, let's focus on abstract class defining a service.
> 
> I would be happy for the "Designing services" section to give more
> advice about the tradeoffs between an interface and an abstract class.
> Two sentences, written in a style that leads a junior developer but does
> not judge them if they don't follow the advice. Can you write it? :-

sure let's try:
if you are wondering when to use an interface and when to use an abstract class, you can use this advice: most of the time you should favor interfaces, unless you want to execute your own code as part of any service implementations like by example when you want to add a security check to validate something about the implementation.

I'm sure you will be able to transform it in proper English.

> 
> -----
> A service is a single type, usually an interface or abstract class.
> ***REMI'S TEXT HERE*** A concrete class can be used, but this is not
> recommended. The type may have any accessibility.
> 
> The methods of a service are highly ...
> -----
> 
> Alex

Rémi