The Next Generation of 2D Roleplaying Games
http://forums.elysianshadows.com/
//Query last log read
int rows = ds.Tables["tblLastLogRead"].Rows.Count;
if (rows == 0)
{
return DateTime.Parse("January 1, 1900");
}
else if (rows == 1)
{
return (DateTime)ds.Tables["tblLastLogRead"].Rows[0]["LastReadDate"];
}
//Something bad happened
return DateTime.Parse("December 7, 1941");
That shit is deeeep.Code: Select all
if (!japanese)
return error;
Code: Select all
//Something bad happened
return DateTime.Parse("September 11, 2001");
Not only is that too close to home, it's too close to now. One of our old applications was written by a guy who thought it would be a good idea to use "9/9/99" as the null date; worst idea ever. Invalid dates should always be far enough in the past that they won't possibly overlap with valid dates, and should *never* be in the future.mattheweston wrote:I could also see
being applicableCode: Select all
//Something bad happened return DateTime.Parse("September 11, 2001");
Yeah, that's definitely the best way in most circumstances. On certain occasions you want the software to keep doing what it's doing even if an error occurs though, so you need *some* valid date. A more intelligent date would be 1900-01-01 or something else innocuous in case someone sees it.K-Bal wrote:I mean you also use an exception or a success / error code parameter...
Lol. "FactoryModule" takes in a "ContainerBuilder". Seems perfectly obvious to me.short wrote:I had no idea at the time what I was doing to myself with this nugget, it's 4 years old at this point:
https://github.com/bjadamson/Smashteroi ... cs#L12-L38
