Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COI am currently in design phase. My child threads once start executing they needs to run periodically for performing some work and also they needs to wait for triggers( events in windows) from the parent thread. This events include termination . Anyway this is in windows.I am finding difficulty in identifying similar interfaces in ACE 2. Only parent thread needs to communicate with child threads 3. Yes we always have the ability to terminate gracefully The other question you have mentioned is exactly what I need to implement using ACE. Can you suggest me similar interfaces in ACE
      singulars
    2. CODisclaimer: I've not used ACE myself, I prefer Boost. If I understand your problem correctly, its not necessarily an ACE issue. In Linux, you need something analogous to Windows Events, such as using sockets and select (see http://linux.die.net/man/2/select_tut). ACE's task class also (see section 5.5 http://www.cs.wustl.edu/~schmidt/PDF/ACE-concurrency.pdf) provides a message queue that can be used to replace events. Another option is to use an ACE Condition. The bottom line is this: there are multiple solutions both using ACE and native linux calls. See which one fits your needs best.
      singulars
    3. CO@resehen what I feel is sockets,select and message queues are basically used for when some IO or data transfer is required. and ACE or linux condition variables is some how odd as I need to have a condition varible for each corresponding event, and multiple threads using the same condition variable with mutex locking is inefficient. May be I should go with ACE thread manager ACE_Thread_Manager::instance ()->cancel_all () for terminating all the threads and ACE event handler in each thread so that they can run periodically.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload