Initial commit. Code is functional, working on making it pass the same tests as Perl's Config::Any so that it is guaranteed API compatible \(to a point\) and people used to Perl's Config::Any should have no troubles using it.
start adding some 'Driver Options' to the code - not fully plumbed, but that will come
remove and re-add the tests directory because of the number of files added in places. This also brings in the tests that directly exercize the Config::General parser.
like an idiot I forgot that node-tap has strict requirements about needing test.end\(\) called
fix some minor bugs that have appeared now that the parser is being called multiple times in a single session
misunderstanding of node-tap led to there being some errors in this that are now fixed
enable the storing of arrays as values in Config::General files
enable the test that was turned off that tested the storing of arrays as values
remove some files that should never have been included
node-ini was not functioning for this case, so it has been replaced with a custom INI parser. this one passes the same tests as Config::Any::INI
core rework and re-org to prep for features like <<include>> that Config::General allows
xml2js was causing problems and not doing some of the things that needed done properly, this is the replacement.
replaced xml2js with a different parser. this one works a lot better.
various fixes and bug-tests. some of it likely needs to go away
had some unsaved changes in my editor when I did the last commit.
replace the Config::General parser with something better designed and capable of handling most of the features of the original. I am still not sure that variables are worth it, though the include functionality (both apache-style and Config::General tag-style) appears functional.
add variables to the Config::General parser, the symbol-table for holding information on them and update one of the test-files to include variables.
found these when checking to make sure there were no untracked changes. Oops.
add more of the tests
this was a tiny bit broken compared to Config::General when it comes to key->value pairs and what a valid key is when the pair is separated by an equals sign.