threads without threads

[sindica]

Hello,

I have a counter loop which actually executes in a different thread.
The thread is there to check for a connection time out. However due to
some limitations, I cannot use pthreads or any OS dependant components
(my code should run on both windows and linux). I have to relegiously
stick on to ANSIC standard. Does ANSI C provide any inherent function
which could accomplish what I intend to do. Or putting it otherway,
how can I just deviate from my direct execution path and just return
to it after a stipulated time has elapsed.

~saraca

 

[Joona I Palaste]

(e-mail address removed) scribbled the following:

Hello,

I have a counter loop which actually executes in a different thread.
The thread is there to check for a connection time out. However due to
some limitations, I cannot use pthreads or any OS dependant components
(my code should run on both windows and linux). I have to relegiously
stick on to ANSIC standard. Does ANSI C provide any inherent function
which could accomplish what I intend to do. Or putting it otherway,
how can I just deviate from my direct execution path and just return
to it after a stipulated time has elapsed.

ANSI C provides no thread support of any kind at all. As far as ANSI C
is concerned, the world is a single thread.

 

[Thomas Matthews]

Hello,

I have a counter loop which actually executes in a different thread.
The thread is there to check for a connection time out. However due to
some limitations, I cannot use pthreads or any OS dependant components
(my code should run on both windows and linux). I have to relegiously
stick on to ANSIC standard. Does ANSI C provide any inherent function
which could accomplish what I intend to do. Or putting it otherway,
how can I just deviate from my direct execution path and just return
to it after a stipulated time has elapsed.

~saraca

As far as sleeping goes, there is no support for task suspension
in the ANSI C language.

However, you _could_ write a wrapper function for your platform
specific code. Just supply different implementations based upon
the platform. This is what many cross platform project do.

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.comeaucomputing.com/learn/faq/
Other sites:
http://www.josuttis.com -- C++ STL Library book

 

[Malcolm]

I have a counter loop which actually executes in a different thread.
The thread is there to check for a connection time out. However due to
some limitations, I cannot use pthreads or any OS dependant components
(my code should run on both windows and linux). I have to relegiously
stick on to ANSIC standard. Does ANSI C provide any inherent function
which could accomplish what I intend to do. Or putting it otherway,
how can I just deviate from my direct execution path and just return
to it after a stipulated time has elapsed.

You need to rewrite the code. If you are executing a long function which may
need to abort (eg for connection time out) then pass in a callback function,
which gets called every so often, and which returns a trigger if the
function is to immediately abort. The callback can check the clock.

 

[William Ahern]

Hello,

I have a counter loop which actually executes in a different thread.
The thread is there to check for a connection time out. However due to
some limitations, I cannot use pthreads or any OS dependant components
(my code should run on both windows and linux). I have to relegiously
stick on to ANSIC standard.

If it's only Windows and platforms w/ POSIX threads (including Linux), then
this might help:

http://sources.redhat.com/pthreads-win32/

Does ANSI C provide any inherent function which could accomplish what I
intend to do. Or putting it otherway, how can I just deviate from my
direct execution path and just return to it after a stipulated time has
elapsed.

Not in ISO C, though I strongly suspect that if you're blocked on a
"connect" that you're already using another set of interfaces. In that case
the right answer for this particular problem couldn't be in ISO C, and
trying to stick too closely to ISO--within the scope of this particular
problem--will probably create more problems than benefits.

When it comes to networking, the next level up in standards is POSIX. You
can generally find POSIX interfaces for Windows (as in the above example).
Ultimately you could always bundle cygwin.dll with your application:

http://www.cygwin.com/