classes and interfaces of every exported package in the module java.base, there
should be a way to specify this in a traditional compilation unit with explicit
class declarations.
To this end, we add a new kind of import declaration: the module-import
declaration. It imports (as needed) all
sses automatically import (as needed) all the
> accessible classes and interfaces of every exported package in the module
> java.base, there should be a way to specify this in a traditional compilation
> unit with explicit class declarations.
>
> To this end, we add a new kind of im
On 2/26/2024 2:32 AM, fo...@univ-mlv.fr wrote:
Oh, so you do not know why import star/wildcard is considered evil.
The main reason is that an import * is considered as a security
malpractice.
Hyperbole is not helpful here.
choice.
Rémi
> From: "Brian Goetz"
> To: "Remi Forax" , "amber-spec-experts"
>
> Sent: Friday, February 23, 2024 3:49:21 PM
> Subject: Re: module-import declaration
> (I think we've had this discussion already? Seems eerily familiar.)
> I re
atically import (as needed) all the accessible
classes and interfaces of every exported package in the module java.base, there
should be a way to specify this in a traditional compilation unit with explicit
class declarations.
To this end, we add a new kind of import declaration: the module-import
dec
ssible
classes and interfaces of every exported package in the module java.base, there
should be a way to specify this in a traditional compilation unit with explicit
class declarations.
To this end, we add a new kind of import declaration: the module-import
declaration. It imports
