On Sun, Feb 02, 2003 at 09:35:26PM +0900, Tom Sawyer wrote: > On Sunday 02 February 2003 03:34 am, Mauricio FernáÏdez wrote: > > your NoOverloading code looks fantastic! > > i must say i expected to be told it wasn't possible. awesome that you were > able to put together a nice solution so quickly. thank you. thank you. thank > you. definitely going into my general library of tools. and truly this (or > its kin written in c) should be considered for inclusion in Ruby proper! I'm quite happy with that code, as I get to mix some of my all-time favorite idioms/features into it ;-) * class instance variables: have been in love for a long time w/ them * singleton methods, especially when added dynamically to a class * nesting a singleton method def inside a method definition In a three words, _singletons classes rule_! I felt so satisfied to get this to work that I put it in the Wiki http://www.rubygarden.org/ruby?PreventingOverloading Now comes the important question: why do you need that? If you find a good use-case scenario, you can start lobbying to get people to use it and then convince matz to make it standard and render me somewhat famous ;-) -- _ _ | |__ __ _| |_ ___ _ __ ___ __ _ _ __ | '_ \ / _` | __/ __| '_ ` _ \ / _` | '_ \ | |_) | (_| | |_\__ \ | | | | | (_| | | | | |_.__/ \__,_|\__|___/_| |_| |_|\__,_|_| |_| Running Debian GNU/Linux Sid (unstable) batsman dot geo at yahoo dot com Software is like sex; it's better when it's free. -- Linus Torvalds