<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Thank you all for your replies, I went ahead and changed my function names and added guards, and it now looks far cleaner.<div class=""><br class=""></div><div class="">One thing that I keep seeing in this thread though is some variant of<b class=""><i class=""> “crash early, crash often,â€</i></b> and this is a little troubling. What if you are writing a program that is receiving a messages and has a queue awaiting action? If the program dies, those messages will be lost, and if the calling processes made ‘casts’ then those messages won’t ever be delivered or processed. Also, it takes a bit of time for the supervisor to re-initialize the process, and this could be bad. </div><div class=""><br class=""></div><div class="">Is it always a good idea to “crash often†when bad input is received?</div><div class=""><br class=""></div><div class="">Thanks for all of your help!</div></body></html>