3 ms·

Just tell GCC to shut up and try again, if persistent make an issue in GH. Shark used to stand for SHAred ARKitecture, since the language can compile to lua, p

Just tell GCC to shut up and try again, if persistent make an issue in GH. Shark used to stand for SHAred ARKitecture, since the language can compile to lua, python and javascript using the shared architecture found in the three. Now it stands for nothing really. Edit: Typo check O _ O

themodelplumber 4y ago
OK, I think I understood your meaning, checked with GPT just in case. > The developer's suggestion to "tell GCC to shut up" means to use the appropriate flags or options to suppress the warnings or errors generated by GCC. > There isn't a specific GCC flag to ignore unexpected arguments. However, you can use the -Wno-error flag to disable the treatment of warnings as errors, which will allow the build to continue even if warnings are generated. OK, same issue flag or no flag, guess I'll file it. Wondered if there was some release or something that was more direct than the build script, thanks. Edit: filed #1
PeterWhittaker 4y ago
> Just tell GCC to shut up and try again, if persistent make an issue in GH. That seems like a cavalier approach to type warnings. Sure, it may not be an issue, most of the time, but type warnings are there to highlight/suggest potentially bad code, e.g., poorly thought out or insufficient consideration given to typing, overflows, etc. For a one-off or bit of hobby code, I'm quite happy to compile without warnings and/or to ignore whatever warnings my code generates, but for something I am sharing with others, especially releasing and hoping they will adopt, I crank the warnings to 11 and make sure compiles are clean, without pragmas.
- shogundev 4y ago
  The code compiles and runs very cleanly and smoothly under win32 and linux mint. This is probably an issue of size_t being different sized in a platform or the code using int64_t everywhere but int is 32 bit. Thanks (and is not ironic). Shogun
  - PeterWhittaker 4y ago
    Perhaps use zu instead of d as the format specifier for size_t types?

themodelplumber 4y ago

OK, I think I understood your meaning, checked with GPT just in case. > The developer's suggestion to "tell GCC to shut up" means to use the appropriate flags or options to suppress the warnings or errors generated by GCC. > There isn't a specific GCC flag to ignore unexpected arguments. However, you can use the -Wno-error flag to disable the treatment of warnings as errors, which will allow the build to continue even if warnings are generated. OK, same issue flag or no flag, guess I'll file it. Wondered if there was some release or something that was more direct than the build script, thanks. Edit: filed #1

PeterWhittaker 4y ago

> Just tell GCC to shut up and try again, if persistent make an issue in GH. That seems like a cavalier approach to type warnings. Sure, it may not be an issue, most of the time, but type warnings are there to highlight/suggest potentially bad code, e.g., poorly thought out or insufficient consideration given to typing, overflows, etc. For a one-off or bit of hobby code, I'm quite happy to compile without warnings and/or to ignore whatever warnings my code generates, but for something I am sharing with others, especially releasing and hoping they will adopt, I crank the warnings to 11 and make sure compiles are clean, without pragmas.

shogundev 4y ago
The code compiles and runs very cleanly and smoothly under win32 and linux mint. This is probably an issue of size_t being different sized in a platform or the code using int64_t everywhere but int is 32 bit. Thanks (and is not ironic). Shogun
- PeterWhittaker 4y ago
  Perhaps use zu instead of d as the format specifier for size_t types?