Mailing-List: contact stdcxx-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stdcxx-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <4638B61C.30703@roguewave.com>
Date: Wed, 02 May 2007 10:02:36 -0600
From: Martin Sebor <sebor@roguewave.com>
Organization: Rogue Wave Software
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1
MIME-Version: 1.0
To: stdcxx-dev@incubator.apache.org
Subject: Re: unprintable characters in Windows build logs
References: <461F0438.2070700@roguewave.com>
In-Reply-To: <461F0438.2070700@roguewave.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Farid,

The question mark symbol that shows up in the browser is U+FFFD,
the Unicode Replacement Character. The actual character in the
log is the NUL ('\0'). I searched the Windows scripts for where
we might be inserting NULs but couldn't find anything. Do you
happen to have any idea where it might be coming from? Could
the IDE be inserting it?

Thanks
Martin

Martin Sebor wrote:
> ...anyone else seeing the question marks at the end of our Windows build
> logs when invoking the clean target? It looks purely cosmetic but if
> someone has the time it would be nice to clean them up :)
> 
> Here's what I'm seeing (the question mark is the first character on the
> line line below the one that ends in '8s Optimized Static|Win32'.
> 
> ------ Clean started: Project: .stdcxx_utils, Configuration: 8s 
> Optimized Static Win32 ------
> 
> Deleting intermediate files and output files for project 
> '.stdcxx_utils', configuration '8s Optimized Static|Win32'.
> �
> 
> 
> ------ Clean started: Project: .stdcxx_testlocales, Configuration: 8s 
> Optimized Static Win32 ------
> 
> Deleting intermediate files and output files for project 
> '.stdcxx_testlocales', configuration '8s Optimized Static|Win32'.
> �
> 
> Martin