Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

sisc(1) [debian man page]

SISC(1) 						      General Commands Manual							   SISC(1)

NAME

       sisc - Second Interpreter of Scheme Code

SYNOPSIS

       sisc [ option ...  ] [ argument ...  [ -- [ program-option ...  ] ]

DESCRIPTION

       SISC,  the  Second Interpreter of Scheme Code, is an extensible Java based interpreter of the Scheme language as described in the Revised^5
       Report on the Algorithmic Language Scheme and adds numerous extensions including Java integration.

STARTUP FILE AND EXPRESSION OPTIONS

       -c name

       --call-with-args name
	      Calls the top-level procedure name with the remaining command-line arguments after the -- delimiter.

       -e expr

       --eval expr
	      Evaluates the provided expression.

       -x

       --no-repl
	      Instructs SISC to run the command line and then exit without entering the REPL.

       -h heap-file

       --heap heap-file
	      Specifies that heap-file should be used as the initial heap image.

       -p config-file

       --properties config-file
	      Specifies a Java property file that contains application properties.

       -l [<host>:]<port>

       --listen [<host>:]<port>
	      Server Mode.  Listen on <host>/<port> for REPL connections.

COMMAND LINE BEHAVIOR

       The commandline is processed in the following manner.

       First, the entire command line is processed, noting the settings of each switch and accumulating all  Scheme  source  files  and  arguments
       after the end of options sequence.

       Second, the heap file is loaded.

       Third, each Scheme source file is loaded in the order they occured on the command line. Errors are noted.

       Fourth, if present, the expression in an --eval switch is evaluated. Errors are noted.

       Fifth,  if  present, named function in a --call-with-args switch is applied to the arguments after the end of options sequence.	Its return
       value is noted.

       Sixth, --no-repl was not specified, the REPL is invoked.

       Finally, if the REPL was run if its return value is an integer, that integer is returned as SISC's overall return code. If the REPL was not
       run,  and any return code supporting step above was run, the most recent return code is returned. If no return code step was performed, but
       a success/failure step was performed, 1 is returned if any failures occured, 0 otherwise.

EXECUTABLE SCRIPTS

       SISC supports all the required SRFI-22 bootstraps, consult the body of SRFI-22 for more information about  using  it  to  write	executable
       Scheme programs.

MORE INFORMATION

       For further information on SISC, please read the SISC for Seasoned Schemers manual available at

							   http://sisc.sourceforge.net/manual/

BUGS

       Submit bug reports to the SISC Users Mailing List.

AUTHOR

       SISC was created by Scott G. Miller (sgmiller@gmail.com) with significant contribution from Matthias Radestock (matthias@sorted.org).

4th Berkeley Distribution					     June 2005								   SISC(1)

Check Out this Related Man Page

Devel::REPL::Profile(3pm)				User Contributed Perl Documentation				 Devel::REPL::Profile(3pm)

NAME

       Devel::REPL::Profile - code to execute when re.pl starts

SYNOPSIS

	package Devel::REPL::Profile::MyProject;

	use Moose;
	use namespace::clean -except => [ 'meta' ];

	with 'Devel::REPL::Profile';

	sub apply_profile {
	    my ($self, $repl) = @_;
	    # do something here
	}

	1;

DESCRIPTION

       For particular projects you might well end up running the same commands each time the REPL shell starts up - loading Perl modules, setting
       configuration, and so on.

       A mechanism called profiles exists to let you package and distribute these start-up scripts, as Perl modules.

USAGE

       Quite simply, follow the "SYNOPSIS" section above to create a boilerplate profile module. Within the "apply_profile" method, the $repl
       variable can be used to run any commands as the user would, within the context of their running "Devel::REPL" shell instance.

       For example, to load a module, you might have something like this:

	sub apply_profile {
	    my ($self, $repl) = @_;
	    $repl->eval('use Carp');
	}

       As you can see, the "eval" method is used to run any code. The user won't see any output from that, and the code can "safely" die without
       destroying the REPL shell. The return value of "eval" will be the return value of the code you gave, or else if it died then a
       "Devel::REPL::Error" object is returned.

       If you want to load a "Devel::REPL" plugin, then use the following method:

	$repl->load_plugin('Timing');

       The "load_plugin" and "eval" methods should cover most of what you would want to do before the user has access to the shell. Remember that
       plugin features are immediately available, so you can load for example the "LexEnv" plugin, and then declare "my" variables which the user
       will have access to.

   Selecting a Profile
       To run the shell with a particular profile, use the following command:

	system$ re.pl --profile MyProject

       Alternatively, you can set the environment variable "DEVEL_REPL_PROFILE" to MyProject.

       When the profile name is unqualified, as in the above example, the profile is assumed to be in the "Devel::REPL::Profile::" namespace.
       Otherwise if you pass something which contains the "::" character sequence, it will be loaded as-is.

AUTHOR

       Matt S Trout - mst (at) shadowcatsystems.co.uk (<http://www.shadowcatsystems.co.uk/>)

LICENSE

       This library is free software under the same terms as perl itself

perl v5.14.2							    2012-06-02						 Devel::REPL::Profile(3pm)
Man Page