Hi Eric:
Thanks, the ancestors method will work better.
Do class objects inherit all of the Module methods?
Bob Rice
On Jan 29, 2011, at 1:22 AM, Eric Christopherson wrote:
> On Wed, Jan 19, 2011 at 5:15 PM, Caio Chassot wrote:
>> On 2011-01-19, at 20:50 , Robert Rice wrote:
>>>
>>> You ins
On Wed, Jan 26, 2011 at 4:50 PM, Laurent Sansonetti
wrote:
> No, only locals and dynamic (block) variables.
> To be honest I always disliked this semantic change too. I think it was a
> mistake to add it. It will probably be reverted for 1.0.
I started to try to implement it, and it's not easy. I
It's great to see this discussion. As a developer, I just want to
‘require "bananas"’ and see it work.
I come from a Rails background, so I know that gem dependencies can
create all sorts of problems. As Macruby becomes more popular, these
problems are going to become more apparent as the diversity
I've reduced the problem to the code below. Creating 1000 proxy objects in a
loop isn't a typical use case, but it does occur when benchmarking and the
crash report is pretty consistent each time.
Should I open a ticket for this issue?
Alan
--
class Proxy
def initialize(delegate)
@de
Btw, I don't think a Gemfile adds anything for a bundled production
app besides that our shim would have to support the DSL. I think the
dev should just use ‘require "bananas"’ in her code and it should just
work. I.e. the Gemfile is I think only needed in development and at
release time.
On Sat,
Yes, what we need is a tool that resolves dependencies at release time
and bundle these in the app. The app also have a shim that makes sure
that if any of the bundled dependencies call Kernel#gem it doesn't
break. I.e. on the clients machine rubygems should not actually be
loaded to ensure as fast
