M
Malcolm
That's inevitable. The convoy travels at the speed of the slowest ship.jacob navia said:Richard Heathfield a écrit :
"Portability" for you means "taking the worst features of each
implementation".
That's inevitable. The convoy travels at the speed of the slowest ship.jacob navia said:Richard Heathfield a écrit :
"Portability" for you means "taking the worst features of each
implementation".
Implicit int was a fossil and it's time it went.
However prototypes are just a nuisance. There's some case for them in a
header file, where they describe the interface to the file, but the only
reason for them in other places is to allow the compiler to check arguments
on one pass. A modern compiler should be intelligent enough to do this
without a prototype to help it along.
Not to mention the fact that maintenance programmers want a prototypeMalcolm a écrit :
Please think a bit Malcom.
To know the argument for a function without prototypes the compiler
should have the source code for all functions, including those in the
libraries the program is using. This would imply that the source code
for all the system would have to be processed, loaded into memory,
before any checks could be done.
This is completely impossible, so *some* type of prototype declaration
is needed. In Pascal you have the 'interface' declarations, in C# you
have a similar construct... etc!
The library should contain information about the signature of the functionsjacob navia said:Malcolm a écrit :
Please think a bit Malcom.
To know the argument for a function without prototypes the compiler should
have the source code for all functions, including those in the libraries
the program is using. This would imply that the source code for all the
system would have to be processed, loaded into memory, before any checks
could be done.
This is completely impossible, so *some* type of prototype declaration is
needed. In Pascal you have the 'interface' declarations, in C# you have a
similar construct... etc!
Think of the attribution lines as prototypes.Richard Heathfield said:Malcolm said:
No, Richard Heathfield didn't write any of the stuff quoted in your
article.
Richard said:Malcolm said:
No, Richard Heathfield didn't write any of the stuff quoted in your
article.
You going to sue him?
Malcolm said:
No, Richard Heathfield didn't write any of the stuff quoted in your article.
Gordon said:This is a perfect example of why attribution = misattribution,
and I didn't have anything to do with prior articles in this thread.
Also, this is off-topic for comp.lang.c. Is there a alt.flame.attributions?
Gordon said:This is a perfect example of why attribution = misattribution,
and I didn't have anything to do with prior articles in this thread.
This is a perfect example of why attribution = misattribution,
and I didn't have anything to do with prior articles in this thread.
This is a perfect example of why attribution = misattribution,
and I didn't have anything to do with prior articles in this thread.
Keith said:.... snip ...
You, on the other hand, repeatedly, consistently, and *deliberately*
make the far worse mistake of snipping all attributions, making
discussions more difficult to follow for everyone. I don't quite
agree with CBFalconer's statement in another thread that this is
plagiarism, but it is extremely rude.
This is a perfect example of why attribution = misattribution,
CBFalconer said:I said it "was tantamount to plagiarism". Several nits there.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.