User forums > Using Code::Blocks

Avoid warning "command line option "-std=c++0x" is valid for C+"

<< < (2/2)

Alpha:
Although, reading back through the code now,

--- Code: (sdk/compilercommandgenorator.cpp:365) ---    wxString cFlags  = m_CFlags[target];
    wxArrayString remFlags;
    if (compExec == ceC)
        remFlags = GetArrayFromString(compiler->GetCPPOnlyFlags(), wxT(" "));
    else if (compExec == ceCPP)
        remFlags = GetArrayFromString(compiler->GetCOnlyFlags(), wxT(" "));
    if (!remFlags.IsEmpty())
    {
        wxArrayString aCflags = GetArrayFromString(cFlags, wxT(" "));
        for (size_t i = 0; i < remFlags.GetCount(); ++i)
        {
            int index = aCflags.Index(remFlags[i]);
            if (index != wxNOT_FOUND)
                aCflags.RemoveAt(index);
        }
        cFlags = GetStringFromArray(aCflags, wxT(" "), false);
    }

--- End code ---
might be performance critical.

oBFusCATed:
So if I understand you correctly this is a non-issue in trunk (the flag is not passed to gcc)?

Looking at it - I see that it is bloody dangerous wxArrayString based code! :)

Alpha:

--- Quote from: oBFusCATed on September 13, 2013, 04:39:07 pm ---So if I understand you correctly this is a non-issue in trunk (the flag is not passed to gcc)?

--- End quote ---
Yes.


--- Quote from: oBFusCATed on September 13, 2013, 04:39:07 pm ---Looking at it - I see that it is bloody dangerous wxArrayString based code! :)

--- End quote ---
At some point I want to rewrite this... as my time allows.

Navigation

[0] Message Index

[*] Previous page