Forcing promises and licence.

Hello.I’ve been looking around on the Internet as to how to force R promisesfrom C code, in the scope of the OCaml-R binding I’m currentlywriting. I’ve stumbled with a google search involving forcing R C promises PROMSXPon the following webpage http://kx.com/q/interfaces/r/kdbplus.cwhere there is some definitely interesting stuff.First, here’s a licencing rant: You google something, hit a .cwebpage, look at the code. No copyright header there. You read thecode. You look around further, and you see that one gets bound to thelicence when downloading code. That’s fairly different from, say, GPL-style license, where you get bound to the licence when you distributethe code. So here’s the rant: I do not appreciate wondering if I getbound to a licence when reading a “random” webpage with no licensinginformation. Please include a licensing header so that I know if Ishould turn a blind eye on the code or not.Now, a compliment: it seems that the kdb+ binding to R is fairlyclean. I nevertheless haven’t found how to force a promise from Ccode. I somehow believe that this has been done somewhere. Please tellme if I’m wrong. Probably in the http://kx.com/q/interfaces/r/l64/c.ofile? I’d appreciate confirmation, since I believe that the c.o fileis much more touchy licence-wise than the kdbplus.c file…All the best,-- Guillaume Yziquelhttp://yziquel.homelinux.org

Guillaume,c.o contains socket and memory management code only.it looks like promises are not implementedstatic K from_promise_robject(SEXP expression){ return kp(“promise”);}kp just generates a char vector, ignoring the expression.CharlieOn Sun, Nov 22, 2009 at 3:18 PM, Guillaume Yziquel<guillaume.yziquel> wrote:> Hello.>> I’ve been looking around on the Internet as to how to force R promises> from C code, in the scope of the OCaml-R binding I’m currently> writing. I’ve stumbled with a google search involving>> ? ? ? ?forcing R C promises PROMSXP>> on the following webpage>> ? ? ? ?http://kx.com/q/interfaces/r/kdbplus.c&gt;&gt; where there is some definitely interesting stuff.>> First, here’s a licencing rant: You google something, hit a .c> webpage, look at the code. No copyright header there. You read the> code. You look around further, and you see that one gets bound to the> licence when downloading code. That’s fairly different from, say, GPL-> style license, where you get bound to the licence when you distribute> the code. So here’s the rant: I do not appreciate wondering if I get> bound to a licence when reading a “random” webpage with no licensing> information. Please include a licensing header so that I know if I> should turn a blind eye on the code or not.>> Now, a compliment: it seems that the kdb+ binding to R is fairly> clean. I nevertheless haven’t found how to force a promise from C> code. I somehow believe that this has been done somewhere. Please tell> me if I’m wrong. Probably in the>> ? ? ? ?http://kx.com/q/interfaces/r/l64/c.o&gt;&gt; file? I’d appreciate confirmation, since I believe that the c.o file> is much more touchy licence-wise than the ?kdbplus.c file…>> All the best,>> –> ? ? Guillaume Yziquel> http://yziquel.homelinux.org>> –>>

Submitted via Google Groups</guillaume.yziquel>