From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-55988-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 17397 invoked by alias); 13 Oct 2014 09:55:40 -0000
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
Received: (qmail 17386 invoked by uid 89); 13 Oct 2014 09:55:39 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-lb0-f176.google.com
Received: from mail-lb0-f176.google.com (HELO mail-lb0-f176.google.com) (209.85.217.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Mon, 13 Oct 2014 09:55:37 +0000
Received: by mail-lb0-f176.google.com with SMTP id p9so6248335lbv.35        for <gcc-help@gcc.gnu.org>; Mon, 13 Oct 2014 02:55:34 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.42.194 with SMTP id q2mr22962640lal.75.1413194133990; Mon, 13 Oct 2014 02:55:33 -0700 (PDT)
Received: by 10.112.4.73 with HTTP; Mon, 13 Oct 2014 02:55:33 -0700 (PDT)
In-Reply-To: <543A79EB.7040002@gmail.com>
References: <5433F137.8050008@bo.infn.it>	<543A79EB.7040002@gmail.com>
Date: Mon, 13 Oct 2014 09:55:00 -0000
Message-ID: <CAH6eHdRbZoGssE8z6syfZetCz6vZM1Jgypq7cd1tjXj7AKnOYA@mail.gmail.com>
Subject: Re: Question
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: David Hagood <david.hagood@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>, Graziano Servizi <Graziano.Servizi@bo.infn.it>
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
X-SW-Source: 2014-10/txt/msg00080.txt.bz2

On 12 October 2014 13:54, David Hagood wrote:
> somewhat OT: I wouldn't put spaces between the class name, the colon, and
> the variable name in your code; they are all one thing - the name of the
> object being accessed. Also, use "std::endl" to end a sequence of insertions
> to a stream, not just '\n' - std::endl has more semantic meaning to the
> system, it really means "I am done with this line, do whatever you need to
> do, such as flushing it to the file", vs. "\n" which just means "insert a
> newline character".

std::endl is defined to be a newline followed by a flush, nothing more.