From: David Douthitt Date: 2000-05-30T08:57:10-05:00 Subject: [ruby-talk:03036] Keywords This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_712976DB.F998FD82 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable > I have recently discovered that things that I thought > were "reserved words" can actually serve as method names and the like. > This shocked me. It doesn't really bother me, but it surprised me. > For example, I used a method named "class" and it worked fine. I actually did something like this - and seems to me it caused me grief. I know I've run into lots of problems when I define a method "print" and = then use print "foo" WITHIN the new "print" method :-) Time for lots of "Kernel.print" = statements.... --=_712976DB.F998FD82 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

> I have recently discovered that things that I=20 thought

> were "reserved words" can actually serve as = method names=20 and the like.

> This shocked me. It doesn't really bother me, = but it=20 surprised me.

> For example, I used a method named "class" and = it=20 worked fine.

I actually did something like this - and seems to me = it caused=20 me grief.

I know I've run into lots of problems when I define a = method=20 "print" and then use

print "foo"

WITHIN the new "print" method :-) Time for lots = of=20 "Kernel.print" statements....

--=_712976DB.F998FD82--