From: Trans Date: 2005-10-23T23:57:53+09:00 Subject: Re: facets gem exception Brian Buckley wrote: > > What did you remove exactly? > > The require I removed had been a file that contained more requires > which in turn had more requires, etc... a whole require tree. But > now I've isolated the problem to facet/array/each_permutation > > require 'facet/array/each_permutation' > require 'facet/enumerable/probability' > > These two lines back to back cause my gem exception. > > Looking at the gems, I see that facet/array/each_permutation is not > part of the current facet(2005.10.15) but it is in facet(0.7.2). > > Any explanation on what's happening here appreciated. I see. Gems is activating 0.7.2 b/c #each_permutation is defined as an array method in 0.7.2, but in the latest version it has been moved to enumerable. So change to: require 'facet/enumerable/each_permutation' require 'facet/enumerable/probability' > PS One more fact, possibly related. My system also has the "nano" gem > installed (0.9.2,0.8.2) which looks like a near copy of the facets gem > and I even see facets has a directory called nano. What is the > relationship between the facet gem and the nano gem? I will explain better soon in offical announcemnt of new Facets, after I finish final todos. But the short of it is simply this: I had changed name to Nano Methods, but after recieveing a great deal of email about Facets, I decided it better to keep Facets name. The project is quite broad now, so currently nano/ dir serves to sort out the methods part of it, mega/ the modules part and facet/ dir contains redirects to all parts. So the thing to do now is to: gem uninstall nano gem uninstall mega (if you have this too) With Facets you can use either: require 'facet/...' or require 'nano/...' # for methods require 'mega/...' # for modules Either will work. T. P.S. The upcoming release that I am finsihing off now will makes things a lot smoother in that it has better interface and will automatically search inheritance chain for matching method.