Subject: Your receipt No. 352-45652 (Term Policy)

From: Policy Confirmation <[email-masked]>
Date: Fri, 30 May 2014 13:37:47 -0700

Greetings Ipp-archive

I was watching the Suze Orman show and I couldnt believe what I saw. She was talking about life Insurance.

She said that the ONLY one you should have is Term-Life Insurance. 

CNBC is all about financial health, and I trust them so I switched, now Im only paying $15 monthly.

- Theres no exam and you get $750k in coverage

-> http://www.mixpurple.com/term/policy/rate/gnerated.index

We hope you enjoyed this financial update
to stop further updates write Update Notice Messages
at one one eight_Kecks Lane_R u f f  D a l e_ Pennsylvania_ 15679
or http://www.mixpurple.com/i49tj.wlrkgt4

@Mrchief: Introducing new keywords after release is a tricky business. It's possible that this wouldn't cause any problems (like other contextual keywords), but I'm not entirely sure... and how would you make a public "getter" with a private "setter" that way? I wouldn't want to have two different syntaxes for it... (Personally I wish field-like events were declared as public event EventHandler Foo { add; remove; }; to make them clearer, but there we "another MS product totally despises the trailing comma" -- I think Mrchief was really talking about object and array literals in IE6, IE7, and IE8 too IIRCI do not think making editing slightly faster is a good reason for messing up the syntax. IMHO this is just another weird C++ feature.  @Giorgio: Well, it's inherited from C. It's entirely possible that it's just an oversight in the original Ok, I didn't know that it comes from C. I just checked that it is allowed in Java, too. It feels kind of weird though: in my intuition the comma 
 is a separator not a terminator. Furthermore, it is possible to omit the last comma. So, is it a terminator, a separator, or both? But OK, this feature is available and it is good to know.  @Giorgio - source code is for humans, not machines. Little things like this to keep us from making simple transposition errors are a blessing, not an oversight. For reference, it also works this way in PHP and ECMAScript (and therefore JavaScript and ActionScript), although it is invalid in JavaScript object notation (JSON) (e.g. [1,2,3,] is OK but {a:1, b:2, c:3,} is not).   - I'd say that rather than messing up the syntax, this improves the syntax. I can't count the number of times I've been glad you can do this. It's also allowed in the latest C# specification @Groky: The more I think about it the more I am convinced that the syntax of a programming language should be as simple and consistent as possible and with as few exceptions as possible: this makes it easier to learn the language (fewer 
 rules to remember). The advantage of saving one or two keystrokes when adding / removing an item to / from a list (which, by the way, I do not do that often compared to the total amount of time I sI disagree completely; [It is my opinion that] it has found its way into many languages created long after C precisely because it is advantageous for the programmer to be able to shift around the contents of the array, comment out lines willy-nilly, and so on, without having to worry about silly transposition-induced syntax errors. Are we not already stressed enough?   Dereleased Aug 12 '11 at 21:54
8	  	
@Dereleased -- by the same logic, why shouldn't trailing (anything) be allowed, how about int a = b + c +; or if(a && b &&); it will be easier to just copy-and-paste anything at the end and easier to write code generators. This issue is both trivial, and subjective, in such cases it's always good to do what's best for the code reader.   Gene Bushuyev Aug 12 '11 at 22:06
1	  	
@Gene Bushuyev: Exactly! I often have long expressions with + or &&, with the operator at the end of the line and, of course, I have to spend some extra time when I want to remove the last operand of the expression. I think this comma syntax is really odd!   Giorgio Aug 18 '11 at 6:15 
1	  	
@GeneBushuyev - I disagree on those. While allowing trailing commas in arrays and the like is a bug-removing feature and makes your life easier as a programmer, I would for the pure sake of readability take measures to remove trailing AND (&&) statements, plusses and other miscellaneous operators from conditional statements. It's just plain ugly, I