Hi, Bradley Lucier <[EMAIL PROTECTED]> writes:
> It > could be said by analogy that the proposed R6RS libraries offer > *only* a (char*) (more tamed than in C), which solves one small > class of problems (how to allow semi-portable, low-level translation > between data types that can be considered sequences of bytes; how to > write I/O device drivers; ...) while completely ignoring a much > larger and more important class of problems (allowing fast and memory- > efficient access to large arrays of homogeneous numerical data). Personally, I don't think of bytevectors as an SRFI-4-like type of homogeneous vectors, in which case the concerns you raise would be valid. Instead, I really consider them as a "portable `char *'", designed to facilitate binary I/O---although I do not know for sure whether this was the authors' intent. If this is the case, the reasons why non-aliasing is not required for `char *' in C99 (as you said) would probably also apply to bytevectors. Thanks, Ludovic. _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
