You mentioned having your own "standard library", perhaps you have some conflicts that can be resolved using namespaces?
Davie21240
Posts
-
Code analysis sucks -
Code analysis sucksIf you are coding in C++, perhaps you should really examine you code, for example, using assert -- you might want to use the Google Test Framework and use their ASSERT_ macros along with gMock so you don't have to pollute your code with something that is normally reserved for debugging and not for a release version. I am wondering if you are a "C-style" developer, which might be causing some of your angst.:java:
-
Bill Gates: ‘Government needs to get involved’ to regulate big tech companies -
Bill Gates: ‘Government needs to get involved’ to regulate big tech companies -
Bill Gates: ‘Government needs to get involved’ to regulate big tech companies -
Bill Gates: ‘Government needs to get involved’ to regulate big tech companies -
Bill Gates: ‘Government needs to get involved’ to regulate big tech companies -
How often do you like to compile?Think everyone develops their own habits naturally for me, as a Linux C/C++ developer, if it's maintenance I am doing fairly frequently as I am making my code changes. We work with eclipse and CMake so it's easy just to hit the build button. But when I am adding a new feature and looking at my class diagrams (Dia, visio type). It normally happens at the end after I code a nearly complete class and add it to the CMakeList.txt file. Think if people created well fleshed out class diagram first, it would happen less often when you start coding it, but then more often afterward.
-
Does anyone miss programming in old languages?I have a warm spot in my heart for Ada. Think more teams should consider Ada2012 for their next project at least if it's realtime embedded development.
-
Does anyone miss programming in old languages?I have a warm spot in my heart for Ada. Think more teams should consider Ada2012 for their next project at least if it's realtime embedded development.
-
Questions on getting into the coding world and gig workThat's exactly my point. The idea is to help the student decide whether they have the aptitude for the profession really early before any real investment is made. When I was a student we learned assembly language. Writing code has lots to do with personality, it's all about solving puzzles, and sometimes you spend lots of time trying to figure things out. If you have "the personality" you will certainly enjoy this book, perhaps people should read this book before they decide to take a software class: The Bug by Ellen Ullman
-
zero-sized array in struct/unionpretty sure you could just use char* name; since the array size is 0.
-
Questions on getting into the coding world and gig workThe idea is to move on to the "candy" languages after you fully understand pointers. The idea is to master "pointers", get a feel for some of the most difficult concepts early. When I went to school the professors were very strict when they taught statics and dynamics for the engineers; the idea was to separate the "wheat from the chaff", early in the program. For example, my younger brother said he got a "D" on his first 4 week exam, because he forgot the -> vector symbols on his equations, even though every answer was correct with all the work shown. The idea is to let the student determine if the subject matter is right for them very early on, so they don't make too much of an investment and bail later than they could have.
-
Questions on getting into the coding world and gig workEnroll in a C programming class at your local community college. NOT C++, NOT C#, NOT Java, NOT python, etc. Just plain old "C" MAKE SURE IT'S A NORMAL CLASS WHERE YOU SIT IN THE CLASSROOM WITH THE INSTRUCTOR AND FELLOW STUDENTS. After you finish the class. Decide if you REALLY like the subject matter. Then take another, perhaps C++. Then after you finish the class decide if you REALLY enjoy the subject matter. If the answer is NO, then go to plan B. If the answer is YES enroll in the "program" for Comp Sci majors where you can matriculate to the nearest state university or 4-yr college that is affordable and near your house. Best of luck and with kind regards, :thumbsup:
-
Code editors rantMy son likes using Atom. Nice.
-
Code editors ranthate using the mouse, my arm gets repetitive motion injuries :cool: :java:
-
Overriding problemYou might not need to make them virtual.
-
How to resolve: error LNK2001: unresolved external symbol "public: static void *Definitely remove the line: using namespace std; My advice: NEVER do that.
-
Of Code and CommentsPersonally, I try to use *doc* style (Javadoc, Doxygen, Pydoc). For C/C++ only in the header files. However, I only comment the stuff I think is helpful to maintain the code. Most developers forget to modify existing code comments, so there's no need to be pedantic and comment about what is clearly gleaned from the source:java:.
-
Programmer vs software engineerbecause I do lots of software maintenance and I am usually fixing stuff that doesn't work :cool: :thumbsup::thumbsup::thumbsup: