Warning Clean-up?

[abellgithub]

Hi,

Is there any opposition to cleaning-up code to eliminate clang compiler warnings?

[hoffstadt]

Absolutely no opposition at all.

As an FYI, we are in the process of cleaning up the codebase and restructuring a lot. It has gone through several phases. It started out heavily OOP and has gone through several style changes (which have left everything a bit of a mess). The final "form" we are trying to get to... mostly C style and simple build scripts. No C++ stl. Only using a few C++ features: namespaces, function overloads, lambdas, and that's about it (handmade hero style). Hoping to salvage the repo(private at the moment).

[abellgithub]

I understand the first sentence. After that I'm confused. You're totally reworking this in private? With no STL because...?

Unless I'm missing something, It doesn't sound like it's worth any time on my part doing any maintenance unless I'm going to fork this and use it as is, right?

[hoffstadt]

I'm so sorry for the late response (new job, new second child, and busy). Private in the sense that we were doing a lot of prototyping and the repo's weren't public.

I'm sure you are already aware since its been months, but most of our efforts are in stability, simplification, and fixes for DPG 1.

Any effort is appreciated and not wasted. We will keep this repo running and working for the long term though our time will be split between this and pilotlight which DPG 2 will be built on top of. We are still in the early stages there.

In that repo we will be sticking to C99 (and some objective C for apple devices). No libraries. No build systems. Simple.