Mon premier blog

Memory as a Programming Concept in C and C++ Frantisek Franek
Publisher: Cambridge University Press

Pointers and casts are the sharpest of the knives, and many people have run into difficult bugs in those areas. Why do people still write in C/C++? The reason why some programmers think C++ is superior to C is because they're bad programmers. Part 1 provided a quick start guide in using the debugger. December 19, 2007 at 6:50 pm · Filed under Programming. As many people have said over the years, C and C++ are sharp knives. However, there are still many C++ programmers out there so there still some PL researchers working on C++, and it is a nice/uncrowded niche if you can stomach it. Many of these efforts, notably the C++0x concept design, have run into trouble by focusing on the design of language features. Now I can guess the program must have been written in a language where programmer had to do memory management himself. I expect that transactional memory will never work in the C/C++ world; it simply costs too much. Java generally doesn't have those problems. Introduction This article is a continuation of the C/C++ Visual Studio Express debugger series. I will assume that you have already read the previous posts in the series, but I will also put in-line links to any important terms or concepts that you might need to know about to make sense of what you're reading. Re "hierarchical & sequential": con/destructors and RAII ultimately tie memory and resource lifetime to sequential control flow through hierarchically nested scopes. Alright, let me rephrase this so you don't immediately start flaming me. Since it is a LED-Box, it must be a C or C++ prgram in embedded environment.