What is wrong with using turbo C?

by

Turbo C is a DOS only product. This means that it no longer runs “natively” on 64-bit versions of Windows, and must be run inside the XP compatibility penalty box.

More Related Contents:

  1. Printf width specifier to maintain precision of floating-point value
  2. Are there machines, where sizeof(char) != 1, or at least CHAR_BIT > 8?
  3. Is “inline” without “static” or “extern” ever useful in C99?
  4. Enabling VLAs (variable length arrays) in MS Visual C++?
  5. What does dot (.) mean in a struct initializer?
  6. What is the use of the `inline` keyword in C?
  7. C99 boolean data type?
  8. What is the correct type for array indexes in C?
  9. What is the difference between C, C99, ANSI C and GNU C?
  10. Realistic usage of the C99 ‘restrict’ keyword?
  11. Get warning when a variable is shadowed
  12. Flexible array member in C-structure
  13. Does Microsoft visual studio 2010 support c99?
  14. Can I omit return from main in C? [duplicate]
  15. Errors using ternary operator in c
  16. state machines tutorials [closed]
  17. What is the default C -std standard version for the current GCC (especially on Ubuntu)?
  18. Does the C standard consider that there are one or two ‘struct uperms_entry’ types in this header?
  19. How to wrap printf() into a function or macro?
  20. Why is the fgets function deprecated?
  21. How to properly add hex escapes into a string-literal?
  22. Why was mixing declarations and code forbidden up until C99?
  23. Is int main() { } (without “void”) valid and portable in ISO C?
  24. Is there any reason not to use fixed width integer types (e.g. uint8_t)?
  25. How to tell GCC that a pointer argument is always double-word-aligned?
  26. Is there a document describing how Clang handles excess floating-point precision?
  27. Dynamic array allocation on stack in C
  28. Unsigned to signed conversion in C
  29. Declaring an array of negative length
  30. Why are compound literals in C modifiable

Leave a Comment