[jsr294-modularity-eg] Ignoring unknown directives...

[Bob Lee]

On Mon, Jun 29, 2009 at 3:21 PM, Bryan Atsatt <bryan.atsatt at oracle.com>wrote:

> It only addresses the validation phase, not resolution.
>

Validation a la annotation/directive types is pretty good. Don't throw the
baby out with the bathwater.


> I'm not sure when it is the case that "the module system can't perform
> higher-level validations". The module system will be available to the
> compiler, or compilation will fail; we are simply considering (this part of)
> the module system api to be a compiler extension. And the same api will be
> available to any other tool or runtime.
>

I thought we were discussing how to handle directives that aren't recognized
by the module system, i.e. due to a minor misspelling.

I'm sorry, but the current language extension is flexible where it should be
limited, and inflexible where it should be extensible and future-proof. It's
entirely divergent from preexisting features of the language, and it seems
to be getting more complex and straying even further. The only defense for
this approach is lack of resources.

Thanks,
Bob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/jsr294-modularity-eg/attachments/20090629/6d38d838/attachment.html>