Are there any accepted or already practiced ways for companies to prevent Ruby source code from being read by potential competitors? I can vaguely imagine redefining Ruby’s “require”-type methods so they can include zipped and passworded “.rbz” files, say. Or using exerb (except for UNIX and without the potential license issues).
I want to use Ruby at work but this is one of those “steps to convincing your boss to use Ruby” I need to go through.
Greg McIntyre
Hello Greg,
Tuesday, March 30, 2004, 10:04:25 AM, you wrote:
Are there any accepted or already practiced ways for
companies to prevent Ruby source code from being read by potential
competitors? I can vaguely imagine redefining Ruby's
"require"-type methods so they can include zipped and passworded
".rbz" files, say. Or using exerb (except for UNIX and without the
potential license issues).
I want to use Ruby at work but this is one of those "steps to
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.
--
Best regards,
Lothar mailto:mailinglists@scriptolutions.com
Ah, that’s quite clever because I presume it also gets around the
licensing issue with the regexp library Ruby uses… Is that right?
Thanks
Lothar Scholz mailinglists@scriptolutions.com wrote:
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.
–
Greg McIntyre ======[ greg@puyo.cjb.net ]===[ http://puyo.cjb.net ]===