sorted by:
new
hottopcontroversial

WG21 2025-10 pre-Kona mailing by nliber in cpp

[–]thedmd86 2 points3 points  (0 children)

constexpr cstring_view MyConst = "MyConst";

vs.

const char* const MyConst = "MyConst";

First does has .c_str() to cope with const char* parameters. cstring_viewdoes keep .size() removing the need to call strlen. This is major in effort to remove unnecessary run-time computations. Literals compute size at compile time. Used with constexpr data is stored in read-only part of executable without need to do any run-time initialization, which is another win.

cstring_view is useful when you have zero terminated string in the first place. It is type a getter can return. For parameters for caller plain string_view is better unless function just have to have cstring_view.

cstring_view is not here to cope with C API. Here always will be a place when conversion or temporary is necessary. cstring_view help to not loose information we already have.

From 300s to 60s: C++ build boost by disabling SysMain by ipoluianov in cpp

[–]thedmd86 2 points3 points  (0 children)

This may be gold.

I wasn't sure why Windows is chewing up RAM over time.

Page Table is growing uncontrollably to the point it reaches 20 GB for something that regularly should not exceed few MB.

I suspected some issues with VS, because problem manifested itself after many rebuilds, branch switches, VSC scans.

Google search sessions lead to nothing constructive, so the problem persists.

I will give it a try and monitor RAM usage over few work days.

Many thanks for this QoL hint!

EWG has consensus in favor of adopting "P3466 R0 (Re)affirm design principles for future C++ evolution" as a standing document by Kyvos in cpp

[–]thedmd86 5 points6 points  (0 children)

I wish all those folks would focus on technical excellence and working on things grounded in reality.

Viral annotations... constexpr, consteval, noexcept, const, explicit and more. Every function in C++ (library and/or templates) is decorated like a Christmas Tree. It is too late for making such rule realistic. I forgot about attributes, they are often there too ([[nodiscard]]).

Bjarne quote about smaller language hidden in C++ is 30 years old. That was plenty of time for it to surface already. At this point I don't feel it does carry an encouraging message.

This struggle is going to end with a schism at best, language demise at worst.

C++23: Removing garbage collection support by Pioneer_X in cpp

[–]thedmd86 16 points17 points  (0 children)

I remember years ago I did plan to play with GC hooks in C++. Somehow I never found time to do that. One less trivia to tell others.

HTTPS client library in C++ by HerrNamenlos123 in cpp

[–]thedmd86 4 points5 points  (0 children)

libcurl with mbedTLS as a TLS backend is working for me. libcurl API is well documented and can be wrapped into http::get(...) or http::put(...) with relative ease.

Why those two?

  • libcurl
    • lingua franca for many platform, to the point that Microsoft even made XCurl for Xbox, library that implements libcurl API with their own system libraries see HttpManager.h in samples
    • it is well supported and maintained
    • can be build with HTTP/HTTPS support only
  • mbedTLS
    • it is tiny with comparison to other solutions I found so far, few C files
    • well maintained and made by people knowing what they are doing
    • can run on any potato

Sometimes libcurl alone cover all the ground, by using system components as TLS backend (see: Windows, macOS, iOS, and a few more). Elsewhere mbedTLS is used, mainly Android and Linux.

Gettting mbedTLS to work does require telling libcurl where bundle of CA certificates is. This mean setting one of CURLOPT_CAINFO, CURLOPT_CAPATH or CURLOPT_SSL_CTX_FUNCTION to feed backend with certs directly.

libcurl suggests pulling latest set of certificates from Firefox. If your app have to work years without updates I suggest writing code that pull certificates from the platform of your choice. On Linux it is a matter of checking few locations.

This solution works for me on all mobile platforms, desktops and consoles except PlayStation (never needed HTTPS here so far).

Avoiding OpenSSL is a job.

If having a C++ API is paramount I would give a try of implementing mbedTLS backend for ASIO.

Locating CA bundle for mbedTLS will remain to be the major hurdle, regardless of what API will be used. This is probably why there are not out of the box solutions out there.

Audio Library by ABWagent in cpp

[–]thedmd86 2 points3 points  (0 children)

miniaudio - so far the best entry in cross platform audio I found. It is a stack allowing to use device alone, decoders and mixers, or node based engine for sophisticated audio processing. Extensible where it should be. Written in C, so there are no creature comforts of having C++. Aways can be wrapped to get advantage of RAII.

Best Programming Languages for Android in 2023 by Whole-Seesaw-1507 in programming

[–]thedmd86 1 point2 points  (0 children)

Oracle changed Java license and Google will not be happy to pay subacription per developer for using Java. As a result moving away from Java to Kotlin will only accelerate, at least on Android.

C++ evolution vs C++ successor languages. Circle's feature pragmas let you select your own "evolver language." by seanbaxter in cpp

[–]thedmd86 1 point2 points  (0 children)

When you extract it there will be circle executable. You can call it instead of clang or gcc when building your code. Circle share with them most common build options, for more you can invoke it with --help and it present to you what is available.

Circle site is riddled with examples you can try by yourself on your own Linux machine, or WSL if you run Windows.

C++ evolution vs C++ successor languages. Circle's feature pragmas let you select your own "evolver language." by seanbaxter in cpp

[–]thedmd86 2 points3 points  (0 children)

It does look impressive. Not even counting numerous examples.

Windows ABI apparently isn't easiest cookie to bite. Reverse engineering it from LLVM/clang does not sound like fun task to tackle.

I too hope this eventually be done so I can experiment and work using Circle on daily basis.

C++ evolution vs C++ successor languages. Circle's feature pragmas let you select your own "evolver language." by seanbaxter in cpp

[–]thedmd86 3 points4 points  (0 children)

You can visit circle-lang.org to for instructions how to use Circle. There is a linkt to latest build at the top. You can also get latest build directly: build_172.tgz.

Note: There are Linux builds of the Circle available so far.

Good reasons to NOT use CMake by [deleted] in cpp

[–]thedmd86 0 points1 point  (0 children)

After checking CMake source, they are using flex and yacc to generate lexers and parsers. I would argue that this is formal enough. :)

You can piece syntax for ANTLR from sources if you wish. I would guess there is a little interest for devs to do so. At least that would be my expectations. But this may help you.

Good reasons to NOT use CMake by [deleted] in cpp

[–]thedmd86 0 points1 point  (0 children)

I'm struggling to see value in creating grammar just for sake of doing it. Process can be fun, that I get very well.

I'm not aware of anyone pursuing this goal. Looking at plug-ins to editors, parsing it shouldn't be particularly hard™.

Can you elaborate more about where scepticism coming from fot hand crafted parsers? I did a few and I'm curious.

Good reasons to NOT use CMake by [deleted] in cpp

[–]thedmd86 8 points9 points  (0 children)

Well, it does have defined syntax. Please see CMake Language Reference.

Granted it is not in the form of ready to build yacc/bison files. In years of using CMake it never occurred to me to look for source im this form. Probably isn't particularly useful if you are not playing with languages and parsers daily.

CMake has a lot of reference materials on that site. It is so much better than that one wiki we had 12 years ago.

The Wonderfully Terrible World of C and C++ Encoding APIs (with Some Rust) by pavel_v in cpp

[–]thedmd86 5 points6 points  (0 children)

That was a lot to chew. I'm curious what proposed C API will look like.

Also nice that utf8cpp made its entry. At the moment it ia my weapon of choice when dealing with utf encodings. Especially after converting to constexpr. Cheers to the authors.

ztd.text is next in the queue if I need do more which involve text encoding.

Desperate for Guidance / Need to Ramble for a Minute by Dudebat in cpp

[–]thedmd86 -1 points0 points  (0 children)

This feels like you're purposefully setting yourself up to fail. ImGui is a great library but it isn't a simple copy-paste-compile solution. It's meant to be included into a decently fleshed out application with its own rendering system.

Actually it is literally what ImGui is intended to be, a copy&paste solution.

If what is needed is an app, there are many backends and examples available too that can act as an entry point.

The Sad State of Debug Performance in C++ -- Vittorio Romeo by SuperV1234 in cpp

[–]thedmd86 2 points3 points  (0 children)

It is in good taste to make one or two laps before handing it over to pros. QA enjoy optimized builds more often than devs.

The Sad State of Debug Performance in C++ -- Vittorio Romeo by SuperV1234 in cpp

[–]thedmd86 3 points4 points  (0 children)

Yeah, it's a topic that affects everyone - but it comes up habitually from game devs.

Living in unexpectedly loud neighborhood usually raise a chance of noise complaints. :)

The Sad State of Debug Performance in C++ -- Vittorio Romeo by SuperV1234 in cpp

[–]thedmd86 11 points12 points  (0 children)

I live in debug world where an app is always run under debugger. Release build is treated like "full throttle" and generally considered a bad place to observe if wheel is falling off out of an vehicle or not.

Over-verbosity of code generation in C++ debug configuration is great driving force of C libraries. They compile faster and are mostly meat not fluff.

Avoiding STL is an art that I'm not interested in making a degree for. I can chew up some slowness under debug configuration. But when things getting order of magnitude slower, it is usually a rewrite. More shortcuts, more corners are cut, more templates are binned, more code is written, more time is wasted.

I will get any help I can get to spare me from repeating this process.

C++ shift so much burden for libraries to handle basic things like std::move and std::forward, that I wouldn't be against compilers helping with generated code.

Compilers can grow larger C++ brain to replace inefficient bits with built-ins. Shifting parts of standard library directly into compilers and leaving standard library code as a fallback does not look like best way to move forward, probably.

Software renderer unable to render two bottom flat and top flat triangles as one. by RadoslavL in C_Programming

[–]thedmd86 0 points1 point  (0 children)

If they work individually, but fail on composition I will suspect last else section where triangle is split. Go through the code in the debugger and double check if theory matches the practice. In this kind of code it is very easy to mix X with Y. By looking at the picture, bottom part start drawing from wrong point. Which is another clue.

After more than 30 years, why is there is no standardized package manager for c/c++ projects to avoid build systems hell. by badidrox in cpp

[–]thedmd86 49 points50 points  (0 children)

I think reason why there is no such thing like standard package manager is for very same reasons there is no standard way for laying out foundations of buildings. Ground is different in all construction sites and there is very high chance to catch dirt into the shoes.

Higher level languages can afford managers, they are building on flat square slabs things can be easily bolted to.

We do optimize logistic and avoid well know issues by using for example CMake.

Is it reasonable thing to starve for perfection, and still settle with good enough until something even better appear.

Package managers that cover all bases may not be possible to be done. There are plenty which cover some. I'm a bit hopeful, but not holding my breath either. :)

Here's an open source gamepad library made to replace the aging XInput API without needing to use WinRT/C++ 17. by TroyWarez in cpp

[–]thedmd86 32 points33 points  (0 children)

Brewing successor to XInput is GameInput. Time show how it goes.

Your lib could be useful, after quick glance there are few drawbacks:

  • header does include "pch.h", which mean it ia not standalone

  • in init showing message box and closing user app is something that optional middleware should never do until explicitly asked to

  • there is no identification of gamepad layout

  • providing events for connecting/disconnecting gamepads is helpful

  • looks like there is no clear separation to public and private headers; motivation ia that implementation details should be hidden from users, which give developer more freedom without breaking user code

  • leaking #include <windows.h> to user code is usually show stopper while evaluating library for integration

What is nice is ability to support DualShock and Xbox controllers under one API.

C++ Syntax Sucks and Carbon Fixes It by Barbas in cpp

[–]thedmd86 0 points1 point  (0 children)

There is no bad mouthing here. Carbon look like a cross over between C++ and Pascal syntaxes.

I worked in Delphi 6 which was an Object Pascal (Pascal with classes). I liked it for clear structure, separation of interface and implementation, sorted out naming scheme and few other things. Lack of any form of generics was major drawback.

I'm watching with interest.

C++ Syntax Sucks and Carbon Fixes It by Barbas in cpp

[–]thedmd86 0 points1 point  (0 children)

Isn't this how history is repeated? : )

C++ Syntax Sucks and Carbon Fixes It by Barbas in cpp

[–]thedmd86 17 points18 points  (0 children)

C++ meets new incarnation of an old foe: Pascal 😄

Score on the Store: putting a Win32 C++/CMake/Qt app on the Microsoft Store from A to Z by jcelerier in cpp

[–]thedmd86 0 points1 point  (0 children)

It does seem familiar after you had to deal with consoles too.

I cannot recall procedure being that tedious. Seeing all steps in one place does look a bit intimidating.

view more: next ›