You can edit this page using wiki syntax for markup.

Article contents:== CHICKEN for Racket programmers Warning: This is very much a work in progress! [[toc:]] === Running scripts Racket: <enscript> #!/usr/bin/env racket #lang racket </enscript> For Chicken, using {{env}} as shown above is not a viable solution because the Chicken Scheme interpreter ({{csi}}) requires the {{-s}} option in order to run in script mode rather than in REPL mode. And it seems as if, currently, only GNU {{env}} provides a way to run commands with additional arguments form a shebang line. So, the most straightforward way to get your Chicken scripts to run is simply using the actual path to the Chicken Scheme interpreter on your system. This can easily be found by running {{command -v csi}} in a non-interactive POSIX-compatible shell: <enscript> $ sh -c 'command -v csi' </enscript> Running the shell non-interactively bypasses any existing shell command aliases, which is the desired behavior here. On a Debian system, the above command returns {{/usr/bin/csi}}. On NetBSD, you get {{/usr/pkg/bin/csi}}. So, to create a runnable Chicken script on the latter, the first line in the file has to be this: <enscript> #!/usr/pkg/bin/csi -s </enscript> Should you need your Chicken scripts to be portable, there are also ways to achieve that without using {{env}}. See [[writing portable scripts|Writing portable scripts]]. === Procedures ==== Optional arguments ==== Named parameters === String manipulation ==== Splitting strings ==== Regular expressionsDescription of your changes:

I would like to authenticate

Spam control

What do you get when you add 21 to 5?