From: Scott Barron <linguist@...>
Date: 2006-04-17T03:10:38+09:00
Subject: Re: Bug: Requiring "breakpoint" causes the entire Rails framework to load.

------=_Part_23878_4703018.1145211035206
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 4/16/06, Alder Green <alder.green@gmail.com> wrote:
>
> On 4/16/06, Logan Capaldo <logancapaldo@gmail.com> wrote:
> >
> > On Apr 16, 2006, at 1:09 AM, Alder Green wrote:
> >
> > > In the short-term, is the best solution to simply get ruby-breakpoint
> > > not through gems?  Or is there a way to fix this issue while still
> > > using the convenient gem version?
> > >
> >
> > I think maybe if you know the version of ruby-breakpoint and its not
> > the same as the rails one you could try something like
> > require 'rubygems'
> > require_gem 'ruby-breakpoint', '0.5.0'
> > require 'breakpoint'
>
> Hi Logan
>
> Thanks, your solution worked. "require_gem 'ruby-breakpoint', '0.5.0'"
> did in fact load only the 0.5.0 did in fact load only the
> ruby-breakpoint 0.5.0, and not the ruby-breakpoint bundled with Rails
> (whatever it is; I know not how to determine).
>
> However, on a permanent basis I'll probably use Florian Gro=DF's
> solution, which works as well: copying the two ruby-breakpoint rb
> files to site_ruby. This solution allows me to require ruby-breakpoint
> in the standard way ("require 'breakpoint'") and saves me the trouble
> of keeping track of my current ruby-breakpoint gem version and more
> importantly: of the Rails gem version, naturally worrying that one day
> it might catch up with the gem and bring back the problem I raised
> here.



Note that if you use require_gem 'ruby-breakpoint' instead of require
'breakpoint', you do not need to give a version.  By naming
'ruby-breakpoint' explictly, it will load the proper one.

-Scott

------=_Part_23878_4703018.1145211035206--