0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 7 months agoSupreme leader madsh.itjust.worksimagemessage-square103fedilinkarrow-up1763arrow-down133
arrow-up1730arrow-down1imageSupreme leader madsh.itjust.works0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish · 7 months agomessage-square103fedilink
minus-squareozymandias117@lemmy.worldlinkfedilinkEnglisharrow-up11arrow-down1·7 months agoThat doesn’t really surprise me, as most of those are the same requirements from any embedded development use case using c++ that I’ve worked on 4 and 5 are the only ones stricter than I’m used to
minus-squareBartyDeCanter@lemmy.sdf.orglinkfedilinkarrow-up5·7 months agoI’ve only worked on a few embedded systems where C++ was even an option, but they allowed 2, 4, 5, and 7. Though, for the most part most classes were simple interfaces to some sort of SPI/I2C/CAN/EtherCAT device, most of which were singletons.
That doesn’t really surprise me, as most of those are the same requirements from any embedded development use case using c++ that I’ve worked on
4 and 5 are the only ones stricter than I’m used to
I’ve only worked on a few embedded systems where C++ was even an option, but they allowed 2, 4, 5, and 7. Though, for the most part most classes were simple interfaces to some sort of SPI/I2C/CAN/EtherCAT device, most of which were singletons.