comments get converted to whitespace after the compiler goes to work.
in this problem the source file shouldnt contain any whitespace when viewd with an editor .thats how the question should be interpreted.
thats it .
oh and by the way,white space characters are defined as blanks (spaces), horizontal and vertical tabs, newlines, carriage returns and formfeeds ONLY
Last edited by abhi_86; 04-03-2007 at 07:04 AM.
wrong. comments get converted to whitespace by the preprocessor. as the name suggests that runs before the compiler.Originally Posted by abhi_86
Kurt
The standard defines comments as whitespace.3. The source file is decomposed into preprocessing tokens6) and sequences of
white-space characters (including comments).Quzah.Preprocessing tokens can be separated by white space; this consists of
comments (described later), or white-space characters (space, horizontal tab, new-line,
vertical tab, and form-feed), or both.
Hope is the first step on the road to disappointment.
well ok. has any of the C gurus come up with the answer yet ???
If they have I don't think they want you to just take it and turn it in for a grade...
For your information i am not even a student of computer science !!! Whatever i am learning is out Of pure interest.
And if i was really looking for answers to an assignment i would have asked for the solutions from my seniors
You can compress this
toCode:typedef/**/struct/**/{unsigned/**/*aku;char/**/*soku;}zan;
Code:typedef/**/struct{unsigned*aku;char*soku;}zan;I don't think your code solves that at all. First of all, it doesn't mention a typedef anywhere [edit] (which is kind of ironic given the title of this thread) [/edit], so you could usecreate snippet of C code that consists of two declarations defining a type called "zan", which should be a struct containing two members: first an unsigned int called "aku", then a constant pointer to char called "soku".
Secondly, soku is supposed to be a constant pointer to char. Thirdly, your code doesn't define a type called "zan", it defines an anonymous type and creates an instance of it called zan. Recall that you can name a struct like so:Code:struct{unsigned*aku;char*soku;}zan;
I personally think that assignments (or whatever) like this are stupid. Who would want to do that in reality?Code:struct name_t { };
dwk
Seek and ye shall find. quaere et invenies.
"Simplicity does not precede complexity, but follows it." -- Alan Perlis
"Testing can only prove the presence of bugs, not their absence." -- Edsger Dijkstra
"The only real mistake is the one from which we learn nothing." -- John Powell
Other boards: DaniWeb, TPS
Unofficial Wiki FAQ: cpwiki.sf.net
My website: http://dwks.theprogrammingsite.com/
Projects: codeform, xuni, atlantis, nort, etc.
Sorry, I didn't mean to offend you. But if you think about it, showing up and asking for the solution after saying that you don't want to put any time into research *and* being snippy about it doesn't encourage people to help you.
well i have put enough research into it. but still no progress.
so has andbody found out the answer ????
Why don't you think about the "answer"...
looks like damn tricky useless college question or assignment or whatever it's.
I wouldn't say useless. It's probably meant to shed light on the manner in which the compiler tokenizes its input. A rather obscure way of imparting that knowledge, but it wouldn't be the worst I've seen.
I shall end this useless discussion by quoting the important passage from K&R:
Blanks, horizontal and vertical tabs, newlines, formfeeds and comments as
described below (collectively, ``white space'') are ignored except as they separate tokens.
Some white space is required to separate otherwise adjacent identifiers, keywords, and
constants. If the input stream has been separated into tokens up to a given character, the next token is the
longest string of characters that could constitute a token.
