Fix points 1) and 2) in ROOT-5468
sorry, there was a mistake in my coverity fix
get master and v5-34-00 to be the same
one last thing ... then master and v5-34 are the same (for TMVA of course only)
fix windows problems following Lorenzos advice
restore backward compatibility with predefined options that are no longer available in the BDTs
Make that TTreeCache::SetEntryRange does not prevent the loading of the first entries as a single read
 that should take care of the last coverity complaints
update documentation
Add missing delete (Fix ROOT-5539)
First version of Quasi random class based on GSL

Add also copying of pesudo-random generator classes using the GSL clone methods
Add dictionary generators for quasi random numbers
Add also typedef for Random and QuasiRandom
Add test for quasi randoms
Small improvements to QuasiRandom interface
update documentation
protect against division-by-zero - JIRA bug report ROOT-5409
Add tutorial for quasi random number  math/quasirandom.C
Add interface to get name of generator
Fix CMake file for new quasi-random classes
make plotOn taking a RooLinkedList public

Signed-off-by: Wouter Verkerke <verkerke@nikhef.nl>
BidirMMapPipe: make the shutdown sequence for pipes and socketpairs more similar

This patch makes the shutdown sequences for pipes and socketpairs more
similar, and should in fact be more robust under high load.

Signed-off-by: Wouter Verkerke <verkerke@nikhef.nl>
fix race condition between dirty shutdown of BidirMMapPipe and RooRealMPFE

When a RooRealMPFE is not deallocated at runtime, but has it's
destructor called during after main() has exited, it may happen that the
cleanup routines for BidirMMapPipe are called first by the C++ runtime
shutdown code. In that case, the pipe held by RooRealMPFE is already
closed by the time RooRealMPFE tries to send the regular Terminate
message to the child process. The patch detects this, and refrains from
sending this final message over the pipe, since the child is no longer
alive at that point. Since the parent process is not waiting for any
data from the child, this is not harmful.

Signed-off-by: Wouter Verkerke <verkerke@nikhef.nl>