I just don't get where it fails from this discussion:

#include <cstdint> #include <algorithm> #include <cassert> int main(int argc, char *argv[]) { constexpr size_t length = 0x20U; uint8_t* ptr = new uint8_t[length]; for(size_t count=0; count<length; ++count) ptr[count] = count; uint8_t* dest = new uint8_t[length]; std::copy(ptr, ptr+length, dest); for(size_t count=0; count<length; ++count){ assert(ptr[count] == dest[count]); } delete[] ptr; delete[] dest; return 0; }

I tested in both c++11 and c++17.

@jsulm Thanks a lot!!! I have installed visual studio and it fixed...

@Match0um where is this declared?
int bufferSize;
if declared as member variable during initialization use like this..
bufferSize = new int(); //don't use int

Or simply use a proper Configuration class (which internally uses QSettings for example) where you can retrieve all those information from?

@jeremy_k Thanks,I want to exclude all gcc headers which is not created by myself,but comes from GCC.

@JoeCFD Thanks,I have all qmake.stash deleted,but the problem remains,and I noticed complete moc statement got printed out like this:

/usr/lib/qt5/bin/moc -DJSON_DIAGNOSTICS=0 -DJSON_USE_IMPLICIT_CONVERSIONS=1 "-DvtkRenderingCore_AUTOINIT_INCLUDE=\"/home/alex/workspace/MTESS/build/CMakeFiles/vtkModuleAutoInit_be7301261a49b13d6a9b1d9e110eacd8.h\"" -I/home/alex/workspace/MTESS/src -I/home/alex/workspace/MTESS/vendor/ProjectStructure -I/home/alex/workspace/MTESS/vendor/imgui -I/home/alex/workspace/MTESS/vendor/imgui/imgui -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/local/qwt-6.2.0/include -I/usr/local/include/opencascade -I/lib -I/usr/local/include -I/usr/include/c++/11 -I/usr/include/x86_64-linux-gnu/c++/11 -I/usr/include/c++/11/backward -I/usr/lib/llvm-14/lib/clang/14.0.0/include -I/usr/include/x86_64-linux-gnu -I/usr/include --include /home/alex/workspace/MTESS/build/MTESS_autogen/moc_predefs.h --output-dep-file -o /home/alex/workspace/MTESS/build/MTESS_autogen/MLM4FWGUYC/moc_NearFieldProcessUtil.cpp /home/alex/workspace/MTESS/src/Layers/ViewLayer/Process/NearFieldProcessUtil.h

And copy this to run in bash,it will give:

usr/include/c++/11/bits/fs_fwd.:39: Parse error at "std"

If removing:

-I/usr/local/include -I/usr/include/c++/11 -I/usr/include/x86_64-linux-gnu/c++/11 -I/usr/include/c++/11/backward

Then run:

/usr/lib/qt5/bin/moc -DJSON_DIAGNOSTICS=0 -DJSON_USE_IMPLICIT_CONVERSIONS=1 "-DvtkRenderingCore_AUTOINIT_INCLUDE=\"/home/alex/workspace/MTESS/build/CMakeFiles/vtkModuleAutoInit_be7301261a49b13d6a9b1d9e110eacd8.h\"" -I/home/alex/workspace/MTESS/src -I/home/alex/workspace/MTESS/vendor/ProjectStructure -I/home/alex/workspace/MTESS/vendor/imgui -I/home/alex/workspace/MTESS/vendor/imgui/imgui -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/local/qwt-6.2.0/include -I/usr/local/include/opencascade -I/lib -I/usr/lib/llvm-14/lib/clang/14.0.0/include -I/usr/include/x86_64-linux-gnu -I/usr/include --include /home/alex/workspace/MTESS/build/MTESS_autogen/moc_predefs.h --output-dep-file -o /home/alex/workspace/MTESS/build/MTESS_autogen/MLM4FWGUYC/moc_NearFieldProcessUtil.cpp /home/alex/workspace/MTESS/src/Layers/ViewLayer/Process/NearFieldProcessUtil.h

Expected file:

moc_NearFieldProcessUtil.cpp

got generated successfully,so question becomes:

How to tell MOC to exclude gcc related includes?

Very thank you for your reply, I found that calls your procedure, the returned is an empty image, debugging and found no trigger Qt3DRender: : QRenderCaptureReply: : completed signals, I wonder if call time is too short and not enough rendering? In addition, I would like to ask that I found the demo written by others on the Internet, as follows:
auto camSelector = this->defaultFrameGraph()->findChildQt3DRender::QCamera*();
m_cap = new Qt3DRender::QRenderCapture(camSelector);
connect(this, &Q3DShowWindow::signalGetImage,&{
QEventLoop loop;
auto reply = m_cap->requestCapture();
qDebug()<<"wait for m_returnimage finish";
connect(reply, &Qt3DRender::QRenderCaptureReply::completed, [&] {
m_returnImage = reply->image();
reply->deleteLater();
loop.quit();
});
loop.exec();
});
I found that when the signalGetImage signal is triggered, the program has been debugging information qDebug () has been unable to enter, do you know why? And how do you change the program? Looking forward to your reply!!

@Q139 said:

What methods can be used within same function to instruct compiler to compile specific code for each input variable type?

Lets say you want to do something for ints and something else for all other types:

void doSomethingWithInt(int) { qDebug() << "I'm an int"; } void doSomethingElse(auto) { qDebug() << "I'm not an int"; }

You can choose the right function at compile time with if constexpr and type traits:

template <typename T> void doStuffToOneItem(T t) { if constexpr (std::is_same_v<T,int>) doSomethingWithInt(t); else doSomethingElse(t); }

and then you can use it in a variadic function with the usual ugly parameter pack shenanigans:

template <typename ...Args> void foo(Args&&... args) { std::initializer_list<int>{(doStuffToOneItem(std::forward<Args>(args)), 0)...}; }

and call it:

foo("hello", 42, 17.3f);

Solved by changing the objects (.o) dependence sequence and using ldd / patchelf utilities, reviewing the path of the libraries that the executable depens, and the path of the libraries that the libraries depend on.

Hello guys
@jsulm @mrjj @JonB @SGaist @AnneRanch
I hope to get some thoughts on this!

@Kent-Dorfman said in code verbosity severely bugs my ADD and OCD:

If you want to be verbose then do it in comments, not code...code does NOT replace proper use of inline commenting.

I completely disagree with this statement. Verbose comments can easily get out of sync with actual code and become harmful rather than helpful. Good code should be as much self-documenting as it's possible. Of course, 30+ character variable or type name doesn't say anything good about code, if it's not possible to come up with shorter name it likely means that this variable or type does too much things and should be refactored.

@AnneRanch actually there is another wrongly placed space: at the beginning before the

..\..

@ActivateTheDroids said in What does "of" when used with QOverload do?:

why is of there?

Because of limitations in C++11.

If you have C++14 support, then you don't need of: https://doc.qt.io/qt-5/signalsandslots-syntaxes.html#selecting-overloaded-signals-and-slots

@sitesv said in std::equal_range for structs:

Is it possible to use equal_range with vector of pointers?

Yes it is, but you will have to provide the comparison function yourself.

It's all shown in the documentation that @Christian-Ehrlicher linked to.

@fcarney I will check it out but on the first view it looks like it's only reporting memory leaks and buffer overruns.

@Thank-You Declare the variable es extern in the header file and define it once somewhere in a C++ file.
See https://en.cppreference.com/w/cpp/language/storage_duration for details.
But keep in mind that QObject based classes are not allowed to be instantiated before QApplication instance is created!