Difference between revisions of "Why I should not use Turbo C?"

(Created page with "# For a beginner he will be learning wrong concepts like conio.h and clrscr must be used in all c programs # Return type of main is int but turbo c forces void # Difficulty in...")
 
Line 1: Line 1:
 
# For a beginner he will be learning wrong concepts like conio.h and clrscr must be used in all c programs
 
# For a beginner he will be learning wrong concepts like conio.h and clrscr must be used in all c programs
−
# Return type of main is int but turbo c forces void
+
# Return type of main is int but Turbo C forces void
−
# Difficulty in coding- turbo c forces all declarations before any function call while Standard c compilers allows declaration anywhere.  
+
# Difficulty in coding- Turbo C forces all declarations before any function call while Standard C compilers allows declaration anywhere.  
 
# int a [10][1000] is not possible in Turbo C while modern compilers allow at least 100 times this size.  
 
# int a [10][1000] is not possible in Turbo C while modern compilers allow at least 100 times this size.  
 
# Far, huge pointers- another not needed concepts
 
# Far, huge pointers- another not needed concepts
−
# C is for system programming, turbo c won't teach you any system as DOS is no longer in use.
+
# C is for system programming, Turbo c won't teach you any system as DOS is no longer in use
−
# "I code in Turbo C" is enough to get the exit ticket from any good company interview.
+
# "I code in Turbo C" is enough to get the exit ticket from any good company interview
−
#A C compiler is supposed to translate a C code to machine code. But the code generated by Turbo C is not for any current machines. It is meant only for DOS (just because DOS emulator is there it works in Windows, but not useful for making any application outside DOS)
+
# I'm lazy- I don't want to write conio.h, clrscr and getch for every C code when it is absolutely not necessary to type them in any standard C compiler
 +
#A C compiler is supposed to translate a C code to machine code. But the code generated by Turbo C is not meant for any current machine (architecture). It is meant only for DOS (just because DOS emulator is there it works in Windows, but not useful for making any application outside DOS). Use the appropriate compiler for your machine and choose others when you can't find one. In most architecture you can get gcc which is the most widely used compiler and is also opensource.
 +
 
 +
 
 +
==Best option for Programming==
 +
on 64 bit machines
 +
 
 +
[http://releases.ubuntu.com/14.04/ubuntu-14.04.1-desktop-amd64.iso Ubuntu 14.04]
 +
 
 +
for other architectures you can see here
 +
 
 +
[http://releases.ubuntu.com/14.04/]
 +
 
 +
==For those who wants to continue use windows (I don't know why?)==
 +
[ http://sourceforge.net/projects/codeblocks/files/Binaries/13.12/Windows/codeblocks-13.12mingw-setup.exe | Codeblocks with gcc for Windows]
 +
 
 +
{{Template:FBD}}

Revision as of 18:39, 20 August 2014

  1. For a beginner he will be learning wrong concepts like conio.h and clrscr must be used in all c programs
  2. Return type of main is int but Turbo C forces void
  3. Difficulty in coding- Turbo C forces all declarations before any function call while Standard C compilers allows declaration anywhere.
  4. int a [10][1000] is not possible in Turbo C while modern compilers allow at least 100 times this size.
  5. Far, huge pointers- another not needed concepts
  6. C is for system programming, Turbo c won't teach you any system as DOS is no longer in use
  7. "I code in Turbo C" is enough to get the exit ticket from any good company interview
  8. I'm lazy- I don't want to write conio.h, clrscr and getch for every C code when it is absolutely not necessary to type them in any standard C compiler
  9. A C compiler is supposed to translate a C code to machine code. But the code generated by Turbo C is not meant for any current machine (architecture). It is meant only for DOS (just because DOS emulator is there it works in Windows, but not useful for making any application outside DOS). Use the appropriate compiler for your machine and choose others when you can't find one. In most architecture you can get gcc which is the most widely used compiler and is also opensource.


Best option for Programming

on 64 bit machines

Ubuntu 14.04

for other architectures you can see here

[1]

For those who wants to continue use windows (I don't know why?)

[ http://sourceforge.net/projects/codeblocks/files/Binaries/13.12/Windows/codeblocks-13.12mingw-setup.exe | Codeblocks with gcc for Windows]




blog comments powered by Disqus
Retrieved from "https://gatecse.in/w/index.php?title=Why_I_should_not_use_Turbo_C%3F&oldid=4179"
  1. For a beginner he will be learning wrong concepts like conio.h and clrscr must be used in all c programs
  2. Return type of main is int but turbo c forces void
  3. Difficulty in coding- turbo c forces all declarations before any function call while Standard c compilers allows declaration anywhere.
  4. int a [10][1000] is not possible in Turbo C while modern compilers allow at least 100 times this size.
  5. Far, huge pointers- another not needed concepts
  6. C is for system programming, turbo c won't teach you any system as DOS is no longer in use.
  7. "I code in Turbo C" is enough to get the exit ticket from any good company interview.
  8. A C compiler is supposed to translate a C code to machine code. But the code generated by Turbo C is not for any current machines. It is meant only for DOS (just because DOS emulator is there it works in Windows, but not useful for making any application outside DOS)