From: Jörgen Sigvardsson <jorgen.sigvardsson@kau.se>
Subject: rsbac_{read,write}_[un]lock
Date: Tue, 20 Feb 2001 13:41:59 +0100
Next Article (by Author): Re: Lists Jörgen Sigvardsson
Previous Article (by Author): Lists Jörgen Sigvardsson
Articles sorted by: [Date]
[Author]
[Subject]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the purpose of the lockflags (2nd parameter)? I see in the code that it doesn't actually do anything. However, I'd like to prepare for the future in case it will be used. Right now I just: u_long lock_flags; ... rsbac_write_lock(&lock, &lock_flags); /* critical section */ rsbac_write_unlock(&lock, &lock_flags); Would this be broken in the future? (If there is a future for the flags parameter that is) - -- Jörgen Sigvardsson, B. Sc. Lecturer, Computer Science Dept. Karlstad University Tel: +46-(0)54-700 1786 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.3 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6kmYXJtcD8rikkmwRAr+EAKCJjvF1B+oXV0GO4fav2GSn8iJovQCdFbvU bOxR/LncA+WR3cKM8phS7JI= =CfCt -----END PGP SIGNATURE----- - To unsubscribe from the rsbac list, send a mail to majordomo@rsbac.org with unsubscribe rsbac as single line in the body.
Next Article (by Author): Re: Lists Jörgen Sigvardsson
Previous Article (by Author): Lists Jörgen Sigvardsson
Articles sorted by: [Date]
[Author]
[Subject]