Trans wrote:
> Marshall T. Vandegrift wrote:
>> You could #eval the code in the subprocess.  That seems like an easy (if
>> slightly kludgey) way to get the benefits of both methods.
> 
> Nice! I'll try that!
> 
> Just the sort of creative answer I hoping for. Thanks Marshall.

Marshall's solution should be just fine--however,
I wanted to mention something a bit extraneous: the
library name 'rubyinline' can easily be confused with
the existing Inline libs.

I understand that this is a generalised version, but I
would still recommend using the standard test format by
naming the libs Test::Inline and reside in test/inline.

Not sure what to call it if you want to designate it as
separate from testing--'runcomments', 'comments2ruby' or
something maybe? :)

> T.


-- 
Posted via http://www.ruby-forum.com/.