On 14/03/11 13:51 , Luis Lavena wrote:
On Mon, Mar 14, 2011 at 7:55 AM, Jim Weirich<[email protected]> wrote:
On Mar 14, 2011, at 3:34 AM, James M. Lawrence wrote:
Are you sure you wish to deprecate 'import'? It seems a gray area due
to the reasons I gave. I assume googlers will find this thread after
being flooded with 'import' warnings :)
Ok, fair question. I'll put it to the mailing list: Deprecate import or not.
I see several options:
(A) Leave import as is and let JRuby worry about the conflict.
(B) Deprecate import (favoring Rake.import), eventually ceding the import
statement to JRuby (this is in the current beta direction)
(C) Make A vs B a command line option (but which way to default?)
I haven't used import in *long* time, and none of my projects uses it nowdays.
I barely remember one or 2 projects that did use it, I think Rubinius
was one where I saw it.
If voting counts, I would say (B) and set a date for removal.
Ditto.
I don't think I've ever used import and I 've got several projects (6 to
be exact) here that are not mine and don't use import either.
B would be my prefered option as well.
Cheers,
V.-
--
http://www.ampelofilosofies.gr
_______________________________________________
Rake-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/rake-devel
