Lothar Scholz posted this to the Ruby-ML.
GM> Are there any accepted or already practiced ways for
GM> companies to prevent Ruby source code from being read by potential
GM> competitors? I can vaguely imagine redefining Ruby's
GM> "require"-type methods so they can include zipped and passworded
GM> ".rbz" files, say. Or using exerb (except for UNIX and without the
GM> potential license issues).
GM> I want to use Ruby at work but this is one of those "steps to
GM> convincing your boss to use Ruby" I need to go through.
Just look at the "eval.c" file, i think the require is defined
there and then write your hook. Or write a dll/so and add embedd your rb
files as large c strings there (using maybe the "wrap" tool from
the Fox Toolkit) and then do rb_eval_string("my c file"). After
this protect the dll with something like "armadillo" (use google
to find the URL). This works perfectly for me.