Thanks! Not even sure how you found it .
I'm fine either way.
Thanks! Not even sure how you found it .
I'm fine either way.
It's a matter of using the correct filter. The PR is closed, you are the author and donovaly did the review. So, you get this filterThanks! Not even sure how you found it
Code: Select all
is:closed is:pr author:AjinkyaDahale mentions:donovaly
doesn't mentions:donovaly only work if someone writes @donovaly somewhere? I would think commenter:donovaly would be a more complete filterwmayer wrote: ↑Wed Apr 20, 2022 10:38 amCode: Select all
is:closed is:pr author:AjinkyaDahale mentions:donovaly
Nice, it's good to see new people with this attitude. I would recommend limiting the scope of your changes and submitting a PR to get feedback and know if you're on the right track. It's also easier to get your changes in if it's not a massive PR.
Thanks for the info, Werner and Adrian.adrianinsaval wrote: ↑Wed Apr 20, 2022 3:11 pm doesn't mentions:donovaly only work if someone writes @donovaly somewhere? I would think commenter:donovaly would be a more complete filter
From https://en.cppreference.com/w/cpp/language/identifierswmayer wrote: ↑Wed Apr 20, 2022 7:56 amConcrete example?FreddyFreddy wrote: ↑Wed Apr 20, 2022 7:29 am The latter (leading _) I understand is all about not polluting the global space (plenty of that here). Not hard to fix, but might need some concensus on naming convention. Any inputs?
Example in exception.cppA valid identifier must begin with a non-digit character ... exceptions:the identifiers with a double underscore anywhere are reserved;
the identifiers that begin with an underscore followed by an uppercase letter are reserved;
the identifiers that begin with an underscore are reserved in the global namespace.
"Reserved" here means that the standard library headers #define or declare such identifiers for their internal needs, the compiler may predefine non-standard identifiers of that kind, and that name mangling algorithm may assume that some of these identifiers are not in use. If the programmer uses such identifiers, the behavior is undefined.
Code: Select all
'static PyMethodDef* __AppMethods = nullptr;
Thx.FreddyFreddy wrote: ↑Wed Apr 20, 2022 10:10 pm From https://en.cppreference.com/w/cpp/language/identifiers
It's in Application.cpp.
The easiest is to move the variable into anonymous namespace which is in anyway the preferred way in modern C++.the identifiers with a double underscore anywhere are reserved;
the identifiers that begin with an underscore are reserved in the global namespace.
Code: Select all
namespace {
static PyMethodDef* AppMethods = nullptr;
}
Seems to work with a bunch of editors/ide's. I think a file is placed in the project root. CLion for example will use it if it is there. It can be initialised from quite a long list of defaults. qt was mentioned here previously. I don't see that listed in cmake doc, but it is one option in CLion.cmake-format can format your listfiles nicely so that they don’t look like crap.