In gcc, the 'int' in main function is optional and 'return 0' is also optional...that leaves a warning but gets complied and gives output.But in one of my prg it doesnt give out put but gives error i wanna know why..So what is the condition on which we are supposed to return the value 0 to main()...
Always.
read FAQ Why int main()
ssharish2005
So let me get this straight...
You're worried that your code is too long, so you think that removing "return 0;" is going to save the day?
That must be some good weed you've got.
Quzah.
Hope is the first step on the road to disappointment.
Sometimes, return 0; is the only bug-free line of code in the whole program
Why would you want to eliminate a free line which prevents your code from being a TOTAL failure
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
lol, hey its 1 line lessOriginally Posted by quzah
As someone else pointed out in a tag line.
- Every program has at least one bug.
- For any given program, it is possible to rewrite it in one less line.
- Therefore, it is possible to reduce every program to a single line, which doesn't work.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Start by deleting whitespace. This is what really makes the code unnecessarily long.
Keep all names short - preferably one character long. (Bonus: it will become almost impossible to make typographical errors too!)
Put as much as you can on one line. Using up a whole line just to do c++; is such a waste.
There may be other suggestions, but if you start out like that you'll quickly discover that you are writing nice short and efficient code.
Macros really help too. Not only for readability but sometimes they run faster because there's less code in your functions. You can also do common things like #define i if to shorten the built-in operators of the language.
I seriously don't see why you'd want to reduce the length of code...
You may want to do it more efficiently. But other than that, I see no reason to make it shorter, other then if you're concerned about readability, which shouldn't be a problem if you comment/document/make appropriate headers, it shouldn't matter how long it is. And taking out white space and lengthy variable names also would just reduce readability, therefore conflicting with what you're trying to do in the first place.
I like the macros idea, though. Macros are your friend.
Teacher: "You connect with Internet Explorer, but what is your browser? You know, Yahoo, Webcrawler...?" It's great to see the educational system moving in the right direction
Please tell me you are not serious. This is really bad advice.
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
Less lines != faster/more efficient
That is a old moronic way of thinking.
Better algorithms, profiling, tweaks here at bottle necks. That will make your code better.
anon is probably just trolling. Ironically, Mir does this a lot too and can't seem to identify other troll posts.
It does in HTML.
But that is a special case.
System: Debian Sid and FreeBSD 7.0. Both with GCC 4.3.
Useful resources:
comp.lang.c FAQ | C++ FQA Lite
Macros don't reduce the number of actual lines. They provide text subsitution. So when it's compiled, it's not going to really save you any space. It may make your source file smaller, but it's not generally going to be a space saver.
Quzah.
Hope is the first step on the road to disappointment.
