With the way we treat animals, I'd say the bat feels lucky too that it ran into a human with no rabies.

There is, but it is no longer C++. It is compiler implementation code which is not in C++ standard. Class (memory) structure is something like this: this_pointer -> [vtable_pointer, dataField1, dataField2, ...] where vtable_pointer points to the table of virtual functions: vtable_pointer -> [func1, func2, ...] So, in theory, you can get access to class (public/private do not make sense in binary) members like this: data1 = *((char*)(*this) + 4); data2 = *((char*)(*this) + 8); // or 12 or 16 depending on the type of data1 Notice, I said in theory, because in practice the compiler aligns data fields the way it wants, even the order matters. So, if you have an integer data field and a double data field you may get something like this: [4 bytes for vtable_pointer, 4 bytes garbage, 4 bytes int, 8 bytes double] There is no simple way to figure out the order and the types of data fields unless you disasm the binary to see which memory locations are accessed from public functions that you know. That's not much, but I hope it'll be helpful. -- modified at 12:28 Wednesday 10th May, 2006

There is a good chinese website http://www.iturls.com/ recommended by such heavyweights as Steve McConnell and Craig Larman. It is chinese but if you click on English at the top left corner you'll get the translation. So you can read the resources in any(both) languages. As to a coder friend ... I would suggest to avoid using word 'coder' when you address a programmer, and God help you if you refer to a software architect as a 'coder'. :laugh:

The real-world problems are not as simple. Example: you develop application with GUI separated from the business logic by Model-View-Controller and you use Observer design pattern to display the state of interest in GUI. Now, the requirements changed and the user wants two GUI, one on the local host and the other on a remote host, both displaying the same information. Observer pattern breaks down here, because of different delays for both GUIs. Which pattern will you use in this case? There are different answers, it may be the combination of other design patterns, but the solution is not unique.

Sounds like the problem is in the driver hands.sys ;P

I think David is he not she, so he would not want to bare with you. :-D

Looks like he has just discovered C++ for himself and it thrills him...

I am not sure what you mean by that but if you are talking about physical memory management then look into Address Windowing Extensions provided in Win API. It lets you lock in some pages in physical memory, for example, when you do OS-level optimization of your algorithms working with reasonably large data sets.

Yeah, most programmers will really "interperate", especially those who post such questions. ;P

I think any named kernel object will do, it does not have to be a mutex.

Speaking seriously, you can build your application with multiple dll files and call functions across different dlls. If I remember correctly, Microsoft used a similar technique in their Win95/98 to hide undocumented functionality of their OS (some kind of dll stubs). It is usually pain in the place to reverse engineer code that makes calls to other binaries. I am not 100% sure but I remember reading somewhere that there are ways of calling a function in dll without exporting its name, just by its binary address (offset) in the file if you know the function signature. This way a person hacking your code can't get much information from dumpbin utility and can't call your function unless he/she can guess all parameter types correctly. Which is not an easy task. Another way is to write a code that overwrites its own binary, but then your antivirus software may start complaining about your program. As a bottom line though, I would think that it'll create more trouble for you than to a person hacking your code. Think twice if it is worth your time.

Can you use ::WaitForSingleObjectEx(...) function?

Isn't 200x200x4 = 160K?

... or use the "state design pattern", which can be implemented in any OO language.

Insert the lines like "temp = temp++ - foo(temp++) - temp++;" throughout your code. Not only people, even compilers will get obfuscated by that! :laugh:

Here is a question to you on C++: Can a class constructor be declared private? If not, explain why. If yes, explain why you would do it.

C/C++ is going to be a better start for him, because he is used to matlab, so he can integrate his C/C++ code with matlab by using matlab mex-functions. P.S. VB is often used for prototyping.

Hi guys, I am looking for some good practical book on agile/iterative software development. I have read some books on XP and browsing some on Scrum but they are not exactly what I am looking for. They describe a general high level idea and do not go into specifics. Ideally I want a book that decribes the process by example, like a story on how the project gets started, what activities are done, and most important what the pitfalls are, how the planning is performed, how risk management is done, how the process gets going etc. What I want is a detailed story about one project in the form of a step-by-step guide. It does not mean I am going to follow all these steps but it'll be more useful than just a discussion on the collection of good practices like: 1) Do TDD 2) Do code reviews and refactoring 2) Do pairs programming 3) Do continuous integration 4) Do timeboxed development ... Any suggestions or recommendations on a book that you have found particularly useful on your projects? Thank you Nick Kisialiou

I can suggest you some resources written by people who have done similar things - SDR through your sound card. You may want to look into the following info (free articles): General articles archive: http://www.flex-radio.com/articles_files/[^] First article talks about sound card based SDR: http://www.flex-radio.com/articles_files/SDRFMP1.pdf[^] How much of expertise do you have in SDR? Are you affiliated with DOD? As far as I know most of SDR projects now are funded through DOD or somehow related to it.

Would be nice to get rid of typos though.