That's not perceived bloat just from reading documentation, which is what the person I was responding to seemed to say. I feel like a hypothetical NROM-128 project is outside that context. But I still disagree with the premise. If you're making an NROM-128 project you could still get more mileage for size out of assembly than the "bloated" by comparison C, right? "But someone could care less about the size benefit of assembly and care more about the time it takes to write in an NROM-256 project." Yes. Sure. Okay.tepples wrote: Or someone doesn't care about micro-optimizations for speed but does care about them for size in an NROM-128 project.
I guess in general, I feel that while the information presented may add to the thread, I feel that because it's posted as a reply to me, but not as a reply to what I feel like I said that confuses me about how to respond. I answered about features from C++ I use that aren't templates, it doesn't mean there's never a reason not to use them. I can see how that can maybe be gotten from "I don't have a reason to use Y", but I'd have said "There's no reason to use Y" if I meant that.
Heheh! I know of it. It might be interesting to start a C/++ resource thread, but there's not much I can personally cosign as "used in an actual project".thefox wrote:This library is pretty sweet: https://github.com/fmtlib/fmt