should i use stl or hard code?
Hello!
I am planning on making a project that is going to be sort of embedded systems.
the system will have 2gb of ram and 4gb of flash memory and a 1ghz processor.
now why i call it sort of embedded systems is because there is a lot more resources available than on the smaller i'cs.
the questions are:
-should i use the containers provided in stl such as map, list and vector or code these pars myself in C only with the functionality i need for portability?
-is it even a good idea to stick with c++ (not using object oriented programming) when resources are not that limited or just go full c?
I am planning on making a project that is going to be sort of embedded systems.
the system will have 2gb of ram and 4gb of flash memory and a 1ghz processor.
now why i call it sort of embedded systems is because there is a lot more resources available than on the smaller i'cs.
the questions are:
-should i use the containers provided in stl such as map, list and vector or code these pars myself in C only with the functionality i need for portability?
-is it even a good idea to stick with c++ (not using object oriented programming) when resources are not that limited or just go full c?
unless you are down to the wire on resources, use the STL. If you run it out of memory or cpu, then you can find whatever is behind the issue and recode it if needed.
C++ can do anything C can, but C can't do much of what C++ can. There is no compelling reason to use C if your platform supports c++.
Its all relative but that is indeed an embedded system... modern PCs have more than 10x the ram and orders of magnitude more processor.
C++ can do anything C can, but C can't do much of what C++ can. There is no compelling reason to use C if your platform supports c++.
Its all relative but that is indeed an embedded system... modern PCs have more than 10x the ram and orders of magnitude more processor.
Topic archived. No new replies allowed.