From: Lothar Scholz <mailinglists@...>
Date: 2004-06-04T10:14:25+09:00
Subject: Re: Obfuscating Ruby Code.

Hello Tim,

TS> This causes problems with method_missing. e.g. what happens if you obfuscate
TS> the `foo' method in the following code:

TS> class Foo
TS>   def method_missing(name, *args)
TS>     name == :foo
TS>   end
TS> end

TS> a = Foo.new
TS> puts(a.foo)

Right, things like this bites you not only in an Obfuscator Tool but
also in a Refactoring Tool etc.

So at the beginning of a project that must use automatic source
code manipulation tools there should be a programming style guide with
things that shouldn't be used. At the moment i would be happy if we could
force all people to make their files (at least all files from the
standard ruby library) "requireable". With this we could write tool
that have access to the introspection features.

But we are still far away even from this (the python community is
in the same situation).


-- 
 Best regards,                        emailto: scholz at scriptolutions dot com
 Lothar Scholz                        http://www.ruby-ide.com
 CTO Scriptolutions                   Ruby, PHP, Python IDE 's