On Mon, 26 Nov 2007, Manuel López-Ibáñez wrote: | On 25 Nov 2007 21:26:21 -0600, Gabriel Dos Reis <[EMAIL PROTECTED]> wrote: | > | > I have no implementation strategy at the moment. But I do have a | > request: Please, whatever you do, please, don't make it noisy with | > template codes and `reasonable' codes. (We have had PRs for that | > behaviour in template codes). | > | | Well, the goal is to define a syntax to allow avoiding the warnings. | See my proposal previously in this thread about why I think an | explicit cast would be better than using 0U in template code. Yet,
I'm no believer in `explicit cast'. | with template code perhaps we could just avoid warning completely but | I don't see how to check at the point of warning that the type comes | from the instantiation of a template. If there is some way to check | that that I have missed while looking into this, please let me know. Template are tricky. During phase one, we usually do as much of semantics analysis as we can, e.g. non dependent things get checked. In phase two, we check only things that were dependent. So, if the enclosing function is generated from a template (and there is a way to know that), then we are checking something that was dependent in the first place. -- Gaby
