[EMAIL PROTECTED] wrote:
"fragile" - "arguments not vetted, you can crash this if
you don't play well with others"
"robust" - "good faith argument checking done, but there
may be some gotchas left"
"ironclad" - "we've collectively banged on this one REALLY
hard, and are confident that errors will be
pre-empted"
How about applying the SourceForge nomenclature for applications:
1: Planning
2: Pre-Alpha
3: Alpha
4: Beta ("fragile")
5: Production-Stable ("robust")
6: Mature ("ironclad")
> So... should we prefer a style for common/standard library
functions, or at least document which position the author (and
maintainers) took?
How about starting with Carl's style guide <
http://www.rebol.com/users/scrstyle.html >, and extending from there?
-T.
