#Turbo borland c code#
In Debug mode, there are symbolic information placed into the executable file.īy the way, the size of the executable may not be the size of the executable code placed in memory. Most likely because you are compiling in Debug mode or because Turbo C++ is a simpler compiler, it doesn't optimize the libraries and code as much as Borland does. Research the difference between ".com" and ".exe" formats. It also depends on whether you compiled for static libraries or dynamic libraries.įundamentally, the Borland Compiler may be generating code that meets the standards required by later versions of Windows than Turbo C++ was required to support. This also depends on whether you compiled in Debug mode or in Release mode. You'll have to either look at the assembly code generated, machine code generated or post to the Borland forums. Your program doesn't require any header files. You don't use them, so there is no additional code generated. You can include all the header files you want. (The main function returns an int, always.) Your program has no functionality and is incorrect. I will do my best at answering these, but you may need to post your questions to the Borland forums for detailed answers. Sorry about this long question but if you can clarify this to me that would be awesome i'm so confused right now. Now i have these question i'd like you to answerġ-Why Borland C++ compiled files are the same when one of them clearly dosen't have some include and another have?Ģ-Why Boland C++ compiled files are that big? (nearly 10 times bigger) and what is compiled that have that much size?ģ-When i submit First Code to this Site i can see the assembly code of simple void main function and i realized that Borland C++ code is very much the same but Turbo C++ assembly code is very very complicated and isn't the same, why?Ĥ-Why this simple Code that compiled with Turbo C++ create this much functions that you can see in it's graph?
![turbo borland c turbo borland c](https://getintopc.com/wp-content/uploads/2014/02/c++-pic.png)
#Turbo borland c pro#
I examined the First Code form these compilers in IDA pro and come across these graphs :
![turbo borland c turbo borland c](https://www.solvusoft.com/file-extensions/images/software/large/2554_borland-turbo-debugger.png)
I checked two Borland execute files with a hex viewer and realize they are exactly the same. I compiled two code using Turbo C++ 3.0 and Borland C++ 5.02 compilers and come across some odd things my cods are like these :