Vincent Manis scripsit:
> R7RS, therefore, needs to accommodate these three audiences. I'm not
> sure about which kind of presentation is best for this, but probably
> the most important thing the R7RS Editors (who may or may not be a
> smaller group than the set of WG members)
That's up to the WGs, but I certainly hope so. A committee for
*deliberation*, such as the WG, should be as large as practicable without
getting killed by N^2 effects; a committee for *action*, such as the
editing sub-committee, should be as small as practicable while still
getting the work done.
> A language that doesn't have hash tables as a predefined
> datatype will get slammed by the Perl/Python/Ruby crowd AND the Java/
> C# crowd, so pointing at a SRFI or saying that the implementation
> might provide hash tables or commenting that any computer science
> student who's taken data structures can implement them will not
> inspire confidence in a prospective Schemer.)
One thing I'm thinking of is writing a map interface SRFI that would
allow you to use (but not construct) any sort of map, whether a mapping
function, an a-list, a symbol p-list, a hashtable, a tree, or what not.
Perl hashes are hash tables, but no Perl code can safely rely on this
fact; Python dictionaries can be anything. This is not a complete
solution, but it would help.
--
Don't be so humble. You're not that great. John Cowan
--Golda Meir [email protected]
_______________________________________________
r6rs-discuss mailing list
[email protected]
http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
