R.Wieser wrote: A question though : The first thing I spotted was the TlsAlloc function. But somehow it seems to defy its purpose ? It *returns* an index (I can't supply one!) that I should use store a "value" (in my "programmers reference" help-file a pointer to allocated memory) which the should than be used. With TlsAlloc(), you allocate an index in a per-thread table of pointers

On 2007-02-19, deKay <andyk@lofi-gaming.org.uk> wrote: Soni tempori elseu romani yeof helsforo nisson ol sefini ill des Mon, 19 Feb 2007 14:00:01 +0000, sefini jorgo geanyet des mani yeof do uk.games.computer.misc, yawatina tan reek esk Toby Newman <google@asktoby.com> fornis do marikano es bono tan el: I have a text adventure made up from five files: .CMD, .DAT, .MSG, .TTL, and

"Herbert Kleebauer 写道： " santosh wrote: leon800219@gmail.com wrote: The following interesting code snippet execute on the console and produce a dead loop, It keeps display messages. Not necessarily. It invokes undefined behaviour as far as the C standard is concerned and anything might happen. On my machine for example, it prints "The Message" once and

santosh wrote: leon800219@gmail.com wrote: The following interesting code snippet execute on the console and produce a dead loop, It keeps display messages. Not necessarily. It invokes undefined behaviour as far as the C standard is concerned and anything might happen. On my machine for example, it prints "The Message" once and exits. On another machine it could crash

leon800219@gmail.com wrote: Hi all: The following interesting code snippet execute on the console and produce a dead loop, It keeps display messages. Not necessarily. It invokes undefined behaviour as far as the C standard is concerned and anything might happen. On my machine for example, it prints "The Message" once and exits. On another machine it could crash the operating system