Re: Win32 condition variables redux

In any case, Win32 is no natural ground for condition variables as
defined by POSIX.

Therefore, it was wrong for me to try to lay a POSIX layer on top of
Win32.

My abstraction layer won't have condition variables, that's all.

You can't fit a square peg in a round hole...efficiently, that is.

.

Relevant Pages

  • Re: Win32 condition variables redux
    ... Win32 is no natural ground for condition variables as ... > defined by POSIX. ... it was wrong for me to try to lay a POSIX layer on top of ... > My abstraction layer won't have condition variables, ...
    (comp.programming.threads)
  • Re: Win32 condition variables redux
    ... Win32 is no natural ground for condition variables as ... > defined by POSIX. ... it was wrong for me to try to lay a POSIX layer on top of ... > My abstraction layer won't have condition variables, ...
    (comp.programming.threads)
  • Re: Win32 condition variables redux
    ... Win32 is no natural ground for condition variables as ... > defined by POSIX. ... it was wrong for me to try to lay a POSIX layer on top of ... > My abstraction layer won't have condition variables, ...
    (comp.programming.threads)
  • Re: Win32 condition variables redux
    ... Win32 is no natural ground for condition variables as ... > defined by POSIX. ... it was wrong for me to try to lay a POSIX layer on top of ... > My abstraction layer won't have condition variables, ...
    (comp.programming.threads)
  • Re: EOF location?
    ... that will use Win32 semantics may show Win32 features rather than POSIX ... line is 11 characters long; 9 characters and two line-end characters. ...
    (comp.lang.cobol)