A Developer's Experience

I gave SMS FireWall a refresh with a couple of features requested by users:- An option 'Allow and Move' in the settings screen, which when checked moves the messages from the quarantine vault when opted to be added to the allowed list. Although it might be clear to you, let me explain it in a few words how it works. When you long press a sender in the quarantine vault, a menu with two options appear - Allow, Delete. When 'Allow' is clicked, the sender is added to the allowed list. And when the 'Allow and Move' setting is checked, the messages from this sender are moved to the inbox. A confirmation dialog prompt when attempted to empty the quarantine vault A few minor (internal) improvements Hope they are useful to others too. And let me know if you need any other features to be in the application.

Hugh pointed out a bug in the OrderedThreadPool . I think there is a small window for error in the OrderedThreadPool class. Bascially, if an item of work is queued, then a worker thread runs, takes the item off the queue and is about to call wcb(state) - but at that instant is (say) context switched. Then another item gets queued and another worker thread runs and dequeues the item and then again is about to call wcb(state). There is scope here for the two operations to run concurrently or even out of order... Here is the fixed version of the same. using System; using System.Collections.Generic; using System.Diagnostics; namespace System.Threading { public class OrderedThreadPool { private Queue workItemQ = new Queue(); private bool loopWorkRunning = false; public void QueueUserWorkItem(WaitCallback wcbDelegate, object state) { lock (workItemQ) { workItemQ.Enqueue(new ThreadPoolTaskInfo(wcbDelegate, state)); if (workItemQ.Count == 1 && !lo