comment on

Many thanks for this.

I need to look more deeply but gtools seems to use system calls. My fallback is to run scripts using system calls, but ideally there would be persistence so the perl side of things can run more analyses without having to restart scripts and reload data.

It also requires the user have a working perl. My system has a large dependency tree that includes many XS libs so can't be fatpacked. Compiling using RTools and installing using a project level local::lib is not impossible but does get complex and hard to control across user environments. ...Although now I read more I see it can compile such libs.

Thanks also for the sockets/pipes advice. I knew about arbitrary code but had never considered external websites hitting local services.

In reply to Re^2: Calling perl systems from other systems, e.g. R by swl
in thread Calling perl systems from other systems, e.g. R by swl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks