The reason being is executable viruses have a nasty habit of hiding themselves from attempts to find them. File system reads/writes get redirected to what looks like good data, so your attempts to find them will actually find nothing.
It's far better to rely on actual anti-virus software, which protects the actual file system code from attempts to redirect/replace it. That's something your code cannot do when a user launches it.
I downloaded it built it debug x64 and as I was stepping thru that code it got an exception it was somewhere in MFC code the call stack indicated it was from an Additem Ill go back and try to fix it up thank you
-first, the dwSemCount value si always printed as 0, even if the semaphore works fine
-second, incrementing the counter with ReleaseSemaphore function from inside of thread doesn't working, I can't explain why.
Hi . Recently i've got to make a game called gomoku between two players and I don't know where to start. Could you please assist with the steps or at least a C++ code for the Gomoku game with comments so that I can at least be able to follow what has been coded.
The first thing you need to do is to study the game so you understand the rules. You can then start to figure out what each step of the game can do. From that you should be able to create a basic design document. Until you have done all that there is no point in thinking about actual code.
I have an block of code which already defined classes. And I want to define their cardinalization. Searched through the internet and books for 2 days but could not find anything. Please help me. Help my poor brain .
I haven’t encountered the notion of “cardinalization” in programming. The only thing close is “cardinality” and that refers to the number of objects of a certain class that are or can be created.
In this context the only frequently encountered case is the case of “singletons”, objects they you need to create only once (Google “C++ singleton” and you’ll find tons of information and examples). Otherwise there is no language construct that limits you to create only 3 or 10 objects of a certain class. It is up to your program to limit that.