Class names in java.lang.Module
njbartlett at gmail.com
Mon Sep 26 09:25:44 UTC 2016
Module is already in the name: “java.lang.module.Configuration”. Wouldn’t “java.lang.module.ModuleConfiguration” look really odd?
> On 21 Sep 2016, at 16:18, Stephen Colebourne <scolebourne at joda.org> wrote:
> I had the same thought while watching the slides. Configuration is
> certainly a class name that exists other places, and would benefit
> from being ModuleConfiguration. Layer is less common, so not worried
> so much. Exceptions with "Module" in the name like
> ModuleNotFoundException would also be clearer.
> On 21 September 2016 at 03:36, Kasper Nielsen <kasperni at gmail.com> wrote:
>> I was wondering if there are any reasons for why these 3 classes in
>> Does not include the name Module?
>> I especially am not to fond of the very generic Configuration name in my
>> source code would much prefer something like ModuleConfiguration.
More information about the jigsaw-dev