Guest

Advertisements

writes:
> Can any one explain me the life cycle of C from source code to process
> termination.

Edit, compile, link, run.

If that's not enough information, you'll have to ask a clearer question.
> please make it fast

If English isn't your first language, you might not be aware that that
sounds a bit arrogant, as if you were giving orders to underlings.
You're asking us for help, which we give freely and voluntarily. The
best way to get help is to ask clear (and interesting) questions, and
to respond quickly to requests for clarification. Telling us that
your question is urgent will not get you a response any more quickly;
in fact, some people will be less inclined to help you at all.

If your question really is urgent, you should explain why -- but don't
expect a lot of sympathy. Your urgency does not create a sense of
obligation for anyone else.

And just in case you haven't read it already, I urge you to read
<http://cfaj.freeshell.org/google/> before posting a followup.

--
Keith Thompson (The_Other_Keith) <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

Advertisements

write:
>Can any one explain me the life cycle of C from source code to process
>termination.
I think you should read the textbook.
>please make it fast
....and learn to be polite, too.Please learn it fast...

wrote:
>
> Can any one explain me the life cycle of C from source code to
> process termination.
>
> please make it fast

Yassuh. Edit, compile, run.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

??? wrote:
> write:
>
>> Can any one explain me the life cycle of C from source code to
>> process termination.
>
> I think you should read the textbook.
>
>> please make it fast
>
> ...and learn to be polite, too.Please learn it fast...

The word is quickly. You make boats fast to docks, or you fast to
lose weight, or for religious reasons.

--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>

In article <>,
CBFalconer <> wrote:
>??? wrote:
>> ...and learn to be polite, too.Please learn it fast...
>The word is quickly. You make boats fast to docks, or you fast to
>lose weight, or for religious reasons.

<OT>
Summarizing from OED:

There are four major noun forms of 'fast' (e.g., absetinence from
food), and two major verb forms, but none of those are relevant to this
discussion because in "learn it fast", fast cannot grammatically be a
noun or verb.

fast as an adverb has very similar senses to the adjective form.
Sense specifically listed include "Quickly, rapidly, swiftly";
"in quick succession; one close upon another"; "readily, with alacrity".
As the sentance being nitted was describing a second action,
the "quick succession" sense is not ruled out, and the "with alacrity"
meaning applies as well, in addition to the "quickly, rapidly, swiftly"
meanings.

If the phrase had been "make it fast" then adjective or adverb could
both have been possibilities, but for "learn it fast", adverb is
the only real choice: "make" is a verb of intentional creation
of state and an adjective can describe a state (e.g., "make it round"),
but for "learn" an auxillary denoting mode (that is, an adverb) makes
more sense -- and... OED clearly shows "quickly" as one of the
adverbal meanings.

I would certainly agree that "quickly" would likely be a better
word than "fast" for the -probable- meaning, but "quickly" is within
the adverbal meaning, and for those other two senses I noted above, "fast"
is the appropriate word.

In summary, your nit is wrong in implying that "fast" was definitely
being used incorrectly.
</OT>
--
Programming is what happens while you're busy making other plans.

Guest

sorry i should really be polite while asking questions
but in a hurry i wrote something without thinking
im sorry once again

and thanks a lot for ur response
a person who tells our mistakes is our real friend rather than a
person who
ignores it( i feel) thanku once again

Actually i was asked to give a seminar on the following question
life cycle of C from source code to process termination.

even i know the answer in one line as u said
edit,compile,link,run
i dint understood what to tell them?
can u tell me what should i explain them?
and when do the process terminate? will it terminate immediately after
running?

ok bye
i will feel happy if u reply me
take care
-ramya

Keith Thompson wrote:
> writes:
> > Can any one explain me the life cycle of C from source code to process
> > termination.
>
> Edit, compile, link, run.
>
> If that's not enough information, you'll have to ask a clearer question.
>
> > please make it fast
>
> If English isn't your first language, you might not be aware that that
> sounds a bit arrogant, as if you were giving orders to underlings.
> You're asking us for help, which we give freely and voluntarily. The
> best way to get help is to ask clear (and interesting) questions, and
> to respond quickly to requests for clarification. Telling us that
> your question is urgent will not get you a response any more quickly;
> in fact, some people will be less inclined to help you at all.
>
> If your question really is urgent, you should explain why -- but don't
> expect a lot of sympathy. Your urgency does not create a sense of
> obligation for anyone else.
>
> And just in case you haven't read it already, I urge you to read
> <http://cfaj.freeshell.org/google/> before posting a followup.
>
> --
> Keith Thompson (The_Other_Keith) <http://www.ghoti.net/~kst>
> San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
> We must do something. This is something. Therefore, we must do this.

writes:
> hi keith thompson
>
> sorry i should really be polite while asking questions
> but in a hurry i wrote something without thinking
> im sorry once again

We get a lot of people here who are unapologetically rude. I'm very
happy to see you're not one of them.

In that spirit, a few posting tips:

Use standard capitalization ("I" and the first letter of each
sentence), spelling, and punctuation. Avoid abbreviations like "u"
for "you", "ur" for "your", and so forth; they merely make what you
write more difficult to read, especially for people whose first
language isn't English. Typos and minor spelling and grammatical
errors are usually ignored; certain kinds of silly abbreviations are
not.

Also, please don't top-post. See <http://www.caliburn.nl/topposting.html>
for more information.

[...]
> Actually i was asked to give a seminar on the following question
> life cycle of C from source code to process termination.
>
> even i know the answer in one line as u said
> edit,compile,link,run
> i dint understood what to tell them?
> can u tell me what should i explain them?
> and when do the process terminate? will it terminate immediately after
> running?

I'm not sure there's much I can add to what's already been said. The
details of how programs are compiled and executed can vary from one
implementation to another. The language doesn't even define the
concept of a "process".

The standard does define 8 "translation phases" (see C99 5.1.1.2;
google n1124.pdf to see the most recent draft), but compilers are
merely required to operate *as if* they work in separate phases. The
standard says even less about how programs are executed.

--
Keith Thompson (The_Other_Keith) <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

CBFalconer wrote:
> ??? wrote:
>
>> write:
>>
>>
>>>Can any one explain me the life cycle of C from source code to
>>>process termination.
>>
>>I think you should read the textbook.
>>
>>
>>>please make it fast
>>
>>...and learn to be polite, too.Please learn it fast...
>
>
> The word is quickly. You make boats fast to docks, or you fast to
> lose weight, or for religious reasons.
>

Unnecessary comment I think. English is not everyone's (myself included)
native tongue around here, you know.

August

--
I am the "ILOVEGNU" signature virus. Just copy me to your
signature. This email was infected under the terms of the GNU
General Public License.

wrote:
> Actually i was asked to give a seminar on the following question
> life cycle of C from source code to process termination.
>
> even i know the answer in one line as u said
> edit,compile,link,run
> i dint understood what to tell them?
> can u tell me what should i explain them?

I'd be tempted to go back to the person who asked you to do the
seminar and ask them what they expected you to cover.

"edit,compile,link,run"

is going to make for a very short seminar!
> and when do the process terminate? will it terminate immediately after
> running?

depend on the OS, but generally yes. When you return from main() or
call
exit() etc. You end up in platform specific code which will generally
terminate
the process and return a value to the caller (parent).

Share This Page

Welcome to The Coding Forums!

Welcome to the Coding Forums, the place to chat about anything related to programming and coding languages.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to ask questions about coding or chat with the community and help others.
Sign up now!