Thanks for the reply, one more question. Am I to use -std=gnu++1y, in addition
-std=c++14 or should I remove -std=c++14. TIA
From: Riot
Sent: Wednesday, July 15, 2015 8:40 PM
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] [[deprecated]]
Use -std=gnu++1y
On 16 Jul 2
Yes, Riot, that was exactly what I was looking for. An example always goes a
long, long way. Thanks so much.
Ruben, thanks s much for the links. Those links answer all the questions
I had about GCC support for c++11/14. Thanks man!
-Original Message-
From: Riot
Sent: Wednesday, July
C++14 includes the [[deprecated("reason")]] attribute, but in my MinGW-64 with
GCC-5.1 it creates a warning saying:
warning: 'deprecated' attribute directive ignored [-Wattributes]|
How can I find out which features of C++11 and C++14 are available in g++5.1?
Thanks--
You know what, it is true, I forgot the main(), but, bud, you nailed it!
Ruben, it seems to me that you have a crystal ball or perhaps, somehow, you are
able to access my computer and thus find out exactly what I mean, since I
cannot, sometimes, express myself in the best way possible. If you don
Can anyone, pleeese, tell me why this extractor operator is not causing this
error:
C:\tmp\adfs\main.cpp|20|error: no match for 'operator<<' (operand types are
'std::wostream {aka std::basic_ostream}' and
'std::unique_ptr')|
namespace abc{
class MyClass{
private:
int nuestro;
public
In an earlier and a different posting, I express my concern about
MS-Windows' std::string/locales, what is the point of wstring, I asked, if
at the end there is no reliable uft-8/16/32 support for. them. The best
thing to do is to use boost's or some other 3rd party, if true utf support
is need
This one is way cooler
http://www.bing.com/search?q=toupper&src=IE-TopResult&FORM=IETR02&conversationid=
From: Alexandre Pereira Nunes
Sent: Tuesday, June 30, 2015 7:37 PM
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] toUpper()
[cut]
This may also help in future:
std::wstring source(L"Hello World");
std::wstring destination;
destination.resize(source.size());
std::transform (source.begin(), source.end(), destination.begin(),
(int(*)(int))std::toupper);
The above code is what did the trick, do not ask how, I am still digesting
it. However, any suggestions
In this web page:
http://en.cppreference.com/w/cpp/locale/toupper
I got this code:
#include
#include
#include
int main()
{
wchar_t c = L'\u017f'; // Latin small letter Long S ('ſ')
std::cout << std::hex << std::showbase;
std::cout << "in the default locale, toupper(" << (std::wint_
I would like to write a function to capitalize letters, say...
std::wstring toUpper(const std::wstring wstr){
for ( auto it = wstr.begin(); it != wstr.end(); ++it){
global_wapstr.append(std::towupper(&it));
}
}
This doesn’t work, but doesn’t the standard already have something like
std::
I have been reading that wchat_t, and therefore wstring, is neither UTF-8 nor a
UTF-16 character set. So, what is wstring good for then?
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
--
Thanks for the help Alexandre.
Look man, it could not have at a better time; porting the code from VC++ to g++
has not been a easy thing for me, I am so used to the flexibility of VS that
now that I am using the actual C++ standard I realize the facilities and traps
provided Microsoft. The last
The latest MinGW64 complains about this code:
#include
#include
#include
bool abc::Sound::PlayIt(){
//return !!sndPlaySoundW(Soundfile.c_str(), SND_FILENAME);
return !!PlaySoundW(Soundfile.c_str(), NULL, SND_FILENAME/*SND_ASYNC*/);
}
It says
In function `abc::Sound::PlayIt()':
C:/Win32
The standard C++ has major, and I mean MAJOR draw-back!!
It cannot handle any other stream format that ASCII. 1988 standards in 2015? I
cannot believe it!!
I am sure that there are 3rd or 4th party libraries that can handle this issue,
but than again, that is that... a 3rd || 4th party library.
I
Nice, thank you, I took your advice. I have now modify the code. I have other
problems, though.
This code:
std::wifstream infile;
infile.open( getFileName().c_str() );
error: no matching function for call to
'std::basic_ifstream::open(const wchar_t*)'
I found this discussion
http://stackoverfl
Thanks Ruben for the help.
To answer your question, yes, I am.
I was also using -std=gnu++14. However, I am now compiling only with
–std::c++11, but to no avail.
From: Ruben Van Boxem
Sent: Monday, June 29, 2015 2:27 AM
To: mingw-w64-public@lists.sourceforge.net
Subject: Re: [Mingw-w64-public] th
In VS2013, I declare the member functions like this:
void setString(const std::wstring& _str) throw(...);
But now that I am switching to MinGW, I get a complain from the compiler saying:
error: expected type-specifier before '...' token
throw(...) {
How can I fix this problem?
Thanks
---
This e
17 matches
Mail list logo
