JLD: add `rootmodule`, and use it in tests of module paths
Fix deprecation of read(stream, a::Array) (fix #86)
Fix reading of Exprs (fix #90)
Allow Colon in hyperslab reading (fix #87)
Fix loading of custom types defined in external modules.
Merge pull request #91 from sunetos/types_fix

Fix loading of custom types defined in external modules.
Allow `test/require.jl` to be run from any directory (fixes Travis errors)
Fix parents_create() when path is an UTF8String
Improve and add test to fix of issue #93
Merge pull request #94 from cdsousa/master

Fix parents_create() when path is an UTF8String
Fix problem with test script on Julia 0.2 (conversions-in-constructor issue)
Fix #95
Merge pull request #96 from timholy/sjk/95

Fix #95
Document manual library installation (fixes #97)
Add high-level load and save functions for JLD

These functions are similar to their macro counterparts, except that they operate on and return dictionaries instead of variables directly in the global namespace.

save takes a filename and a dictionary with bytestring keys. The dictionary key-value pairs are saved in the file, with the keys as the variable names and the values as their contents.

load takes a filename and (optionally) a list of variable names to read. If no variable names are given, all names in the file are read. It reads the variables into a dictionary that is returned.
Change the macro load to return the list of variables loaded

Previously, this macro would simply return the value of the last variable it read. This is more useful.
Append instead of overwrite in save; make the dict typing a little less restrictive
Revert saving in "r+" mode, use "w" instead

"r+" requires the file to already exist. Appending data to files is tricky and not terribly intuitive (what if data with the same names are already there?). I think "w" is better.
Further relax the Dict type in save()

Given that the typing of dict comprehensions is poor at the top-level, it is silly to make folks jump through hoops to make sure that they String keys really are strings.  The bytestring function will error just fine by itself, although perhaps it could use a nicer error message.
Add doc and a test for the save/load functions