object & executable file

[techgroups.bk]

can you tell about what is the object file and executable
file. give difference between these files.

 

[Ian Collins]

can you tell about what is the object file and executable
file. give difference between these files.

What has your book or Mr. Google told you?

 

[osmium]

can you tell about what is the object file and executable
file. give difference between these files.

This might help. This was posted years ago by one of the best ever
contributors to any of the C associated groups, Karl Heinz Buchegger. He
lived in Austria, and from the name I would guess he actually was an
Austrian, but he wrote better English than the vast majority of Americans.
Sadly, one day he just disappeared; it was a great loss.
..
http://groups.google.com/group/comp.lang.c++/browse_thread/thread/55f635de1fe30fd3?hl=en&q=100-dreds

 

[Antoninus Twink]

http://groups.google.com/group/comp.lang.c++/browse_thread/thread/55f635de1fe30fd3?hl=en&q=100-dreds

Nice resource!

A couple of points for the OP:

1) To get a broad overview of an unfamiliar topic, it's generally better
to read an article on Wikipedia or elsewhere on the web (or even in a
book - avoid "C unleashed", though), and then use these newsgroups for
specific questions about points you don't understand.

2) I notice that some of the more unpleasant posters to clc ("Ian
Collins", "CBFacloner", etc.) have already given your posts a hostile
reception. They have their own agenda and want to disrupt the smooth
running of this newsgroup. It's best just to ignore them - they won't
give you any help here anyway, so it's not as if you're losing anything.

 

[jfbode1029]

           can you tell about what is the object file and executable
file. give difference between these files.

This really isn't a C question; you would be better served going to a
resource like Wikipedia or About.com.

In an overly simplistic nutshell:

Object files are binary files containing the machine code translation
of your source code. They are not (typically) executable on their own
since they may be incomplete (e.g., they won't have the machine code
for any library routines like printf() or malloc() or anything like
that) and may not be formatted or marked as executable.

Executable files are, well, executable. Depending on how tightly you
want to define "executable", they can be binary files generated from
linking object files together, or they can be shell scripts or other
interpreted files. Executable binary files are often organized in a
specific format, and may contain some leading magic bits that identify
them as exectable.

Obviously, details will vary by system, development environment, and
language.

 

[Guest]

Nice resource!

A couple of points for the OP:

1) To get a broad overview of an unfamiliar topic, it's generally better
to read an article on Wikipedia or elsewhere on the web (or even in a
book - avoid "C unleashed", though), and then use these newsgroups for
specific questions about points you don't understand.

Twink is mostly right here, but his remark about "Unleashed" is simple
a display prejudice. The book is fine and well worth a read. I don't
believe it specifically addresses the topic you are interested in and
since it is out of print it may be difficult to lay your hands on a
copy.

<snip>