cppfront
cppfront copied to clipboard
hsutter
A personal experimental C++ Syntax 2 -> Syntax 1 compiler
This provides a simple solution to issue #1436 based on a the following comment `"break" won't [work] until we do extra work to implement that using a flag and implementing...
**Describe the bug** A Cpp2 for loop that uses 'next' is implemented as a do { } while(false) loop inside the main loop -- and the 'next' is done right...
All credit goes to @JohelEGP for this -- it just scratched an itch I've felt for a long while, so I rebased and updated it. Should fix #542 and #1343.
My OS just got GCC 15 as its default compiler, so I added the relevant infrastructure to support it. There was only one minor change from GCC 14.
Enumeration in C++1 is trivial; it should be trivial in C++2 as well. ```cpp // cpp1 enum class Foo { A, B, C, }; // cpp2 Bar: @enum type =...
Move the construction of the OOB violation string to after the OOB check fails so that the code is not allocating, concatenating and freeing strings that are never used in...
Providing a negative number as the start of a for-range produces broken cpp1 code: the `-` negative is parsed to apply to the resulting range object rather than the number...
**Describe the bug** When compiling, it appears this error, which I tried to fix by following the instructions: "in Cpp2, write 'using the_namespace_name::_' to bring all names in the namespace...
**Describe the bug** The simple hello example successfully processed by cppfront v0.7.3, but cppfront >v0.8.x emit uncompilable C++ code **To Reproduce** Steps to reproduce the behavior: 1. `main: () =...
**Describe the bug** When using R string literals for usage documentation and other longer things I found an odd parse issue. If you use an open parenthesis inside the R...
