Re: SUSv3's "memory location" and threads

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Adam Olsen" <rhamph@xxxxxxxxx> writes:

> I realize I'm "probably" safe if I ensure adjacent members are at
> least as large as int (or long, or maybe long long, depending), but
> I'm extremely mistrustful of C.  I'm hoping to find a way to be *sure*
> I'm behaving in a correct, portable manor.

Unfortunately there is no such way.  The only way you could be sure in
a portable manner is for the C and/or C++ language standard to define
how multi-threaded code should behave.  But they don't.

The next C++ standard, C++0x is intended to include definitions for
multi-threaded programs.  But it does not exist yet.

Ian

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux