@0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish • 1 year agoSupreme leader madsh.itjust.worksimagemessage-square102arrow-up1764
arrow-up1764imageSupreme leader madsh.itjust.works@0x4E4F@sh.itjust.works to linuxmemes@lemmy.worldEnglish • 1 year agomessage-square102
minus-square@ozymandias117@lemmy.worldlinkfedilinkEnglish11•1 year 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-square@BartyDeCanter@lemmy.sdf.orglinkfedilink5•1 year 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.