Would have been much more helpful if you had gone through how to construct the CMake,Makefile and the compiling strategy, eg. - compile against libs (static & dynamic options) or - encorporate the gtest source into the application under test... Both require different cmake,makefile setups.
yeah but the video is title is clearly "c unit testing introduction" not "how to unit test" w/ google test (if it was "tutorial" maybe but its just not this type of content)
Very nice and informative video. Thanks!!! I wanted to ask what kind of editor are you using? I know at some point you said 'vim'. But what's that opening tab on left side, by "CTRL+O"?? Is it TMUX? how to do it any link to set it up? Thanks again.
sweet and to the point on how to use c with google test framework, amazing. I only have one issue you called it "care" instead of "char" let the flame war begin!!! Really though great explanation!
@@KrisJordan how do you pronounce "stdlib" std lib where the lib is like liberty , or the lib like library? lol we have this discussion at work. if we go by your answer to previous question you pronounce stdlib like library
@@EdwinFairchild great question. I honestly don't know that there's a correct answer here, but I would believe it if the original Unix programmers went with "libe". I have always read it in my head as just "lib" even though I know it's short for library.
could you please give the previous lesson's link? kind of lost in your you tube channel video play lists and was not able to figure out where are previous or next videos.
One minor observation: in line number 9 of copy.cpp, should not the dst be allocated size(src) + 1 bytes? Otherwise while writing a null terminated string, the next byte on the stack would be overwritten leading to stack corruption! >> char dst[sizeof(src) + 1];
