3 Apr
2012
3 Apr
'12
8:23 p.m.
On 04/03/2012 10:18 PM, Paul Mensonides wrote:
Ticket closed--not a bug.
It *happened* to work in older versions primarily because the tuple implementation had a backdoor to all () as a nil tuple is *some* cases. However, () is not a nil tuple--particularly not in C99+ or C++11+. There is no such thing as a zero-element array (or tuple), and the array implementations defer to the tuple implementations. (0, ()) is invalid, as it should be (1, ()) just as with (2, (,)) and (3, (,,)).
If there was a nil array, all of the array operations would have to go out of there way to handle it specially.
Conclusive. Thank you for explaining. Regards, Jan.