HTEventList_loop

Hmmm, this *seems* to be a bug, but you implementors will know better than
I. The !WWW_WIN_ASYNC version of HTEventList_loop is coded as:

     do { <the event loop> } while (!HTEndLoop);

We just ran into a case where a user-established AFTER filter had called
HTEventList_stopLoop() *before* HTEventList_loop() had been called. In this
case, the program hung in the event loop infinitely. This is on a Mac using
CWGUSI for sockets. It seems that it would be more defensive to code the
event loop:

     while (!HTEndLoop) do { <the event loop> };

Yes? No?

regards,
-jim