X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Subject: Re: DJGPP doesn't support std::wstring? To: djgpp AT delorie DOT com References: <59728009 DOT 7010801 AT gmx DOT de> <5ba63d08-999c-db29-3e59-5feca8f71c38 AT iki DOT fi> <597482DE DOT 2010800 AT gmx DOT de> <5974A319 DOT 8070300 AT gmx DOT de> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" Message-ID: <718a3b5c-a24d-e8b7-0ea6-6e96bac96c9e@iki.fi> Date: Wed, 2 Aug 2017 17:45:56 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <5974A319.8070300@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 07/23/2017 04:22 PM, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com] wrote: > > > I do not understand what are the impediments to commit what we already have > (aka wchar.zip and after having fixed everthing). There is absolute no > release planed for the near future so we have years ahead to adjust the > code of wchar.zip and to implement what is possible to implement at all > and to fix the issues that all this may rise. > > As I have tried to explained, all the code is a simple copy of the equivalent > char versions. Thus there should neither be a copyright issue nor a quality > or functional issue. I am writting some small testsuite for the existing code > that shall reveal issues. It may be added to the repository if the wide char > stuff is added to the repository. > Well. I'm simply afraid that otherwise we'll (or somebody else who will be around then) will have the same discussion sometimes in the future similarly as it it was already discussed almost 20 year ago and got forgotten. Andris