Most 'volatile' in the code are historical, as volatile is no longer considered best coding practice since the semantics of volatile are unclear for SMP and don't deal with load/acquire. Nowadays we usually use the atomic library routines or intrinsics, or mutexes. My experience is that is relying on volatile for correct behavior is often suspect on SMP. I'm not familiar with this module AMRWriter in particular, so I can't comment on whether it is correct or not.
On Friday, November 1, 2013 12:24:46 PM UTC-7, baskar_IEL wrote: > > Hi All, > > I was going through the AMRWriter.h file , the variable mReachedEOS is > > volatile bool mReachedEOS - from JB version. and > > bool mReachedEOS - in GingerBread Version. > > Please let me know what difference it will make by qualifying the variable > to "Volatile". > > > Regards, > BT. > -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
