But 8.17 has: int j = { "A", "B", "C", "D" }; { >> {j}} // generates stream "A" "B" "C" "D" { << byte {j}} // generates stream "D" "C" "B" "A" (little endian) { << 16 {j}} // generates stream "C" "D" "A" "B" { << { 8'b0011_0101 }} // generates stream 'b1010_1100 (bit reverse) { << 4 { 6'b11_0101 }} // generates stream 'b0101_11 { >> 4 { 6'b11_0101 }} // generates stream 'b1101_01 (same) { << 2 { { << { 4'b1101 }} }} // generates stream 'b1110 All those lines except the first ARE examples of usage outside an assignment-like context. Shalom > But "int j = {>>{a,b,c}};" is an assignment-like context. The question > is whether a streaming_concatenation can occur outside of such a > context. There are no examples of such usage in the LRM, and I have > trouble reconciling the error messaging requirements of 8.17 with the > viewpoint that a streaming_concatenation has a self-determined type. I > contend that a streaming_concatenation is more closely analogous to an > assignment_pattern than to a concatenation. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu Jan 4 09:55:57 2007
This archive was generated by hypermail 2.1.8 : Thu Jan 04 2007 - 09:56:04 PST