Thank you for all the feedback and discussion.
I now realize that my app, which seems to work
perfectly, is a time bomb that would blow
my brain away because I'm using a "pipeline"
where a finished job is indicated by setting
a flag as the final instruction. Like this:
.....
// do stuff
.....
// and finally
flag = flag_val;
// WRONG. Can be reordered even if
// atomicity can be assumed
I have to put a barrier to ensure that the flag
setting is REALLY the final instruction. Can
I do this?
.....
// do stuff
.....
// and finally
AtomicInt.@set (ref flag, flag_val);
// Safe????
What's the correct way to do this in vala?
Nice day
Nor Jaidi Tuah
PRIVILEGED/CONFIDENTIAL information may be contained in this message. If you
are neither the addressee (intended recipient) nor an authorised recipient of
the addressee, and have received this message in error, please destroy this
message (including attachments) and notify the sender immediately. STRICT
PROHIBITION: This message, whether in part or in whole, should not be reviewed,
retained, copied, reused, disclosed, distributed or used for any purpose
whatsoever. Such unauthorised use may be unlawful and may contain material
protected by the Official Secrets Act (Cap 153) of the Laws of Brunei
Darussalam. DISCLAIMER: We/This Department/The Government of Brunei Darussalam,
accept[s] no responsibility for loss or damage arising from the use of this
message in any manner whatsoever. Our messages are checked for viruses but we
do not accept liability for any viruses which may be transmitted in or with
this message.
_______________________________________________
vala-list mailing list
vala-list@gnome.org
https://mail.gnome.org/mailman/listinfo/vala-list
