SevSeg Library 2.1.zip issues

So earlier this eveing, I was attempting to learn and write my own library for a common anode 7-seg display. Then, I decided to just see if there was an existing library (why create whats already there?) just to toy around with and maybe check out the library myself to see more complicated examples of how to write a library.
Anyways, I went here...
https://docs.google.com/file/d/0Bwrp4uluZCpNN1Q4dmFZX1MzWVE/edit
And thought oh cool! There is one! So I download the .h and .cpp file (along with a nifty counter example), and when I go to compile the example (as is habit now to discover any errors in my own code), I find that there is an error, and apparently "SevSeg does not name a type".
Here is the beginning of the code...

#include "SevSeg.h"

//Create an instance of the object.
SevSeg sevseg = ;

//Create global variables
unsigned long timer;
int CentSec=0;

The part that says "SevSeg sevseg = ;" is what is highlighted when the error pops up. As well, the IDE points out that, well, because this does not name a type, "sevseg" that appears throughout the rest of the program is not valid as well.
Does this indicate a problem with the library? I tried amending the instance to "SevSeg sevseg = SevSeg();" but to no resolve. Any help would be appreciated! Thanks!
:~
~gtr_stitch

Does

#include "SevSeg.h"

not produce any error?

Where have you installed the library files?

SevSeg sevseg = ;

This is a syntax error anyway.

Change it to

SevSeg sevseg;

As far as I can tell, the include doesn't pull up any errors. It seems just with that "SevSeg sevseg = ;" part. I changed it as you suggested, and it's the same error. Didn't really change anything.
:~

I ask again: Where did you install the library files?

Sorry. There in the libraries folder with all the other libraries, inside a folder named SevSeg. You think the folder name has anything to do with it?

You think the folder name has anything to do with it?

No. But, you should try compiling your code on 1.0 (NOT 1.0.1). 1.0.1 has a fatal flaw that the Arduino team seems to be ignoring, where missing include files are no longer considered fatal errors. What horseshit. Of course they are.

Thanks Paul. I appreciate the feedback. I'll definitely give that a go and see what happens.

I compiled in 1.0, and I am still getting errors. The same one, actually. Considering just scrapping the sketch and library. I'm sure there are tons more out there. Thanks for the help, anyway!