And it would be very handy...C++ maybe?
C++ maybe?
How about adding classes? It needs extra stack call but many projects would live with that And it would be very handy...
And it would be very handy...Re: C++ maybe?
C++ hardly gets used for microcontrollers because it has large overhead both in terms of memory requirements and in terms of execution time. Actually the use of C++ for embedded development has greatly decreased over the last 10 years or so after some initial hype; now C is almost completely dominant (somewhere around 70% of the projects, the rest being C++, other high-level languages, and assembler).
Wolfgang
Wolfgang
Re: C++ maybe?
Hello,
I think womai explained most of the reasons why. Our management evaluated the necessity for such development and investing so much energy into developing C++ compiler (at least for now) would really not produce as much results as it is needed. However, we are always open for suggestions and comments, and if it turns out that there are many requests for C++, we might reconsider our current position and involve into producing one.
Best regards,
Aleksandar
I think womai explained most of the reasons why. Our management evaluated the necessity for such development and investing so much energy into developing C++ compiler (at least for now) would really not produce as much results as it is needed. However, we are always open for suggestions and comments, and if it turns out that there are many requests for C++, we might reconsider our current position and involve into producing one.
Best regards,
Aleksandar
Web Department Manager
Re: C++ maybe?
I would much rather have a well supported Forth compiler.
C++ I would (and do) go out of my way to avoid.
john
C++ I would (and do) go out of my way to avoid.
john
-
Rocket
Re: C++ maybe?
Hello ...
The beauty with OOP (object orientated programming) is code re-usability, maintainability and enhanced clarity of the code.
I agree that with most MCUs, the benefits don't outweigh the limitations that would arise. The language would consume much more of the micro's memory and computing power. However, I wonder if some of these newer breeds of MCUs which boast a much larger degree of memory and computing power, could perhaps seem as suitable candidates for OOP.
If your typical programmer has around say 20% of unused program memory and computing horsepower for the taking, then it does make sense to consider OOP, at least in my mind.
Try making a decent video game without using OOP -- you'll likely do your head in with it. Fact: OOP was invented some 20 years ago to solve a rather big problem, large scale projects were failing with the use of traditional procedural-based languages. Too messy and unmaintainable basically.
Kind regards,
Leo Simpleson
The beauty with OOP (object orientated programming) is code re-usability, maintainability and enhanced clarity of the code.
I agree that with most MCUs, the benefits don't outweigh the limitations that would arise. The language would consume much more of the micro's memory and computing power. However, I wonder if some of these newer breeds of MCUs which boast a much larger degree of memory and computing power, could perhaps seem as suitable candidates for OOP.
If your typical programmer has around say 20% of unused program memory and computing horsepower for the taking, then it does make sense to consider OOP, at least in my mind.
Try making a decent video game without using OOP -- you'll likely do your head in with it. Fact: OOP was invented some 20 years ago to solve a rather big problem, large scale projects were failing with the use of traditional procedural-based languages. Too messy and unmaintainable basically.
Kind regards,
Leo Simpleson
Re: C++ maybe?
OOP is a means to an end and has little to do with the language you use.
(I first implemented OOP from Dick Pountains Forth book - I remember
reading the first articles in Byte when the concepts were being suggested -
at the time I think they were calling it "re-usable code" or "software-ICs")
C++ is a seriously poor quality language that put many large projects
(notably telecoms ones) in serous trouble.
I doubt it would be sensible to even consider C++ for embedded applications for a whole host of reasons.
Just my own view of course.
john
(I first implemented OOP from Dick Pountains Forth book - I remember
reading the first articles in Byte when the concepts were being suggested -
at the time I think they were calling it "re-usable code" or "software-ICs")
C++ is a seriously poor quality language that put many large projects
(notably telecoms ones) in serous trouble.
I doubt it would be sensible to even consider C++ for embedded applications for a whole host of reasons.
Just my own view of course.
john
