   20 issues of porting C code on the 64-bit platform
  Comments for the article 20 issues of porting C++ code on the 64-bit platform
  The link on the main page to this article takes me back to the main page.   ;  Yes I know, which is why I posted a news item. The problem will resolve itself once the main page updates again - I have no idea when but within 4 hours of the article being posted.   ;  A very valuable read. Thank you very much. I'm about to port a medium-sized project (~150000 lines of code) to Win64 and now I've grown a new fear of innocent-looking math expressions :-)   ;  I have just started to read this article and correct me if I am wrong, but C++ does not have types intptr_t and uintptr_t. I believe the next standard defines them but not the current.   ;  That doesn't make any information about them any less useful...   ;  Nice article.Quote:Original post by coldacidThat doesn't make any information about them any less useful...Do you not think? what about section "6. Storing of pointer addresses" or "14. Mixed use of simple integer types and memsize types"http://www.informit.com/guides/content.aspx?g=cplusplus&seqNum=223&rl=1Quote:The latest C standard ISO/IEC 9899 (known as C99) introduced quite a few core and library extensions that aren't supported in ISO C++ yet. The C++ standards committee is working with WG14 (the ISO C standards committee) to resolve these incompatibilities. The aim is to adopt C99 features that can be useful or necessary in C++, while rejecting features and library extensions that C+ doesn't need. Here, I present two of these C99 features: long long and intptr_t, and discuss their future in C++.;  very nice article!I would love to read similar articles for other types of bugs (ie. OpenGL bugs, multi-threading bugs, exceptions bugs, memory bugs, etc...)   ;  nice article indeed.But what is ILP, LP, LLP ?? Author does not explain anything what these acronyms stand for..   ;  This is one of the best articles in the last few months! Hopefully this quality will continue!   