Search:

you're adding to the confusion here.

[list=1]
for certain platforms, where there's no underlying OS support for threading (dude_1967 mentioned microcontrollers - an easier example could have...

this is the ONLY general way actually - you can have some particular cases in which you know beforehand that only one thread will pause, set signal masks accordingly so that only that thread catches...

that´s a bad policy - better leave the memory management for the threadData completely to the dialog object:


add a threadData member
initialize it inside the onInitDialog() function
pass...

it´s a bad design choice to wait for something while processing an event - it blocks the event-processing queue and the app. becomes unresponsive. a better choice would be using a CThread (or a...

1. unless it's a typo, your prototype doesn't match the implementation - the argument has to be a pointer.

2. template code must reside in the header file - so you probably want to replace the...

actually, if you're interested in playing around with Linux use a 'live cd'. the most popular choice is Knoppix, but SuSe and Mandrake also offer a live-cd version of their distros (SuSe Live and...

that is because most X apps on't use them ... they're 'evil' :D the recommended practice is 'use selections'



you need some determinate googling or fiddling through X reccomendations to figure...

try doxygen

the X clipboard requires the X server (obviously :p ) See this link about cut buffers:

http://tronche.com/gui/x/xlib/utilities/using-cut-buffers.html

otherwise, use selections. you'll have to...

not if you're not their employee ;)

I apologize for the imprecision - that was referring to precompiled objects/classes that need to be linked in (the OP had a linking problem due to cout). As you already said, STL resides usually only...

the compiler will usually have a list of standard search paths; same goes for the linker. in particular, in Lunix g++ (the c++ compiler) will add to the standard include search path (/usr/include)...

you can use the rdstate() member function to read the state of the stream.

it's the intended behavior. Constructors don't return error codes so if you do a one-step (i.e. in the constructor) initialization of some resource and that fails, the most dirrect way of announcing...

let me spell it out then. you said:


and you were wrong - there's no such interdiction in the C++ standard.



My bad - the quote I gave was from Appendix C (C1.6 Clause 8: Declarators)....

behavior will depend on the type of object and the type of function you call (as it should be obvious from the previous POD-nonPOD discussion). However, you can allocate memory (via malloc(),...

you are mistaken. void is a perfectly legal C++ function argument - I dare you to show me the exact paragraph in the standard that says different. however, if you DO look at the standard, you'll see...

short answer, yes. the body of the inlined function has to be in the same scope as the place where it gets inlined. (when in doubt, check with the standard: 3.2.4. An inline function shall be defined...

or install a terminate() handler with set_terminate()

otherwise, just throw an exception object for catch to receive. however, throwing *this would be a serious mistake, as it's not completely...

well, outside of the windows world it appears that CLOCKS_PER_SEC=1000000L, so the counter overflows in little more than one hour. and no, there's nothing (portable) you can do about it.

from the c++ standard, 15.1 (Throwing an exception):


6. A throw-expression with no operand rethrows the exception being handled. The exception is reactivated with the existing temporary; no new...