Here is my glue code. 
use strict;
package Extension;

sub apply_scalar_function_of_x {
  my $f = shift; # lisp source code, with x as the input, e.g., "* x 0
+.1"
                 # As a convenience feature, if $f is undefined or nul
+l string, we return the input unaltered.
  my $x = shift;
  if (!defined $f) {return $x}
  my $lisp = "(display ((lambda (x) ($f)) $x))";
  my $result = `guile -c '$lisp'`;
  if ($? == 0) {
    return $result;
  }
  else {
    print STDERR "Error executing scheme code $lisp using guile.";
    return undef; # occurs if guile is not installed or the guile code
+ dies with an error
  }
  # to do:
  #   Escape single quotes inside the string.
}

1;

[download]

Unfortunately, as discussed, this suffers from multiple potential injection and quoting issues. In this case, I would recommend either IPC::Run3 (libipc-run3-perl) or IPC::System::Simple (libipc-system-simple-perl) - the former is probably better if this software is supposed to run on Windows too. If you don't want to install an extra module, then you could use the piped open I show near the bottom of my post here.

use IPC::System::Simple qw/capturex/;
sub apply_scalar_function_of_x {
    my $f = shift;
    my $x = shift;
    if (!defined $f) {return $x}
    my $lisp = "(display ((lambda (x) ($f)) $x))";
    my $result;
    if (not eval { $result = capturex('guile','-c',$lisp); 1 }) {
        print STDERR "Error executing scheme code using guile.\n";
        return;
    }
    return $result;
}

[download]
I'm looking into how to sandbox Guile. ... if there's any way to prevent code from accessing the file system and such.

Yes, I would very strongly recommend not leaving an open source grading system open to attacks ;-)

In reply to Re^2: Extending a perl program with Scheme, Lua, or JS by haukex
in thread Extending a perl program with Scheme, Lua, or JS by bcrowell2

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.