Re: REXML::Functions.name == nil

On Tue, 30 Nov 2004 09:53:38 +0900, Ryan Davis <[e-mail]> wrote:
> On Nov 29, 2004, at 6:30 AM, Florian Growrote:
> > Ryan Davis wrote:
> >> I found this oddity while running ParseTree over every .rb file in
> >> the ruby libs:
> >>> irb(main):003:0> REXML::Functions.name
> >>> => nil
> >> sure enough, Functions::name is defined. This seems bad to me. It
> >> also defines id and breaks it too:
> >>> irb(main):004:0> Class.id
> >>> => 974456
> >>> irb(main):005:0> REXML::Functions.id
> >>> ArgumentError: wrong number of arguments (0 for 1)
> >> Can we get these renamed or otherwise make them work with their
> >> regular semantics?
> > I'm not sure about .id as that should not be used anymore anyway, (use
> > .object_id instead) but for REXML::Functions.name a workaround is to
> > use Module.instance_method(:name).bind(REXML::Functions).call
> Until .id is removed from the vocabulary (and probably a long while
> afterwards so that people can assume backwards compatibility), it
> shouldn't be overridden.

I personally always use #__id__ when I need the object's ID, not #id
or #object_id. Maybe we need a #__name__ as well? #__id__ shouldn't be
overridden.

-austin
-- 
Austin Ziegler * [e-mail]
               * Alternate: [e-mail]