Question

C++, Fortran, COBOL, etc. use:
a) Assemblers b) Compilers
c) Interpreters d) Applications

Answer 1

C++, Fortran, COBOL, etc. use:

Ans. d) Applications
Hope This Helps
........... . .... . ..

Answer 2

Answer:

And is C: Applications

Explanation:

FORTRAN or COBOL are clearly 3 Generation Languages while C++, C#, Java and many more implementing OO concepts are 4 Generation languages.

The major fact why Fortrans and Cobol fall out is:

they are not object oriented OO.

C, BTW, is also not OO but C++ is. But C has other strengths COBOL and FORTRAN do not have.

Why is OO so important? because it helps most to master complexity which adds a lot to robustness and other QA factors. And once you understand one single OO priciple, that a larger component is made of smaller componets, you got it; like a tree. The rest, more complex things, like inheritance, interfaces, polymorphism, etc. … comes much later.

An example: Look at a truck and define its subcomponents? Then develope each subcomponent by writing a class. Finally you write your truck class and reference the subcomponents from there.

Develope a class for a weel, a frame, a motor, wind screen wippers, lights, blinker, breaks, etc. … and finally the truck. what ever you need to espress for your abstract truck type goes into the truck class. The truck class is like a blue print. Its the only class your application needs to instanciate into an object.

During this instanciating cycle, all subcomponents referenced by the truck class are instanciated and initialized as well. So all you need to do after your truck class is finished, develope a main() and inside the main do like

Truck mytruck = new Truck();

Boolean running = mytruck.run;

…

and a need to change an attribute of your motor, well you find the place to do that in seconds. its in the mo

Then as your truck project gets more and more complex, you may have the desire to visualize what you developed because a picture tells you more then a 1000 words. So you shop for a CASE tool which allows for roundtrip engineering. You suck up your project directory and, wauu, you have all classes in a class diagramm. You can then continue and add more classes and modell them using your CASE tool. Once you are fnished you GENERATE your code and you add the fine programming stuff from withing your favorite IDE. Gradually you many go on and add sequence diagrams. Class interaction diagrams, You migth have a desire to trace components from your requirement engineering cycle to the test cycle. And you may well generate your documentation by a click, given you have added text at the proper place in your UML diagrams. Using this approach, you are high class and state of the art.

HOPE IT HELPS

PLEASE MARK AS THE BRAINLIEST