Thanks for the info Nicholas :-) Nish Regards, Nish Native CPian. Born and brought up on CP. With the CP blood in him.

answer: Pointer to a null-terminated string of 16-bit Unicode characters. Aizik Yair Software Engineer

Hi, You are right!!! Following is the Macro Jeffrey Richter wrote. // The normal HANDLE_MSG macro in WINDOWSX.H does not work properly for dialog // boxes because DlgProc's return a BOOL instead of an LRESULT (like // WndProcs). This adgHANDLE_DLGMSG macro corrects the problem: #define adgHANDLE_DLGMSG(hwnd, message, fn) \ case (message): return (SetDlgMsgResult(hwnd, uMsg, \ HANDLE_##message((hwnd), (wParam), (lParam), (fn)))) And this Macro is collected in Win95adg.h which is included in source file. Thank you Best regard. I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.

A loop is the whole thing, an iteration is once through the loop. for (int i = 0; i < 10; ++i) { if ( 5 ==i) continue; cout << i; } will print 012346789. for (int i = 0; i < 10; ++i) { if ( 5 ==i) break; cout << i; } will print 01234. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. And you don't spend much time with the opposite sex working day and night, unless the pizza delivery person happens to be young, cute, single and female. I can assure you, I've consumed more than a programmer's allotment of pizza, and these conditions have never aligned. - Christopher Duncan - 18/04/2002

NicholasCougar wrote: small *p =(small) b; This won't even compile. You are attempting to assign small to small*,( via unsafe casting). Nish The posting stats are now in PDF:- http://www.busterboy.org/codeproject/ Feel free to make your comments. Updated - May 04th, Saturday

NicholasCougar wrote: Can you explain the code for me in detail? I mean word by word. There is no need to explain it more than to say that they cast a pointer to a member function into another type of function pointer. But to spell it out, I think it's spelled something like: Emm eff see sucks, partially because Microsoft lagged ~5 years behind the competing C++ implementation, and partially since the AFX (remember, it was Application Framework eXperimental - probably with emphasis on the experimental part) group wasn't too good at neither design nor C++. Sure, using the inferior MS compiler they actually managed to make something work, sometimes... But the price we got to pay for this was un-typesafety that has wasted several hundred of thousands of developer hours around the globe to date.

1. Nothing special. The DllMain entry point is called for each newly created thread with fdwReason set to DLL_THREAD_ATTACH. 2. No race conditions occur as calls to DllMain are serialized by the system. As a corollary, threads cannot be created inside DllMain. 3. TLS routines can allocate and deallocate indexes that are local to each running thread. These usually are used to map some dyamically allocated memory. Check MSDN article Using Thread Local Storage for details. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

Once is enough, asking over and over only annoys people, especially when the first ask is only two posts down. You want to look at function pointers, that is how callbacks work and it's just as easy to impliment your own if you want to. Christian The tragedy of cyberspace - that so much can travel so far, and yet mean so little. And you don't spend much time with the opposite sex working day and night, unless the pizza delivery person happens to be young, cute, single and female. I can assure you, I've consumed more than a programmer's allotment of pizza, and these conditions have never aligned. - Christopher Duncan - 18/04/2002

Yes as long your application is still running! ;P A callback function is "not much than calling convention". In fact WINAPI and CALLBACK is the same __stdcall. Do not confuse CALLBACK function and RPC! int __cdecl _tmain(int argc, _TCHAR **argv, _TCHAR **envp) { myDebugCallback( TEXT("Hello world..." ) ); } void CALLBACK myDebugCallback(LPCTSTR strMessage) { _stprintf(TEXT("Message: %s\n"), strMessage); } "Dirty hands lead to important discovery..." - Thomas Edison

Braulio Díez wrote: Todos somos buenos amigos de la gente que escribe buenos libros Oh si, claro! Ahora! Pero que paso en escuela? :) Braulio Díez wrote: Es muy duro escribir un libro ?, Me refiero a si es una tarea a la que te tienes que dedicar 100 %. Cono mijo. No puedes imaginar. Es ridiculo a veces. La cosa es que los publisher no quieren intender que muchas veces estamas escribiendo en algo que esta in beta y no funciona bien. Tampoco no tiene instrucciones ni nada. Pero ellos todavia esperan que nosotros comple con las fechas. Muchas veces el resultado es que tenemos que avanzar y terminar algo que sabemos no es nuestro mejor trabajo. En terminos de horas, si toma un monton de tiempo escribir un libro y los publisher actua como el libro es tu unico trabajo cuando normalmente es algo que hacemos en la noche. Te digo, no es un trabajo facil. Pero la cosa es que me gusta ayudar a la gente y en eso recibo me pago. Cheers, Tom Archer Author, Inside C# Please note that the opinions expressed in this correspondence do not necessarily reflect the views of the author.

It basically allows the statement from the previous line to continue to the next line. Mainly they are used in macros like Christian Graus has explained above. There are not very many other useful uses for this operator. Build a man a fire, and he will be warm for a day Light a man on fire, and he will be warm for the rest of his life!

NicholasCougar wrote: For example, CRuntimeClass, Message Map and RTTI etc. Heck, I must be in trouble - I've been programming C++ since late 92 and I've never needed to know how CRuntimeClass and RTTI work. :-D You can learn more about MFC in the book MFC Internals. Michael :-)

Use HTML tags when typing your post. Note, not all tags are recognized. Plus, you can use special tags like <pre></pre> to display source code, like this: // This is a comment int nFoo = 43; /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com

:: is not only used to specify superclass methods. It can be used to: Specify methods in your own class, Specify class methods (static) in any class, Resolve namespaces, Reference instance and class member variables, Specify any nested classes, structs, enums, etc. All it really does is give the location of a specific item. E.g. std::cout // specifies that cout is in the std namespace class C { enum E { num1 }; static void sfunc(); }; void func(C::E num); // specifies the type E in class C func(C::num1); // calling function with class C's enum value num1 C::sfunc(); // calling class C's static function sfunc() etc... Hope that helps.

Ravi Bhavnani wrote: I think you mean "synchronized".    Quoted from MSDN docs: "To ensure thread safety, the heap has to serialize access to itself" and "The default behavior is to serialize access to the heap".  True, a synchronization object is used for this.    The difference is that "Serialization" basically means "one thing after the other, and one at a time".  "Synchronization" usually involves multiple threads at work, where two threads can actually try to manipulate something at the same time.    Although I agree as much as to say that the two terms are often used interchangeably...    Peace! -=- James.

moliate wrote: I am still a bit unclear about non-virtual member functions, however. I assume that they are not replicated in every object instance? Is there a separate pointer like the vtbl for them?    IIRC, neither virtual or "normal" member functions are replicated for every instance of a object.  The old idea of "one copy of code, multiple copies of data" comes to mind.    Yes, if the object contains virtual methods, then each instance of the object gets a copy of it's vtable.  This is needed for polymorphism.  But it is just the vtable that is in the memory layout of the object, not the code for the functions themselves.  That code still exists in one place, and the vtable is used to get to them. moliate wrote: Could you help me to become a better C++ programmer?    That is what this site is (supposed to be) for!     :P    (Note, I used "object" above instead of "class" because both classes and structs can contain member functions...)    Peace! -=- James.

Hi CG, Richter's advice was that we should use _beginthreadex if we plan on using CRT functions inside our thread. But if we are not, then we might as well use the API calls to start threads Nish _ If I am awake and my eyes are closed, it does not necessarily mean that I am thinking of naked women._

The codes are from Multithreading Applications in Win32 written by Jim Beveridge & Robert Wiener First, please study the second and sixth parameters. unsigned long _beginthreadex( void *security, unsigned stack_size, unsigned (* start_address)(void *), void *arglist, unsigned initflag, unsigned *thrdaddr); HANDLE CreateThread( LPSECURITY_ATTRIBUTES lpThreadAttributes, DWORD dwStackSize, LPTHREAD_START_ROUTINE lpStartAddress, LPVOID lpParameter, DWORD dwCreationFlags, LPDWROD lpThreadId); According to Jim Beveridge & Robert Wiener' point of view, the function _beginthreadex() is the coat of CreateThread() and the types of its parameters have been changed for the sake of being adoptable to other operation system. While, as the CloseHandle() must be called at last, programmers can't get rid of "window.h". Another side effect is, though C compiler makes no difference between DWORD and unsigned (in fact unsigned int), C++ compiler doen't think so. As CreateThread() is inside _beginthreadex(), its parameters are less likely to be modified. Defining parameters according to CreateThread() is smarter. Since the parameters must be accepted by _beginthreadex(), the codes we discussing must appear there. The true meaning of the codes is: force type convertion before calling _beginthreadex(). the following are codes in all: //The beginning of codes #define WIN32_LEAN_AND_MEAN #include #include #include #include typedef unsigned (WINAPI *PBEGINTHREADEX_THREADFUNC)( LPVOID lpThreadParameter ); typedef unsigned *PBEGINTHREADEX_THREADID; int main() { HANDLE hThread; DWORD dwThreadId; int i=0; hThread = (HANDLE) _beginthreadex(NULL, 0, (PBEGINTHREADEX_THREADFUNC)ThreadFunc, // Attention, Plz (LPVOID) i, 0, (PBEGINTHREADEX_THREADID) & dwThreadId // Attention, Plz ); if(hThread) { WaitForSingleObject(hThread, INFINITE); CloseHandle(hThread); } return EXIT_SUCCESS; } DWORD WINAPI ThreadFunc(LPVOID n) { // Do something... return 0; } //The end of codes My opinion