🚀 go-pugleaf

It seems that newlines-to-CR does odd things,
and even if unchecked some odd things can happen.

With newlines-to-CR off, writing a std::endl
to an fstream writes '\r' but writing std::endl
to a stringstream writes '\n'.  However writing
a std::string which contains carriage returns to
an fstream translates '\r' to '\n'!!!

With newlines-to-CR on, I noticed a really bizarre
thing: writing a literal '\r' to an fstream produces
a '\n' in the file.  Which isn't map-newlines-to-CR,
it's map-CR-to-newline!

Is all of this documented somewhere?  I searched
the manuals for "newline" and nothing came up.

What I'd really like is to have std::endl always
be the same thing regardless of whether it's
going to an fstream or a stringstream, and
also have '\r' in code always mean '\r' in
the byte and its subsequent i/o, and sim. for
'\n' to always mean '\n', with no translation
other than what the programmer does explicitly.
If this is possible in MSL C++, what does 
it involve other than the newlines-to-CR setting?

Thanks for info,
Chris