Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There are a TON of warnings #126

Open
moon-chilled opened this issue Mar 17, 2017 · 3 comments
Open

There are a TON of warnings #126

moon-chilled opened this issue Mar 17, 2017 · 3 comments
Assignees
Labels

Comments

@moon-chilled
Copy link

If you want, I can try to clean some of them up and make a PR, but there are a TON of them

@thebracket thebracket self-assigned this Mar 17, 2017
@thebracket thebracket added the bug label Mar 17, 2017
@thebracket
Copy link
Owner

You're absolutely right - there are a ton of warnings (depending upon which compiler you use, there are even more - GCC gives a lot more than Clang). My goal is to do a big cleanup on that (and some global variable issues) soon, but I want to stabilize some architecture decisions first. Thanks!

@thebracket
Copy link
Owner

thebracket commented Apr 6, 2017

Two changes to RLTK just went up that massively reduced the number of warnings (especially on Clang). I'd omitted some braces in an initializer list (it still worked, oddly), in each and each_if - which are used everywhere. That's a good start! (I'll have the RLTK link updated in the main source shortly)

@thebracket
Copy link
Owner

I just went on a big warning hunt, and removed a LOT of warnings from Clang builds. I'll have to do the same for GCC, but not today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants