C++0x language feature checklist - Page 2
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Page 2 of 2 FirstFirst 12
Results 16 to 18 of 18

Thread: C++0x language feature checklist

  1. #16
    Join Date
    Nov 2008
    Location
    Netherlands
    Posts
    77

    Re: C++0x language feature checklist

    @joncaves

    im sorry for not being pecific but i wasnt talking about template specialization i was talking about defining variables... Tho its been a along time since i used "typename<> variable".
    Sorry again for not being pecific. Im not sure if its any diffrent now from the last time that i used VC++ with default template parameters

    And your right there is a work around but its really annoying using ::T bit, and i get tangled in giving the classes the name i wanted to give.

  2. #17
    Lindley is offline Elite Member Power Poster
    Join Date
    Oct 2007
    Location
    Fairfax, VA
    Posts
    10,893

    Re: C++0x language feature checklist

    The only attribute I've ever used is GNU's "unused" to avoid a warning on static functions that don't get called. At present I don't believe VS2005 warns for that, so I haven't needed the MS version. That said, if there *were* a standard specification for such things, I might use them more often.

    One of the things I hate doing is writing code that ties me to a particular compiler. I always #ifdef such code and provide alternatives when it's necessary, but that can get messy. So anything that reduces the need to do that is a good thing.

  3. #18
    Join Date
    Mar 2002
    Location
    NY, USA
    Posts
    12,097

    Re: C++0x language feature checklist

    I have to agree with Lindley on this one [yes, it does happen. ].

    For the "standard" attributes which have a direct (or very close) mapping to the existing Visual C++ attributes, it would be a BIG help if the standard syntax was supported [this should primarilty impact the lexical analysis and not the internals of the compiler].

    For those which do not match, having them parsed and either generating a "non-supported" error, or an "ignored" warning (ideally configurable between the two) would be a great help in keeping source code "clean".
    TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
    2008, 2009
    In theory, there is no difference between theory and paractice; in practice there is.

    * Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions
    * How NOT to post a question here
    * Of course you read this carefully before you posted
    * Need homework help? Read this first

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Windows Mobile Development Center


Click Here to Expand Forum to Full Width

This is a CodeGuru survey question.


Featured


HTML5 Development Center