sig_atomic_t

[sleith]

i have couple of questions about sig_atomic_t
1. if the first declaration variable of sig_atomic_t is 0 (without assigning the 0 value, just declare like sig_atomic_t atomic; )?
2. suppose i have this code

sig_atmoic_t atomic;
if( ++atomic == 1 ){
}

will this become 2 seperated atomic operation that first to ++ the atomic value, and then check if the value is 1?
or it will be as one atomic operation that will guaranted that atomic variable inside if statement will not be read/write in another thread?

thanks

[Codeplug]

1. Variables of type sig_atomic_t are typically declared with static scope. That means it will be zero initialized by the system if it isn't explicitly initialized. For their intended use in signal handlers, they should also be declared as volatile.

2. That's at least 2 atomic operations.

>> ...will not be read/write in another thread?
Thread? You mean signal handler?
sig_atomic_t and threads have nothing to do with each other.

gg

[sleith]

>> ...will not be read/write in another thread?
Thread? You mean signal handler?
sig_atomic_t and threads have nothing to do with each other.

i mean if there's two thread using the sig_atomic_t for synchronization instead of mutex.

[Codeplug]

The only guarantees you have with sig_atomic_t have to do with signals. All bets are off for threads. For proper synchronization, use the primitives provided by the threading API.

The new C++ standard will have atomic types for use by threads.

gg