Message from C, C++ discussions

January 2020

— Can't share e-book though...


Guys, I've written a library, built an API and want to open source it soon but I want to stress and quailty-control it as much as I can before releasing.
Like code quality, architecture, performance, obvious dumb things....
Any suggestions?

— Every good project should have, at least:
- Continuous Integration
- Tests
- Benchmarks
- Examples
- Static analyzer/Address Sanatizer
- Build system

Message permanent page

— When we use **array[]

— No, a good project should have code that works

— That's implicit in any project. If your code doesn't work, there's no point in anything else

— Having so many things for a kinda small scale project is overkill, and kills productivity though

— Thank you.
I have all of them except CI, don't know how to do it. It's been just a private project so far.

Message permanent page

— What about code quality?

— And design?

— Don't worry, I'm still struggling with Travis. It's not something you learn in a moment

— Thanks