semaphores do not access like volatile

Niko Schwarz niko.schwarz at gmx.net
Mon Feb 10 17:12:20 UTC 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Montag, 10. Februar 2003 13:54 schrieb Bob Arning:

> The difference is that #forMutualExclusion signals the newly-created
> Semaphore so that the first #wait will proceed straight through, although
> you could easily use #new and then #signal yourself.

It seems to me very annoying that Semaphores store a signal in case nobody is 
listening. 
That's very unpleasent for network communication, because sometimes I just 
want an event to be ignored, while potentially there /could/ be someone 
interested in it.

Is there a way to make semaphore behave non-remembering?
SharedQueue looks better, but a timeout would be nice, and im not sure, but: 
doesnt it remember signals forever, too?

regards,

nick
- -- 
Real programmers don't write in FORTRAN.  FORTRAN is for pipe stress
freaks and crystallography weenies.  FORTRAN is for wimp engineers who
wear white socks.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+R9103P3nmXTVnC8RAtEgAKCc7XCJtpWPXs1cHSFzpqNnGW2TUwCbBQVK
iV5Q7tRvKDjX/3KDKnVBhMo=
=P/rP
-----END PGP SIGNATURE-----



More information about the Squeak-dev mailing list