About the features function, draft 7 states:
"Returns a list of the feature identifiers which cond-expand
treats as true."
Kawa has an open-ended set of feature identifiers, in that
class-exists:CLASSNAME is true if the java class CLASSNAME exists
in the compile-time environment. This functionality has similar uses
as the new library clause, and could perhaps be replaced by the latter.
Still, it is unclear if an implementation with a feature-set pattern
like class-exists:CLASSNAME is strictly conformant. Perhaps I could
just say class-exists:CLASSNAME is not a feature-name, but a
different kind of extension to cond-expand.
What are the use cases for the features function, except perhaps
informational, for humans?
--
--Per Bothner
[email protected] http://per.bothner.com/
_______________________________________________
Scheme-reports mailing list
[email protected]
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
