Thanks to Rennie and Igor for replying to my post. I now have a much better
idea of what I need to do. Doubtlessly I will still encounter many problems
when I start converting my programs however!
What books would you recommend Igor? I am used to writing C code but have
never needed to split it in to processes and threads before (i.e. all non
real-time)
R > Thanks to Rennie and Igor for replying to my post. I now have a much better
R > idea of what I need to do. Doubtlessly I will still encounter many problems
R > when I start converting my programs however!
R > What books would you recommend Igor? I am used to writing C code but have
R > never needed to split it in to processes and threads before (i.e. all non
R > real-time)
R > Thanks again,
R > RonanK
If you can accomplish what you need to accomplish with a single
threaded application, then don’t complicate your life needlessly. Code
your application as a single threaded application.
If your system requires that several processes occur somewhat
concurrently, then your still living in the single threaded world.
Write two seperate processes and let them both run concurrently.
NOTE: putting a ‘&’ after a command on the command line runs the
command in the background so that you have a new command line prompt
to enter another command.
The only time you really should write a multi-threaded application
is when you realize that multiple things need to happen at the same
time AND in a tightly coupled environment. I.E. they are sharing
resourses like a common memory buffer.
I.E. If you need something to be multi-threaded, you’ll know it!
Thanks to Rennie and Igor for replying to my post. I now have a much
better
idea of what I need to do. Doubtlessly I will still encounter many
problems
when I start converting my programs however!
What books would you recommend Igor? I am used to writing C code but have
never needed to split it in to processes and threads before (i.e. all non
real-time)