The following test program (Test.cpp) fails with.L + Test.cpp+, but not with plain .L, nor with gcc. It also does not tell me anything about why where it fails!

#include <string>
int Test(std::string x) {
cout << x << "\n";
 return 1;
};

Error in <ACLiC>: Executing 'C:\root_v6.28.06\bin\rootcling -v0 "--lib-list-prefix=C:\Users\snyde\BFROOT\ROOT\Test_cpp_ACLiC_map" -f "C:\Users\snyde\BFROOT\ROOT\Test_cpp_ACLiC_dict.cxx"  -rml Test_cpp -rmf "C:\Users\snyde\BFROOT\ROOT\Test_cpp.rootmap" -DR__ACLIC_ROOTMAP -I%ROOTSYS%\include -D__ACLIC__  "C:/Users/snyde/BFROOT/ROOT/Test.cpp" "C:\Users\snyde\BFROOT\ROOT\Test_cpp_ACLiC_linkdef.h"' failed!

Huh? Why?

I can't learn what's wrong using 'g++  -c Test.cpp' (outside ROOT)  as it compiles w/o complaint in that case.

Is there a way to get ROOT to tell us what it objects to?

The code generting module C writes  result to screen. How to I get it to file?

 In the memory leak problem with my DStarLepNu simulation program, I did find one cause in that due to normalization errors the accept/reject algorithm in ‘PickAngles’ was executed too many times. This should have just made angle generation inefficient but occasionally, but not always produced very big memory bumps when a large number of trials were needed to pick angles. It’s not clear why these bumps occurred as the code being executed is always the same and is simple.

Fixing this did however not prevent memory crashes or even reduce them much.

I have since turned off accept/rej and calls to ‘arccos’ and more modest spikes remain and crashes still occur!

I don’t understand how Maple memory management works. My B-meson decay prov ‘bDecay’ usually gives  still shows occasional spikes and and there’s a weird correlation between the first (B1) and second (B2) call:

DStar3DKinRecoLoopDebugCombo200EventsExportRun2.mw

çMemory added by ‘bDecay’ proc on 1^st call vs 2^nd call in the B1-B2 event loop..

èWhat with the slope and difference in width?

How do I set the axis range in a Maple scatter plot. It's not evident to me from the Help.

As my jobs are still crashing with memory leak, I'd like to write results out to files and read them back to add them together.

I see something called 'Export' and something called 'Import'. It didn't work for me. Does the file have to already exist? An example would be nic