News for hackers. Stuff that matters.

A comment on A Special Kind of Hell: intmax_t in C and C++. Parent comment

Re:A Special Kind of Hell: intmax_t in C and C++ by jcelerier on Saturday December 05, 2020 @05:29PM (#25319030)
> Oh but there is :) As a library author I really don't want to dictate users what compiler to use,

sure, there's nothing wrong with self-inflicted pain. Rust shows that a compiler monoculture works much better in practice.

[ Parent | on HN ]
Re:A Special Kind of Hell: intmax_t in C and C++ by pjmlp on Sunday December 06, 2020 @02:05AM (#25321740)
When everything you need is Linux.
[ Parent | on HN ]
Re:A Special Kind of Hell: intmax_t in C and C++ by jcelerier on Sunday December 06, 2020 @05:19AM (#25322514)
I use a clang/libc++ toolchain to target Linux, macOS and Windows - works like a charm. It's also the toolchain used by Android and iOS, and I could also do some WASM with it. So portability here is definitely not an issue to me
[ Parent | on HN ]
Re:A Special Kind of Hell: intmax_t in C and C++ by pjmlp on Sunday December 06, 2020 @09:05AM (#25323526)
A small portion of operating systems and CPUs available in the market.

I thought the message was about everyone not your bubble.

[ Parent | on HN ]
Re:A Special Kind of Hell: intmax_t in C and C++ by jcelerier on Sunday December 06, 2020 @02:08PM (#25325768)
c'mon, clang is able to target x86&64, ARM, AArch64, MIPS, AVR, RISC-V, WASM among others - those combined are 99.9% of the market (and 100% of the market for desktop apps).
[ Parent | on HN ]
Re:A Special Kind of Hell: intmax_t in C and C++ by pjmlp on Sunday December 06, 2020 @04:04PM (#25326617)
Among others is still a smaller pie than either GCC or vendor specific compilers on embedded systems CPUs and operating systems.
[ Parent | on HN ]