I hear crickets chirping
-
@SimonSchroeder
If you want to be picky, it presumably won't compile with warnings -> errors as theintfunction does notreturnanything ;-)@JonB since C++11 int main() has, as the only case in the whole standard, an implicit return value and not writing your own return 0 is completely valid.
Do not flame on me, I do not agree with this decision
Be aware of the Qt Code of Conduct, when posting : https://forum.qt.io/topic/113070/qt-code-of-conduct
Q: What's that?
A: It's blue light.
Q: What does it do?
A: It turns blue. -
@JonB since C++11 int main() has, as the only case in the whole standard, an implicit return value and not writing your own return 0 is completely valid.
Do not flame on me, I do not agree with this decision
-
@J.Hilk Really? That's ridiculous! It's a non-void function, so it needs a
return, simplez ;-) -
@JonB since C++11 int main() has, as the only case in the whole standard, an implicit return value and not writing your own return 0 is completely valid.
Do not flame on me, I do not agree with this decision
@J.Hilk said in I hear crickets chirping:
@JonB since C++11 int main() has, as the only case in the whole standard, an implicit return value and not writing your own return 0 is completely valid.
Do not flame on me, I do not agree with this decision
Nor do I. Hidden or implicit actions are not a good thing.
I wonder what would happen if you explicitly define
void main() {}
Since the startup code only cares about the symbol, not its type.
c++ test.cc test.cc:15:1: error: ‘::main’ must return ‘int’ 15 | void main() { | ^~~~Well, there you have it.
-
Doesn't anyone have any esoteric C++ incantations to discuss. It's too quiet in here.
@Kent-Dorfman said in I hear crickets chirping:
Doesn't anyone have any esoteric C++ incantations to discuss. It's too quiet in here.
Change of topic: I recently found some esoteric C++ incantations: a
constexprcounter based on template instantiation: https://b.atch.se/posts/constexpr-counter/ . However, it seems that this behavior is about to be deprecated (you cannot rely on the order templates are instantiated). At the same time, something quite similar has occured in one of the reflection examples (https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p2996r12.html Chapter 3.17 "Compile-Time Ticket Counter"). This reflection proposal has been accepted, so we might be able to safely do a constexpr counter through reflection starting with C++26.
