This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
define-alias question
- From: Matthieu Vachon <matthieu dot o dot vachon at gmail dot com>
- To: "kawa at sourceware dot org" <kawa at sourceware dot org>
- Date: Wed, 17 Jul 2013 22:29:49 -0400
- Subject: define-alias question
Hi all,
Is it intended that `define-alias` are exportable? From my point of
view, `define-alias` are used mainly to reduce variable name length
and hence, have little usage when exported and reuse across multiple
modules.
The aliases enable us to have more readable code by aliasing java
fully qualified name to their simple name. However, we often hit
warnings saying that some alias is already specified from another
module. This happens when the module export all of its definitions and
this module is imported in another module.
I think this should not happen because in my opinion, alias should be
private to the module where they were defined. I see not much points
in making them exportable other then creating conflicts. Of course, I
could oversee some really valid use-cases that would involve exporting
aliases.
What do you think about this potential change? I would like to know if
such change would be eventually merged before I start putting time
into it. Should it be only enabled by setting a specific flag?
Regards,
Matt