marcandre/backports — pull request #63 by hynkle (2012-10-03 19:31:09+00:00)
Title: add advice about requiring early to readme

If you do:

```ruby
require 'prime'
require 'backports'
```

you get the following noise on stderr:

```
Prime::new is obsolete. use Prime::instance or class methods of Prime.
…/gems/backports-2.6.4/lib/backports/1.9.1/stdlib/prime.rb:411: warning: already initialized constant BITS_PER_ENTRY
…/gems/backports-2.6.4/lib/backports/1.9.1/stdlib/prime.rb:412: warning: already initialized constant NUMS_PER_ENTRY
…/gems/backports-2.6.4/lib/backports/1.9.1/stdlib/prime.rb:413: warning: already initialized constant ENTRIES_PER_TABLE
…/gems/backports-2.6.4/lib/backports/1.9.1/stdlib/prime.rb:414: warning: already initialized constant NUMS_PER_TABLE
…/gems/backports-2.6.4/lib/backports/1.9.1/stdlib/prime.rb:415: warning: already initialized constant FILLED_ENTRY
```

Not very surprising behavior in this reduced case, but I ran across it in a less obvious fashion when I required a gem that requires 'prime' before I required the gem I'm using that requires 'backports'. Hopefully adding this to the Readme can help someone else figure out why they're getting these warnings a bit quicker than I did.