Does anyone know of a good resource for learning about .BIN files, what they do, how to use them and make them, etc.? Note that I'm talking about the files you might find in the "bin" folder of your compiler's files.
Does anyone know of a good resource for learning about .BIN files, what they do, how to use them and make them, etc.? Note that I'm talking about the files you might find in the "bin" folder of your compiler's files.
Last edited by Jaken Veina; 05-26-2005 at 10:00 AM.
they're whatever you make of them really. ".BIN" usually means it's just data in binary format. The tutorials around here have information on how to open files and deal with the data inside. You might also find DLL's in the bin folder, which I believe you can also find in the tutorials.
Last edited by skorman00; 05-26-2005 at 07:43 PM.
Well....I don't know. Maybe I didn't ask the right question. What I'd kinda like to know is what a .bin file (or any file in the /bin folder) does for the compiler. How does the compiler use it?
/bin is a common place to store programs - usually without a .bin extension. If it has a .bin extension it's probably just binary data tagged to tell you not to treat it as text. Any file can really be any format - text, binary, or something more specific. If you can't read hexidecimal you aren't going to get much of anywhere, and if it's binary numeric data, you need to know what kind of computer it was written on (x86 machines store binary numbers byte by byte low order first, and many others store high order first). .exe files are MS binary programs in a specific format which is different from the one that Unix type systems use. A compiler will generate an object file (binary) which is linked with a starter object and probably library objects (also binary and different depending on the operating system and perhaps the compiler) to make a program. These all have well defined formats, but there are many different ones. The compiler and linker are programs which may well reside in a /bin directory, and in Unix/linux, you may also find shell scripts (text) there as well just because they are executable. For more info, ask more specific questions.
Last edited by Karthur; 05-27-2005 at 06:47 PM.
7. It is easier to write an incorrect program than understand a correct one.
40. There are two ways to write error-free programs; only the third one works.*
