The languages are not case sensitive in most implementations. However, Fortran versions from F77 forward allow the use of lower-case letters in statements; the compiler simply translates them all to upper-case before processing.
Case sensitivity is a contentious item among programmers. Typing in mixed, INsensitive case is a lot more readable, but programming with case sensitivity can be a recipe for disaster. For example, it's a lot easier to read a name called SetOutputStage than SETOUTPUTSTAGE or setoutputstage. But if the compiler is case sensitive, all it takes is one fumblefingered letter to create 2 variables - e.g. SetOutputStage and SetOutputstage, which are virtually indistinguishable to the eye!
The real-world is case-sensitive and it would actually take more effort to remove case-sensitivity. Keyboards treat the characters 'A' and 'a' as being separate entities with different character codes, it's only humans that treat them as being different cases of the same letter. In order for a computer to treat them as being the same letter, it must convert all characters to the same case (whether upper or lower case) and that alone takes far more effort than simply treating them as being the completely separate characters they actually are. C is a high-performance language, so it makes no sense to waste time converting characters unnecessarily.
The case-sensitivity (or lack thereof) of any programming language typically stems from the systems upon which the language was originally intended, or from the languages upon which they were derived. C has its roots in UNIX which is an inherently case-sensitive system. That is, README.TXT and readme.txt are distinct file identifiers that may co-exist within the same folder. It only makes sense for C to treat identifiers in exactly the same way. After all, the fewer inconsistencies we introduce into a system, the easier that system is to use.
You might ask why UNIX is case-sensitive, but the answer is simple. While the Latin alphabet has 26 distinct characters with two representations each (uppercase and lowercase), implementing a case-insensitive system in English is trivial. However, most people prefer to use identifiers in their own native language but not all languages lend themselves to a case-insensitive system quite so readily. For instance, the German eszett "ß" has no uppercase equivalent while certain Arabic scripts have certain letters with three representations rather than two. Case-sensitivity caters for all languages equally.
FORTRAN is a third generation language.Note: I don't know what these generations are, but I'm quite sure that Fortran is one of the oldest high-level programming languages, as are Cobol and Algol.
COBOL, FORTRAN, BASIC, C and C++.
fortran language,basic language,cobol language.
Fortran (Foltran is a misspelling)
The Fortran and COBOL programming languages have both been around for a long time. Fortran was released around 1957, while COBOL followed a couple years later. Fortran has historically been mostly used for numerical and scientific calculations, while COBOL is primarily used by businesses.
From oldest to newest: FORTRAN, COBOL, BASIC, and C++
fortran, algol, cobol, pl/i, for example
Examples: Algol, Cobol, Fortran, PL/I, Basic
Programming languages such as COBOL and FORTRAN are examples of procedure languages.
Assembly language Fortran LISP COBOL ALGOL
FORTRAN is a third generation language.Note: I don't know what these generations are, but I'm quite sure that Fortran is one of the oldest high-level programming languages, as are Cobol and Algol.
COBOL, FORTRAN, BASIC, C and C++.
fortran language,basic language,cobol language.
Fortran (Foltran is a misspelling)
Machine Code, Assembler, & High Level (FORTRAN, COBOL, C).
Fortran and Cobol are two old and successful languages.
COBOL stands for Common Business Oriented Language and, as the name implies, is best applied in business and accounting type projects. FORTRAN is primarily for scientific/engineering/mathematical problems. The name comes from 'Formula Translator.' The FORTRAN that I worked with some 50 yrs ago in no way resembles the FORTRAN of today ... it evolves I've been told that 500 yrs from now, engineers will still be using something called FORTRAN though it had evolved even more through time.