This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.


[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]

Re: unnecessary typename requirment? (apparently not!)




joe buck wrote:
> ISO C++ requires that you use the typename keyword here.  I'm sorry,
> but you're just going to have to get used to doing this.  "But it worked
> with compiler X" -- there are much fussier compilers around.

mike stump wrote:
> If management won't let you use a ANSI compliant compiler and forces
> you to use one that isn't ANSI compliant, then maybe you should
> consider switching jobs (or management).  :-)


wow.  in less than 30 minutes i got three responses from the egcs
list, went to management to see what they thought, and now we can use
egcs!  :)  Thanks for the help!


FYI:
It helped that we found a very explicit paragraph about why KCC
handles this new ISO C++ requirement in this way.

-----------------------------------------------------------------------------
Implicit use of keyword typename

ISO recently introduced a keyword typename. Its use is required inside
templates for certain contexts by the ISO rules, as demonstrated by
typename.C. However, it is so recent that very few codes use
it. Therefore, by default, KAI C++ infers where the keyword typename
should have been used. To turn off this inference, use the option:

        --no_implicit_typename

The option --strict also turns off the inference. If you want strict
ISO except for typename, use the options --strict --implicit_typename.
------------------------------------------------------------------------------
    found at:    http://www.kai.com/C_plus_plus/online_doc/migrate/



noel


here we go typenaming away...