Is there a way to call R from a standalone C++ program without the need to disclose the source -

we think using statistical library package in our application , want know whether possible use r without having publish source of our application.

thank you. tobias

you should definitively ask lawyer (or maybe intellectual property department).

however, here 2 ct:

• it should possible same way allows writing closed-source programs linux.

• a solution emphasizes fact talking 2 programs, r , yours, using r server

• wikipedia summarizes discussion whether linking implies result derived work.
  not astonishingly, fsf's point of view is irrelevant whether linking dynamic or static. after all, if linking of program non-free (incompatible) licence free library should allowed, license of library should lgpl instead of gpl. however, wiki article gives other points of view well.

here 2 relevant snippets gpl faq:

• what difference between “aggregate” , other kinds of “modified versions”?

  an “aggregate” consists of number of separate programs, distributed on same cd-rom or other media. gpl permits create , distribute aggregate, when licenses of other software non-free or gpl-incompatible. condition cannot release aggregate under license prohibits users exercising rights each program's individual license grant them.

  where's line between 2 separate programs, , 1 program 2 parts? legal question, judges decide. [...]

  if modules included in same executable file, combined in 1 program. if modules designed run linked in shared address space, surely means combining them 1 program.

  by contrast, pipes, sockets , command-line arguments communication mechanisms used between 2 separate programs. when used communication, modules separate programs. if semantics of communication intimate enough, exchanging complex internal data structures, basis consider 2 parts combined larger program.

• i'd incorporate gpl-covered software in proprietary system. can this?

  you cannot incorporate gpl-covered software in proprietary system. [...]

  however, in many cases can distribute gpl-covered software alongside proprietary system. validly, must make sure free , non-free programs communicate @ arms length, not combined in way make them single program.

  the difference between , “incorporating” gpl-covered software partly matter of substance , partly form. substantive part this: if 2 programs combined become 2 parts of 1 program, can't treat them 2 separate programs. gpl has cover whole thing.

  if 2 programs remain separated, compiler , kernel, or editor , shell, can treat them 2 separate programs—but have properly. [...]