From hin-tak.leung at cimr.cam.ac.uk  Mon Jan 28 22:50:54 2008
From: hin-tak.leung at cimr.cam.ac.uk (Hin-Tak Leung)
Date: Mon, 28 Jan 2008 21:50:54 +0000
Subject: [Rd] Distributing R Programs
In-Reply-To: <479E433D.6090507@biostat.ku.dk>
References: <fnl7l7$3g8$1@ger.gmane.org> <479E433D.6090507@biostat.ku.dk>
Message-ID: <479E4E3E.4080007@cimr.cam.ac.uk>

Peter Dalgaard wrote:
> CapCity wrote:
>> We recently developed an R program as part of an application. We'd like to
>> distribute this, but not allow access to the R source code. Is this
>> possible?
>>
>>   
> Not in any obvious way, and I don't think anyone around here would 
> volunteer to help you find out.

:-). I don't like the idea of hiding source code - I am not an 
open-source fanatic, but a broken piece of software can be fixed by a 
3rd party, otherwise you are at the mercy of the time/financial 
constraints of the author...

That said, since the original poster said 'as a part of an application',
it is probably possible to just uuencode/flatencode/ucs-16 some R-code,
stuff it down as a long char array, and pass the decrypted version one 
line at a time to R_eval() in a C wrapper, just to get around the usual
R ways of getting at the R-based source code.



[Rd] Distributing R Programs
Hin-Tak Leung