Incorrect year assigned to combat log

[GoogleCodeExporter]

Combat logs from 2008 are given "2009" as their year.  Is it possible to
put a small check in to correct this?  Maybe check to see if the date of
the log is >= 1 week in the future?

Original issue reported on code.google.com by schep...@gmail.com on 27 Jan 2009 at 3:18

[GoogleCodeExporter]

You can add "-year 2008" when you run a log from last year.

I'd recommend doing that, since I think I'd rather keep the default logic 
simple (just use current year unless you 
tell it "-year xxxx").

Original comment by gianmerlino@gmail.com on 27 Jan 2009 at 3:27

• Changed state: WontFix

[GoogleCodeExporter]

You beat me to it.  Thanks for the quick response!

I'm a perl noob, but I figured there might be some way to tweak the code and 
when I
went looking I found the getoptions statement:

my $rc = GetOptions(
    "version=s"     => \$opt_version,
    "logger=s"      => \$opt_logger,
    "file=s"        => \$opt_file,
    "dir=s"         => \$opt_dir,
    "minlength=i"   => \$opt_minlength,
    "attempts"      => \$opt_attempts,
    "nowrite"       => \$opt_nowrite,
    "year=i"        => \$opt_year,
    "sfile=s"       => \$opt_sfile,
    "trash"         => \$opt_trash,
    "overall"       => \$opt_overall,
    "combine"       => \$opt_combine,
    "server=s"      => \$opt_server,
    "collapse"      => \$opt_collapse,
    "tail"          => \$opt_tail,
    "navigation"    => \$opt_nav,
    "filter=s@"     => \$opt_filter,
    "throttle=i"    => \$opt_throttle,
    "debug"         => \$opt_debug,
);

Original comment by schep...@gmail.com on 27 Jan 2009 at 4:51