Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.c++.moderated    |    Moderated discussion of C++ superhackery    |    33,346 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 33,218 of 33,346    |
|    Daryle Walker to All    |
|    Re: Is "T[N][]" (or "T[N][][M]") indirec    |
|    29 Sep 13 19:17:27    |
      From: darylew@googlemail.com              On Sunday, September 22, 2013 8:30:03 PM UTC-4, Daniel Krügler wrote:              > I do not understand what you mean by direct or indirect means in this       > contact. The standard clearly says that such types are not allowed, it       > doesn't distinguish direct or indirect ways to form them.              Where the Standard talks about adjacent array specifications, there are two       possible meanings:              1. The specifications are lexically adjacent: "using Z = int[][N]"       2. The specifications are logically adjacent: "using X = int[]; using Y = X[M]"              I wasn't sure of which meaning. But you state that "adjacent" is logical; that       making an array of an array of unknown bound indirectly via composing type       aliases isn't allowed.              I found a C++14 draft, and it solves the problem unambiguously. It explicitly       states that an array of unknown bound cannot be used as an array element type.              Daryle W.                     --        [ See http://www.gotw.ca/resources/clcm.htm for info about ]        [ comp.lang.c++.moderated. First time posters: Do this! ]              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca