Conversation
|
|
|
Didn't notice this repo was using C99. |
|
Could you share the specific compiler warnings you're seeing? That would help us understand what's being triggered and evaluate the best way to address or silence them. |
|
This is with clang |
|
And with MSVC: |
|
We use To silence the warning, just add |
|
Wouldn't it be more user-friendly to silence these warning from the library's side? |
|
And GCC doesn't report any warnings. By high warning, I mean |
True, that's a fair point. The issue is that I don't have access to a Windows machine, so I don't see these warnings on my side. Fixing it from my end would mean coding blindly, which I try to avoid. I rely on GitHub Actions to catch platform-specific warnings, and I do my best to address them when I can see what’s going on. If you have a clean way to silence just this warning within the library, feel free to suggest it. |
|
Both clang and MSVC suggest adding the same |
This reverts commit beb44ec.
|
Had to add a guarded pragma because sprintf warnings were comming from a header file. |
|
Interesting, I’ll look into it. What are you using PlutoSVG for, by the way? If you’re keen, I’d love to hear more. |
|
Technically MSVC doesn't need |
Currently, I'm only using it for emoji rendering with FreeType library in my game (engine), I'll probably use it for "real" SVG rendering to be able to use SVG assets in the future. |
Nice, that sounds great. It’s late here, so I’m signing off for now. Bye! |
sprintf_s instead of sprintf|
I wasn't able to test this on my side, though. Note: CMake considers both |
|
Wouldn't be easier to just use |
|
@rasky thanks for your suggestion. |
Sadly no, using The only way to silence I don't have any Mac/Hackintosh machines to test macOS builds, and I can't see why macOS |
Makes PlutoSVG more secure (theoretically) and silences compiler warnings at high settings.