Re: [Monotone-devel] [PATCH] Specifying multiple --message arguments for commits

[Richard Levitte - VMS Whacker]

In message <address@hidden> on Sun, 01 Oct 2006 17:47:00 -0500, Timothy 
Brownawell <address@hidden> said:

tbrownaw> On Mon, 2006-10-02 at 00:19 +0200, Richard Levitte - VMS Whacker 
wrote:
tbrownaw> > In message <address@hidden> on Sat, 30 Sep 2006 14:34:15 -0500, 
Timothy Brownawell <address@hidden> said:
tbrownaw> > 
tbrownaw> > tbrownaw> On Sat, 2006-09-30 at 21:17 +0200, Thomas Moschny wrote:
tbrownaw> > tbrownaw> > Can't you simply use std::endl for that?
tbrownaw> > tbrownaw> 
tbrownaw> > tbrownaw> std::endl is the same as '\n' plus flush() . No reason to
tbrownaw> > tbrownaw> use it unless you're trying to also flush the stream 
you're
tbrownaw> > tbrownaw> writing to...
tbrownaw> > 
tbrownaw> > ...  or trying to be platform independent...
tbrownaw> 
tbrownaw> How so? Line-ending translation is handled elsewhere, what
tbrownaw> other platform-specific things could be there? (plus, IIRC
tbrownaw> endl is *defined to be* write "widen('\n')" and flush the
tbrownaw> stream)

On some platforms, then end of line is "\r\n".  On some others, it's
not even a character, it's writing down the line as a record with a
length indicator.  But I'm sure the stream is flushed either way.

Cheers,
Richard

-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.

-- 
Richard Levitte                         address@hidden
                                        http://richard.levitte.org/

"When I became a man I put away childish things, including
 the fear of childishness and the desire to be very grown up."
                                                -- C.S. Lewis