closes #424 also reverting the CWD changing behavior in loading that Stefan didn't like
the bootstrapping process is in flux. soon there will be two stages: - stage0: builds sys.ji from nothing, i.e. from a state where there is no running julia code. - stage1: julia starts with sys.ji as in normal use, and another copy of the standard library is loaded in a separate module, which gets saved as sys.ji.new. If this image works, it can replace sys.ji. - Standard use (e.g. typical library edits) will only require running stage1 once. - If edits were made to critical code, stage 1 should be repeated to run the new code on itself. - If we ship sys.ji, nobody will ever need to run stage0 except in rare cases. As of this commit stage1 does not quite work yet, and we are only using stage0.
tuples. adding test. tweaking specialization heuristic for tuple arguments not to specialize slots declared as (Any,Any) and so on. the method cache for map() on tuples was getting way too big. renaming unittests to quicktests, to reflect what it's for
the standard library
removing some unused files
used for library files adding JULIA_HOME runtime variable in julia making julia_home always the correct full path, instead of relative to CWD
adding PCRE_DIR build var