??? From above
??? The author(s)
??? the draft/final/withdrawn status of the SRFI, information on how
to subscribe to its mailing list, and important dates in its history.
The editor will add this section.
??? abstract, preferably shorter than 200 words. Please outline the
need for, and design of, the proposal.
??? Optional section that may point out things to be resolved. This
will not appear in the final SRFI.
??? detailed rationale. This should be 200-500 words long. Please
explain why the proposal should be incorporated as a standard feature
in Scheme implementations. List related standards and SRFIs,
including dependencies, conflicts, and replacements. If there are
other standards which this proposal will replace or with which it will
compete, please explain why the present proposal is a substantial
??? detailed specification. This should be detailed enough that a
conforming implementation could be completely created from this
??? explanation of how it meets the reference implementation
requirement (see process), and the
code, if possible, or a link to it
Source for the reference implementation.
??? credit where it is due
Copyright (C) ??? (201?). All Rights Reserved.
Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files
(the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
Editor: Arthur A. Gleckler