A C23, GCC question: The first line of code here causes `-Wold-style-declaration` warning in GCC 13.1. Is this warning because GCC's C23 implementation of placeholder type `auto` is not yet complete?

https://sigcpp.godbolt.org/z/6Yos9oMch

#C #C23 #programming #godbolt

Dev: decltype(n) and typeof(n) for "strong typing"
C, C++: error: increment of read-only variable '**i**'
Dev: Not like that

(Sure, range-for avoids the issue **in this case** but you've to admit that the core issue is sneaky. Also, there is no range-for in C.)

https://sigcpp.godbolt.org/z/zsfTszW4d

#c #cpp #cplusplus #godbolt

Programmatically enabling assertions in Java, even if assertions are not enabled on the cmd line when JVM was started (`-ea` was not included in the cmd line).

Works for classes yet to be loaded by a specific class loader. For illustration, uses the loader for the class containing the `main` method.

Results subject to any selective enabling/disabling of assertions on command line. See Java docs.

CE: https://sigcpp.godbolt.org/z/bE34a5E6f

#java #programming #godbolt

What's the best and most convenient way to look at how #SwiftLang translates to #ARM64, given that #Godbolt #CompilerExplorer doesn't currently support Swift -> ARM64?

https://github.com/compiler-explorer/compiler-explorer/discussions/4400

So, I was writing some C, and I've learned that shis thing compiles and runs. Anyone here knew this, and why?
https://godbolt.org/z/vEasn57oo Also godbolt shows wiggly red lines without any error present.

#godbolt #c #til

Am I the only one who has their downloads folder filled with "Compiler Explorer C++ Editor #1 Code (N).cpp" files because they keep pressing Ctrl+S accidentally? #godbolt

Awesome C++ folks -
1. Does godbolt support gdb debugging?
2. I've a sample C++ code on #godbolt, to run on ARM gcc compiler. Need a print to understand a behavior. Obviously, std::cout not working. Any other option? FYI @mattgodbolt
#cpp #cplusplus #embedded #debug #print #dev #programming #programmer #ARM