Why C/C++ is still alive From last 40 years ?

Short Brief

C is a general-purpose programming language developed in Bell Labs by Dennis Ritchie. After it, C++ is born in 1979 by Bjarne Stroustrup as an extension of C containing Classes. Since 1972 until now they have had some release versions. For example, the last release of C is C18 and C++20 for CPlusPlus. Who would think that they continue as an important programming language about 4 decades? Perhaps no one.

Some reasons

Nowadays, almost all programmer learn C or C++ as a fundamental skill. There are some reasons describing why they are still alive. I want to show some of the reasons here.
Compilers
All top corporation compiler like Microsoft, Intel, IBM and others like GCC, LLVM Clang support C and C++. Supporting C & CPlusPlus helps communities and programmers to develop their product confidently by them. Because of this, they remain as an important language although new programming languages bring new facilities to us.
Speed & Footprint
According to some test results, C and C++ are between 3 top high-performance languages.
Firmware
All Embedded engineers ought to develop their firmware based on C/C++. Because all compile of embedded systems designed based on Microprocessor just support C/C++. So you must know these languages.
Embedded OS
To develop an embedded system the number one choice of every programmer is C or C++. Because there are some acceptable Embedded-OS and RTOS based on them. For example, eCos, RTLinux, QNX, VxWorks, AUTOSAR, MicroC/OS are some of Top Embedded OS.
Libraries
Since when C and C++ are born, there are a large number of libraries developing for various usages by corporation and individuals. Most of these libraries are Open-Source used by every person that needs.
Developing OS
Windows, Linux, Unix are developed based on C and C++.
DataBase
Most popular DB like MySQL, MSSQL, Oracle, etc are based on C/C++.

As a mother language

The C and CPlusPlus are very useful and powerful, so no one can ignore them. I can say that: "these two languages are irreplaceable". We can anticipate that they will be used for decades.

Comments

Post a Comment

Popular posts from this blog

Getting backtrace during stack corruption

As we know , if program crashes and if it results in stack corruption, GDB will never give backtrace of the crashes.Even coredump does not help. Consider the below situation of stack corruption, Is it possible to make out anything useful from this for debugging?No Program received signal SIGSEGV , Segmentation fault . 0x00000002 in ?? () ( gdb ) bt #0 0x00000002 in ?? () #1 0x00000001 in ?? () #2 0xbffff284 in ?? () Backtrace stopped : previous frame inner to this frame ( corrupt stack ?) ( gdb ) Those bogus adresses (0x00000002 and the like) are actually PC values, not SP values. Now, when you get this kind of SEGV, with a bogus (very small) PC address, 99% of the time it's due to calling through a bogus function pointer. Note that virtual calls in C++ are implemented via function pointers, so any problem with a virtual call can manifest in the same way. An indirect call instruction just pushes the PC after the call onto the stack and then sets the PC
Read more

Analyzing Crash dumps in Linux using GDB

GDB is a common tool for debugging applications in Linux development environment. Before generating the core dump use -g compiler option for compiling the application for enabling debugging symbols. 1. set ulimit -c unlimited  in cmd to enable core dump. 2. Then run the application, after application crashes it generates code dump with core.pid file name. 3. Load the application in gdb ex: gdb <path to application> 4. In this step load the core dump by using core-file <path to core dump> command 5.Just use bt for getting the backtrace of the crash which will give you exact location where app has crashed. Use GDB instead of logging which will save your time for debugging !!!!
Read more

.b4s playlist parser WINAMP XML PlaylistFormat

More info on this file format is at http://filext.com/file-extension/B4S This can be parsed using following xml based parser application. /* .b4s parser Application */ /*Author:chandrashekar bs*/ /*email:buggs.cancerion@gmail.com/chandragoan@gmail.com*/ /* I have not added <> for including files because of in google blogs since <> are interprested as htnl syntaxes and content within thos are not appeared*/ #include iostream #include string.h #include libxml/parser.h #include libxml/xinclude.h #include libxml/tree.h #include libxml/xmlIO.h int main(int argc, char **argv) {     xmlDocPtr doc;     xmlNodePtr nodePtr;     xmlNodePtr rootnodePtr;     xmlChar *xmlbuff;     int loopcount1, loopcount2, loopcount3, loopcount4;         loopcount1=loopcount2=loopcount3=loopcount4=0;     if(argc !=2)     {         printf("Usage %s: Enter valid b4s playlist file",argv[1]);     }     char *filename = (char *)argv[1];     doc = xmlParseFile((c
Read more