Opened 7 years ago

Closed 5 years ago

#62 closed defect (fixed)

Environment Variables

Reported by: cowan Owned by: alexshinn
Priority: major Milestone:
Component: WG1 - Core Keywords:
Cc:

Description (last modified by alexshinn)

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.

Change History (9)

comment:1 Changed 7 years ago by cowan

  • Description modified (diff)

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.

comment:2 Changed 7 years ago by alexshinn

  • Description modified (diff)

comment:3 Changed 7 years ago by cowan

ModulesShinn does not contain the string "exit" anywhere.

comment:4 Changed 6 years ago by cowan

  • Resolution set to fixed
  • Status changed from new to closed

WG1 voted to accept SRFI 98.

comment:5 Changed 6 years ago by alexshinn

  • Resolution fixed deleted
  • Status changed from closed to reopened

comment:6 Changed 6 years ago by alexshinn

  • Owner alexshinn deleted
  • Status changed from reopened to assigned
  • Summary changed from The calling context to Environment Variables

comment:7 Changed 6 years ago by alexshinn

  • Status changed from assigned to decided

comment:8 Changed 6 years ago by alexshinn

  • Owner set to alexshinn
  • Status changed from decided to writing

comment:9 Changed 5 years ago by cowan

  • Resolution set to fixed
  • Status changed from writing to closed
Note: See TracTickets for help on using tickets.