Re: f0dder's Fabulous Wait States.

Don't mind if I laugh, blocking is internet technology, GetMessage()
has been around since win 3.0 and it still does the same thing, it does
not return unless there is a mesage in the que. Same comment as before,
"Not return != blocking".

Like it or lump it a message loop is a polling loop and a WndProc is
part of a bigger polling loop run by the OS. Polling tecnology is
superior technology and proven at an operating system level by the
internal structure of the Windows messaging system. Without it no GUI
app would run.

Noting that Donkey posted the version that was supposed to be the
"correct" way to call a wait state, my criticism is perfectly valid and
he should fix it. Noting that you are defending his badly written
broken function, I guess you ae as ignorant of the right way to call a
wait state as he was when he wrote that function.

Make sure you shut a timer next time you copy a piece of my posted code
and try and apply it. Just another sloppy programming technique from
someone who does not know any better.

Regards,

hutch at movsd dot com

.

Relevant Pages

  • Re: f0dders Fabulous Wait States.
    ... > said something like the GetMessage() function remains "suspended" ... "blocking" will make sure your thread takes 0% CPU ... and "block waiting" (in windows terms) means removing your thread ... > it is a data retrieval function, not a polling loop and it is ...
    (alt.lang.asm)
  • Re: Hutch, give it up.
    ... "blocking" function in a polling loop. ... When you manually code a polling loop that does not have an automatic ... I'll let you in on another little secret: ... a duration of ZERO to yield, running ANY task that did something ...
    (alt.lang.asm)