This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: define-alias question
- From: Matthieu Vachon <matthieu dot o dot vachon at gmail dot com>
- To: "kawa at sourceware dot org list" <kawa at sourceware dot org>
- Date: Fri, 19 Jul 2013 12:51:03 -0400
- Subject: Re: define-alias question
- References: <CAOTvmokJvFFYkeCJPvD-VTmZNQ-n=S1v7AdyyTwyjDUQdbj3Vw at mail dot gmail dot com> <51E7900F dot 7060301 at bothner dot com> <19C6E9FB-A962-4830-8877-D662D89B34DB at theptrgroup dot com>
>
> I have no problem with requiring an export statement, in fact I think I already do that in most of my code. But I would be annoyed if it were impossible to export aliases.
>
I was a bit too "aggressive" with my first proposition. Removing
ability to export
aliases is not a good idea as you mentioned. Requiring an explicit export is a
better alternative that brings in my opinion the best of both world.
Ability to use `define-alias` like java imports without having bunch
of warnings
about already defined alias and ability to create dedicated aliases
module where aliases are exported and can be reused by other modules.
I'm going to propose a patch for this feature soon.
Regards,
Matt