Subject: Simplified Protection | Term-Life Policy: 250K Available

From: Eligible for 750k Payout <[email-masked]>
Date: Tue, 27 May 2014 07:47:22 -0700

Greetings Ipp-archive,

------ May Policy Update ------

- Update the policy while your healthy 

You have reached a life milestone which now qualifies you for a low Term-Life Rate.

View Updated Rate Here: / http://www.centrunnano.com/life/term.index
~ Rate Generated on: May 27, 2014

Are you experiencing 1 of the following?

- Getting Married
- Buying A Home
- Managing A Growing Family
- Becoming A Stay At Home Parent
- Running Your Own Business
- The Single Life
- Life After The Kids Have Moved Out
- Planning For Retirement
- Supporting Aging Parents
- Estate And Legacy Planning

If you said yes to any of the following, go here -> / http://www.centrunnano.com/life/term.index

------ End Policy Update ------

-to modify messages - write Alert System Notifications
 @ 1107 Valeria Drive-Marion- TX-78124 http://www.centrunnano.comjf3/3mr.html

 

 Do we need to account in our code for cases where the person in question have travelled large distances near the speed of light?   JTew Mar 25 '11 at 4:04 what all of the answers so far have missed is @Yaur: Just convert the time of now + birth into GMT/UTC, age is only a relative value, hence timezones are irrelevant. For determining the user's current timezone, you can use GeoLocating.   Quandary Oct 3 '11 at 10:20
 Shouldn't we close this question with the according to the rule: Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results.   uthark Sep 6 '13 at 15:34  @uthark this was a self-answered question. Read the answers and pay attention to the author of the question and the answers. Also the dates and times.   Jeff Atwood Sep 6 '13 at 20:36 @JeffAtwood author of accepted answer is community wiki. In revisions I see that accepted answer was written by Mike Polen, you just edited the answer, so it is not a self-answered question from what I see. And I see that it is something very old.   uthark Sep 6 '13 at 22:11@donkaka - Please elaborate on what you are looking for with the bounty. Thanks.   Matt Johnson Sep 16 '13 at 15:2	  @Quandary: only if you want their age in standard time. If you want their age in some solar time like local mean time, their date of birth is not enough. 
 We'll also need the latitude and longitude of their place of birth.   Bas Sep 19 '13 at 13:38  Why not consider [Julian Date][1]? [1]:    Muhammad Hewedy Oct 5 '13 at 13:32Why does this question have so many upvotes?   Bobby Alexander Oct 7 '13 at 2:33 This is a base knowledge of c#,it's just a simple datetime function. >Why does this question have so many upvotes?  Bobby Alexander Oct 7 at 2:33   xudong125 Nov 3 '13 at 14:07@uthark Don't be silly. This question has 675 upvotes at the time of writing this, which shows that it is a valuable resource for the community now, and for new-comers in the future.   delete this account Dec 22 '13 at 8:23Just wanted to comment on DateTime.Now performance. If you don't need an accurate time zone value, use DateTime.UtcNow it's much faster.   JAG Jan 22 '09 at 10:29Given we're talking birthdays you can just use DateTime.Today given the time part has no relevance.   Tristan Warner-Smith Jul 24 '09 at 18:04
This answer does not work with all locales and all ages. Several countries have skipped dates after the birth of current living people, including Russia (1918), Greece (1924) and Turkey (1926).   Lars D Nov 9 '09 at 22:09
So we have a different age according to different countries and calendar ? What a scoop...   e-satis Nov 16 '09 at 16:35@JAG: DateTime.Today should be even faster.   Shimmy Dec 14 '09 at 0:37
This is wrong! Try it with a person born 2000/02/29. If now is 2009/02/28, your code will state that the person is 9 years old.   Danvil Apr 15 '10 at 19:13Good catch Danvil! Changed last line to: if (bday > now.AddYears(-age)) age--; I think that fixes it. It passed my measly 3 tests :-)   Mike Polen Apr 16 '10 at 20:13Actually, it's still not entirely correct. This code presumes that 'bday' is the date-portion of a DateTime. It's an edge-case (I guess most people will just be passing dates and not date-times), but if you pass in a birthday as a date-and-time where the time is greater than 00:00:00 then you'll run into the bug Danvil pointed out. Setting bday = bday.Date fixes this.   vind Nov 16 '10 at 15:37The last line made me think too much. Instead how about: if (bday.AddYears(age) > now) age--; This seems to be a more intuitive expression.   cdiggins Jul 16 '11 at 17:53 Good idea cdiggins, but it doesn't work as bday.AddYears(age) when age is 2/29 returns 2/28 on years that ar
 e not leap years...keep trying   Mike Polen Jul 18 '11 at 18:04Or just do if (BirthDate.DayOfYear > Today.DayOfYear); no need to forther modify the date variables   NKCSS Aug 16 '12 at 15:15@NKCSS: That does not handle the leap year correctly. My testing shows that only if (bday > now.AddYears(-age)) works. Since DayOfYear returns 61 in 2012 and 60 in 2011 for March 1.   Guvante Aug 21 '12 at 18:47
@Guvante Thanks...I lost my test last year when I lost my hard drive...I should have tested more   Mike Polen Aug 23 '12 at 13:07@Danvil, is it really wrong? Take a simpler example. Birthday = 2000/02/29, Today = 2001/02/28. Days elapsed: 365. Isn't that one year, and therefore, isn't the person one year old on the 28th? Or is the definition of a year 365-1/4 days? I'm just sayin', it's complicated.   devuxer Dec 12 '12 at 2:06Wouldn't it be easier to just do DateTime dateDifference = subject.Birthday - DateTime.Now; int age = dateDifference.Year;? Also, I don't think age depends on leap years. After all, a year is defined as 365<x<366 days, leap years don't make you any day younger.   Nolonar Jan 31 '13 at 10:55 
I can't edit my comment anymore, so here's my correction: TimeSpan difference = subject.Birthday - DateTime.Now; int age = difference.Days; If you want the age in years, you could always add int ageInYears = age / 365;   Nolonar Jan 31 '13 at 11:03 
@LarsD "Several countries have skipped dates after the birth of current living people" <- What do you mean?   cja Feb 13 '13 at 15:08@cja - It means that some countries did some funnies years ago to sync up calendars and remove discrepancies! en.wikipedia.org/wiki/Gregorian_calendar may speak more about it, I haven't fully read. The reference to 'Current People' is simply to state that the adjustments happened in the 20th century (1901-2000). A lot of people are still alive from that period! :)   bPratik Feb 14 '13 at 18:04
DateTime birthdate = new DateTime(2012, 11, 5); DateTime now = DateTime.Now; int years = now.Year - birthdate.Year; if (now.Month < birthdate.Month || (now.Month == birthdate.Month && now.Day < birthdate.Day)) years--; Console.WriteLine(years.ToString()); Console.ReadLine();   Shaik Raffi Nov 5 '13 at 11:34
@LarsD so what you are saying is that there is no way to calculate people's ages? Rubbish. They messed with their calendar, they can adapt. Even if you could do a library to calculate cross calender based on locale, a) where do you source this info b) is it actually worth it?   Gusdor Nov 5 '13 at 13:04 
This code is not calculating the nearest age. Here, is the code: var ts = DateTime.Now - new DateTime(1988, 3, 19); var age = Math.Round(ts.Days / 365.0);   Dhaval Panchal Dec 3 '13 at 10:13
int age = DateTime.Today.Year - bday.Year; age = bday > DateTime.Today.AddYears(-age)) ? age-- : age;   Travis Ma