By the way, I apologize for an error in the subject line and body of my original post. I referred to fxcopy-bit-field, which is the procedure I was implementing when I realized that the specification of fxbit-field contains an arbitrary (and, in my opinion, idiotic) restriction on its third argument.
One can make a legitimate argument (from portability) in favor of the similar restriction on the third argument of the fxcopy-bit-field, fxrotate-bit-field, and fxreverse-bit-field procedures. Will _______________________________________________ r6rs-discuss mailing list [email protected] http://lists.r6rs.org/cgi-bin/mailman/listinfo/r6rs-discuss
