This site is a static rendering of the Trac instance that was used by R7RS-WG1 for its work on R7RS-small (PDF), which was ratified in 2013. For more information, see Home.

Ticket 62: Environment Variables

2012-10-05 00:48:01
WG1 - Core
alexshinn
major
cowan
fixed
source
closed
2010-05-03 00:27:59
defect

Currently, there is no standard way to communicate with the context from which a Scheme program was started. This has become pretty standardized over time: a list of strings ("command-line arguments") and a map from strings to strings ("environment variables") on input, and a small integer or string on output ("exit value"). Scheme should recognize these realities.

We have command-line and exit from ModulesShinn, so the question remains if we should add SRFI-98 environment accessors.

cowan
2010-05-03 00:30:46
descriptionCurrently, there is no standard way to get the context from which a Scheme program was started. This has become pretty standardized over time: a list of strings ("command-line arguments") and a map from strings to strings ("environment variables") on input, and a small integer or a string on output ("exit value"). Scheme should recognize these realities.Currently, there is no standard way to communicate with the context from which a Scheme program was started. This has become pretty standardized over time: a list of strings ("command-line arguments") and a map from strings to strings ("environment variables") on input, and a small integer or string on output ("exit value"). Scheme should recognize these realities.

I propose an optional module (optional so that embedded Schemes don't have to support it) containing command-line and quit from (rnrs programs), and get-environment-variable and get-environment-variables from SRFI 98.

alexshinn
2010-11-15 10:14:07
descriptionCurrently, there is no standard way to communicate with the context from which a Scheme program was started. This has become pretty standardized over time: a list of strings ("command-line arguments") and a map from strings to strings ("environment variables") on input, and a small integer or string on output ("exit value"). Scheme should recognize these realities.Currently, there is no standard way to communicate with the context from which a Scheme program was started. This has become pretty standardized over time: a list of strings ("command-line arguments") and a map from strings to strings ("environment variables") on input, and a small integer or string on output ("exit value"). Scheme should recognize these realities. We have `command-line` and `exit` from ModulesShinn, so the question remains if we should add SRFI-98 environment accessors.
cowan
2010-11-15 15:14:59

ModulesShinn does not contain the string "exit" anywhere.

cowan
2011-01-24 06:39:36
resolution␣fixed
statusnewclosed

WG1 voted to accept SRFI 98.

alexshinn
2011-01-29 11:50:56
resolutionfixed␣
statusclosedreopened
alexshinn
2011-01-29 11:51:32
summaryThe calling contextEnvironment Variables
owneralexshinn␣
statusreopenedassigned
alexshinn
2011-01-29 11:51:43
statusassigneddecided
alexshinn
2011-02-26 19:44:04
owner␣alexshinn
statusdecidedwriting
cowan
2012-10-05 00:48:01
resolution␣fixed
statuswritingclosed