Add missing cpp files to the project.
Add two new constructors to ProgramBddContext

These take a vector and map of variable names/sizes, then call
the appropriate setIntVars() function.
Turn on -std=c++0x for the unit tests

XFA stuff needs it, and now that I am writing XFA unit tests it needs
to be on in the client code. So I just turned it on for all tests
because that seems simpler.
Merge branch 'master' of https://github.com/WaliDev/WALi-OpenNWA
Remove NewtonLogger.cpp from VS project
Fix severe bugs in WFA::isAcceptedWithNonzeroWeight and simulate

These are of the "this never worked" variety. Basically the existing
code wasn't handling weights correctly AT ALL.
Add 'const's -- THIS IS A BREAKING CHANGE

Introduce 'const' a bunch of places that should really have it, e.g.
'WFA::intersect(WFA & other)' becomes 'WFA::intersect(WFA const & other) const'.

However, the intersect() change caused ripple changes. In particular,
the signature of the virtual function make_weight(ITrans*, ITrans*) in
wali::wfa::WeightMaker has changed to accept 'ITrans const *' instead.

What does this mean? It means that if you have a subclass of WeightMaker
and overrode that version of make_weight() (there is another overload
in the original function make_weight(sem_elem_t, sem_elem_t)), then
in the new version your subclass will HIDE the new const version instead
and it will not be called.
Kill warning
Improved accepted word identification strategy
Merge branch 'master' into nwa_detensor
BinRel: Move the well-formedness checks in extend/combine before short-circuiting returns.

BinRel returns one/zero elements early in these operations. But the check that
both operands are either tensored, or non-tensored must be done before this
short-circuit.
Last commit introduced a bug in tensor.

This is what you happens when you disregard gtest.
API_CHANGE: path summary under Newton now works with tensored weights till the end.

This changes how to use Newton based poststar.
So far, path summary would obtained detensored weights from Newton based FWPDS and do path summary.
There are two externally visible changes now
(1) get_weight on FWPDS will return tensored weights.
(2) the output automaton after poststar as well as path summary can be seen to
    be labelled with tensored weights. The weights on the state after path
    summary are also tensored.
(3) path summary *must be* seeded with tensored weights.
(4) the input automaton *must continue* to be labelled with untensored weights.
    This is consisntent with the view that input automaton is a part of the
    input, and along with the pds, uses raw weights.
Update other goals in NewtonCompare for the new API of Newton based poststar.