Proper term for non-automatic modules

[Nicolai Parlog]

 Hi Alan,

thanks for your quick answer. I shall use "explicit", then. :)

 so long ... Nicolai



On 29.08.2017 08:56, Alan Bateman wrote:
> 
> 
> On 29/08/2017 06:52, Nicolai Parlog wrote:
>>   Hi!
>>
>> While describing the difference between automatic and non-automatic
>> modules I often need a term do describe the modules that are not
>> automatic (as I did twice just now).
>>
>> As far as I know there is no such term. There are a few related ones but
>> unless I missed something none describes quite the right set:
>>
>> * named modules include automatic modules
>> * platform modules leave out user-created modules
>> * application modules include automatic modules
>>    (if they don't, then `{ platform } ∪ { application }` is
>>     the right set)
>>
>> I think a term for `{ named } ∖ { automatic }` is important when
>> discussing automatic modules and it would be very helpful if the Jigsaw
>> team coins it.
>>
>> My suggestions are "explicit", "proper", and "manual" modules.
>>
> We've been using term "explicit".  You'll see it used in the
> ModuleFinder.of(Path...) spec for example where it describes a modular
> JAR as defining an explicit module.
> 
> -Alan.
> 

-- 

PGP Key:
    http://keys.gnupg.net/pks/lookup?op=vindex&search=0xCA3BAD2E9CCCD509

Web:
    http://codefx.org
        a blog about software development
    https://www.sitepoint.com/java
        high-quality Java/JVM content
    http://do-foss.de
        Free and Open Source Software for the City of Dortmund

Twitter:
    https://twitter.com/nipafx