# Redefine "method" method

**URL:** <https://www.ruby-forum.com/t/redefine-method-method/145785>\
**Category:** Ruby\
**Created:** [August 13, 2008, 10:13pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785 "2008-08-13T22:13:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 10:13pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/1 "2008-08-13T22:13:36Z")

</div>

Hi, I’d like to have a method called “method” in some classes, but  
since “method” is a Ruby method present in any class I would like if it  
could  
originate any problem.

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 10:34pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/2 "2008-08-13T22:34:07Z")

</div>

Technically, it seems that you could do something along the lines of the  
following:

class Test  
class \<\< self  
undef\_method “method”  
end  
end

Although… that really seems like a bad idea. I don’t know enough about  
the  
internals to say whether or not anything would break (I poked at it a  
little  
and haven’t tripped across any side effects, but it seems like there  
should  
be).

Any chance you could just use a different name for your method?

–Tommy M.

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 10:49pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/3 "2008-08-13T22:49:56Z")

</div>

El MiÃ©rcoles, 13 de Agosto de 2008, Tommy Morgan escribiÃ³:

> Any chance you could just use a different name for your method?

Of course, but I’m doing a SIP protocol application, in which a core  
concept  
is the _method_ (INVITE, ACK, BYE…), so it would be really nice to  
use:

request.method

instead of:

request.sip\_method \<— This is what I use for now.

Thanks.

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 10:56pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/4 "2008-08-13T22:56:23Z")

</div>

On 13.08.2008 22:10, Iñaki Baz C. wrote:

> Hi, I’d like to have a method called “method” in some classes, but  
> since “method” is a Ruby method present in any class I would like if it could  
> originate any problem.

I’d say the idea is not so good because - depending on libraries that  
you use - you might experience errors or strange behavior. I’d rather  
choose a different name if at all possible.

Kind regards

robert

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 11:06pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/5 "2008-08-13T23:06:56Z")

</div>

Well, for what it’s wirth:

I think request.sip\_method is actually better.  
While it’s important to try and go for naming conventions in your code  
that  
are succinct, you also want to avoid ambiguity. If someone else is  
looking  
at your code and they see ‘request.method’, it isn’t obvious that you  
are  
referring to something aside from what is built into ruby. sip\_method  
helps  
to avoid that ambiguity, and it also allows you to go back and utilize  
the  
built-in method if you need to at some point in the future.

Hope that helps.

–Tommy M.

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 11:03pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/6 "2008-08-13T23:03:25Z")

</div>

El Miércoles, 13 de Agosto de 2008, Robert K.  
escribió:\> On 13.08.2008 22:10, Iñaki Baz C. wrote:

> > Hi, I’d like to have a method called “method” in some classes, but  
> > since “method” is a Ruby method present in any class I would like if it  
> > could originate any problem.
> 
> I’d say the idea is not so good because - depending on libraries that  
> you use - you might experience errors or strange behavior. I’d rather  
> choose a different name if at all possible.

Thanks.  
In fact, I’ve just realized that I can use “Method” nada 🙂

---

<div class="post-metadata">

**Author:** ![ISSSSaki\_Baz\_C](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/51bf81/32.png) [@ISSSSaki\_Baz\_C](https://www.ruby-forum.com/u/ISSSSaki_Baz_C)\
**Post date:** [August 13, 2008, 11:42pm UTC](https://www.ruby-forum.com/t/redefine-method-method/145785/7 "2008-08-13T23:42:39Z")

</div>

El MiÃ©rcoles, 13 de Agosto de 2008, Tommy Morgan escribiÃ³:

> Hope that helps.  
> Enough arguments to remain using “sip\_method” 🙂

Thanks.
