[Rake-devel] Deprecating Import ???

Wayne E. Seguin wayneeseguin at gmail.com
Mon Mar 14 09:37:15 EDT 2011


I  have never used import myself directly, I vote for B.  IMHO namespacing a
loading mechanism
specifc to the library (Rake.import) is always a better option in order to
avoid general conflicts even
with other libraries.

  ~Wayne

On Mon, Mar 14, 2011 at 6:55 AM, Jim Weirich <jim.weirich at gmail.com> 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?)
>
> Weight in people.
>
> --
> -- Jim Weirich
> -- jim.weirich at gmail.com
>
>
>
>
> _______________________________________________
> Rake-devel mailing list
> Rake-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rake-devel
>



-- 
  ~Wayne

Wayne E. Seguin
wayneeseguin at gmail.com
wayneeseguin on irc.freenode.net
http://twitter.com/wayneeseguin/
https://github.com/wayneeseguin/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/rake-devel/attachments/20110314/924df879/attachment.html>


More information about the Rake-devel mailing list