Used all of these three. I don’t want to even look at MS Visual C/C++ ecosystem.

  • JGrffn@lemmy.ml
    link
    fedilink
    arrow-up
    31
    arrow-down
    1
    ·
    1 year ago

    I haven’t touched compilers in a while, but I was a dirty little MS pig boy back in college. Qt with MSVC just made sense for me, with the single exception of non standard byte lengths for longs (almost cost me a class due to not using std uints, totally my bad but you don’t really expect compilers to understand basic data types differently).

    The true shitfuckassface experience for me was ICC. Stupid little pig boy decided he wanted his Qt working with ICC, due to all dem optimizations for Intel CPUs. After hours of debugging nonsense errors and janking my way through Qt code which was way above my head, I finally got a Qt build, only to have ICC find thousands of completely removed errors in a project where no other compiler would find errors.

    Yeah that was the day I stopped caring for C++, stopped licking intel’s ass, and started getting ever so slightly radicalized due to the lies of the republic.

      • JGrffn@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        If data structures weren’t working with MSVC, you’re probably working with non-portable code in the first place. Don’t assume an int is 32 bits long!

        Oh absolutely! I was starting out during this time, and started using memcpy for a uni project, hardcoding byte sizes to what I assumed long’s size was, instead of checking or using standardized data types (because I didn’t even know they existed). The result was such a mess, exacerbated by the good ol “let’s write it all in one go and run it when we’re done”. Boy did I suffer in that class.