sh?tpile of errors

[Bill Cunningham]

Would anyone be interested in giving this a quick look. The compiler
gave me so many errors I don't know where to start. This is my first use of
isalpha.

#include <stdio.h>
#include <stdlib.h>
#define ex exit(EXIT_FAILURE)

int main(int argc, char *argv[])
{
if (argc != 4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2])) {
puts("name is 3rd arg");
ex;
}
double x, y;
FILE *fp;
x = strtod(argv[1], NULL);
y = strtod(argv[2], NULL);
if (fp = fopen(argv[3], "a"))
== NULL) {
puts("fopen error");
ex;
}
fprintf(argv[3], "%.2f", x, y);
if (fclose(fp))
== NULL) {
puts("fclose error");
ex;
}
return 0;
}

I dunno sigh..

Bill

[Bill Cunningham]

"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000h sk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

(Recommended options such as -Wall suppressed for clarity.)

Ok that works. Here is my compiler's errors. I have rewritten everything
and since this is non-production code I am using the ex macro to represent
exit(EXIT_FAILURE).

gcc: 2: No such file or directory
p.c: In function `main':
p.c:11: error: syntax error before '{' token
p.c: At top level:
p.c:17: error: conflicting types for 'x'
p.c:16: error: previous declaration of 'x' was here
p.c:17: error: `argv' undeclared here (not in a function)
p.c:17: error: initializer element is not constant
p.c:17: warning: data definition has no type or storage class
p.c:18: error: conflicting types for 'y'
p.c:16: error: previous declaration of 'y' was here
p.c:18: error: initializer element is not constant
p.c:18: warning: data definition has no type or storage class
p.c:19: error: syntax error before "if"
p.c:22: error: syntax error before string constant
p.c:22: error: conflicting types for 'fprintf'
p.c:22: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
p.c:22: error: conflicting types for 'fprintf'
p.c:22: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
p.c:22: warning: data definition has no type or storage class

Bill

[Bill Cunningham]

"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000h sk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");
ex;
}
FILE *fp;
double x,y;
x=strtod(argv[1],NULL);
y=strtod(argv[2],NULL);
if (fp=fopen(argv[3],"a"))==EOF) {
puts("fopen error");
}
fprintf(fp,"%.2f",x,y);
if (fclose(fp))==EOF) {
puts("fclose error");
}
return 0;
}

Bill

[Richard]

"Bill Cunningham" <no****@nspam.comwrites:

"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000h sk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

(Recommended options such as -Wall suppressed for clarity.)

Ok that works. Here is my compiler's errors. I have rewritten everything
and since this is non-production code I am using the ex macro to represent
exit(EXIT_FAILURE).

Non production code!

LOL! Stop! You're cracking me up!

Oh, and why are you posting the rubbish below?

>
gcc: 2: No such file or directory
p.c: In function `main':
p.c:11: error: syntax error before '{' token
p.c: At top level:
p.c:17: error: conflicting types for 'x'
p.c:16: error: previous declaration of 'x' was here
p.c:17: error: `argv' undeclared here (not in a function)
p.c:17: error: initializer element is not constant
p.c:17: warning: data definition has no type or storage class
p.c:18: error: conflicting types for 'y'
p.c:16: error: previous declaration of 'y' was here
p.c:18: error: initializer element is not constant
p.c:18: warning: data definition has no type or storage class
p.c:19: error: syntax error before "if"
p.c:22: error: syntax error before string constant
p.c:22: error: conflicting types for 'fprintf'
p.c:22: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
p.c:22: error: conflicting types for 'fprintf'
p.c:22: note: a parameter list with an ellipsis can't match an empty
parameter name list declaration
p.c:22: warning: data definition has no type or storage class

Bill

--

[Richard]

"Bill Cunningham" <no****@nspam.comwrites:

"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000h sk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");
ex;
}
FILE *fp;
double x,y;
x=strtod(argv[1],NULL);
y=strtod(argv[2],NULL);
if (fp=fopen(argv[3],"a"))==EOF) {
puts("fopen error");
}
fprintf(fp,"%.2f",x,y);
if (fclose(fp))==EOF) {
puts("fclose error");
}
return 0;
}

Bill

I needed a good laugh so I complied the rubbish above. It took 10
seconds to get it to compile with only warnings.

You need to improve your trolling - pretending that you dont know how to
bracket code is simply over the top.

,----
| #include <stdio.h>
| #include <stdlib.h>
| #include <ctype.h>
| #define ex exit(EXIT_FAILURE)
|
| int main (int argc, char *argv[]) {
| if (argc!=4) {
| puts("print usage error");
| ex;
| }
| if (isalpha(argv[1]) || isalpha(argv[2])) {
| puts("print non alpha allowed");
| ex;
| }
| FILE *fp;
| double x,y;
| x=strtod(argv[1],NULL);
| y=strtod(argv[2],NULL);
| if ((fp=fopen(argv[3],"a"))==EOF) {
| puts("fopen error");
| }
| fprintf(fp,"%.2f",x,y);
| if (fclose(fp)==EOF) {
| puts("fclose error");
| }
| return 0;
| }
`----

So come on Bill, you can do better than that!

[Bill Cunningham]

"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

Yes. (*blush*)

You left me kinda scratching my head there on that one Keith. I'd never
seen int *argv[] before. But what do I know.

Bill

[Bill Cunningham]

"Richard" <rg****@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

Non production code!
Yes that's right Richard. Non production meant to be used only by me or I
would use exit(EXIT_FAILURE) everytime it is to be used and not the #define
ex macro.

Bill

[Bill Cunningham]

"Richard" <rg****@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

You need to improve your trolling - pretending that you dont know how to
[snip]

F?ck off.

[santosh]

Richard wrote:

"Bill Cunningham" <no****@nspam.comwrites:

>Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");
ex;
}
FILE *fp;
double x,y;
x=strtod(argv[1],NULL);
y=strtod(argv[2],NULL);
if (fp=fopen(argv[3],"a"))==EOF) {
puts("fopen error");
}
fprintf(fp,"%.2f",x,y);
if (fclose(fp))==EOF) {
puts("fclose error");
}
return 0;
}

I needed a good laugh so I complied the rubbish above. It took 10
seconds to get it to compile with only warnings.

<snip>

Why republish horribly broken code when you aren't going to attempt to
correct it?

That it compiles is beside the point.

[Anand Hariharan]

On Aug 4, 12:33*pm, "Bill Cunningham" <[e-mail]:

"Keith Thompson" <[e-mail] in message

news:ln************@nuthaus.mib.org...

Yes. *(*blush*)

* * You left me kinda scratching my head there on that one Keith. I'dnever
seen int *argv[] before.

There was sufficient context around that particular statement to
suggest that it was just a slip by Keith Thompson.

This was before the statement:

<quote>
In particular, strictly speaking, the use of argv doesn't involve
multidimensional arrays; rather, it involves a pointer to the first
element of an array of pointers to strings (where a "pointer to
string" is a pointer to the first element of an array of char
containing a string).
</quote>

And this after the statement:

<quote>
argv[i], for an integer value i, is a pointer to a string.
</quote>

But what do I know.

Am sure you are following the posts (cf. else-thread by Barry Schwarz,
Santosh, Ian Collins et al.) that have been betting on what exactly
you are doing here?

- Anand

[Bill Cunningham]

"santosh" <sa*********@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

Why republish horribly broken code when you aren't going to attempt to
correct it?

That it compiles is beside the point.

This has been re-written Santosh. Or as you say there would have been no
reason to reprint it. I am seeing a lot of notes and warnings from the
compiler too on this one. I was republishing new code for William to look at
as there was a request for compile warnings and the like.

Bill

[Richard]

santosh <sa*********@gmail.comwrites:

Richard wrote:

>"Bill Cunningham" <no****@nspam.comwrites:

>>Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");
ex;
}
FILE *fp;
double x,y;
x=strtod(argv[1],NULL);
y=strtod(argv[2],NULL);
if (fp=fopen(argv[3],"a"))==EOF) {
puts("fopen error");
}
fprintf(fp,"%.2f",x,y);
if (fclose(fp))==EOF) {
puts("fclose error");
}
return 0;
}

I needed a good laugh so I complied the rubbish above. It took 10
seconds to get it to compile with only warnings.

<snip>

Why republish horribly broken code when you aren't going to attempt to
correct it?

That it compiles is beside the point.

Don't be such a moron all your life Santosh. It compiling is the first
step to get Bill to fix his own bugs. So no, compiling it is NOT beside
the point.

[Bill Cunningham]

Santosh or anyone,

isalpha takes as its parameter an int. If it is testing to see if something
is a char it doesn't make sense to me to take an int. What am I not seeing?

http://www.cppreference.com/stdstring/isalpha.html

This is a pretty good reference page. char **argv is the parameter I am
passing to main. isalpha is not going to take this. It wants an int. Am I
going to have to use atoi in here somewhere just to test if something is a
char or not?

Bill

[Keith Thompson]

"Bill Cunningham" <no****@nspam.comwrites:

"Richard" <rg****@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

Non production code!

Yes that's right Richard. Non production meant to be used only by me or I
would use exit(EXIT_FAILURE) everytime it is to be used and not the #define
ex macro.

In code meant to be used only by you, you can do anything you like.

If you want to post it here and expect to get help, I suggest that you
drop the "ex" macro and write "exit(EXIT_FILAURE)", so that it's
easier for us to read your code and offer advice.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Keith Thompson]

"Bill Cunningham" <no****@nspam.comwrites:

"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

>Yes. (*blush*)

You left me kinda scratching my head there on that one Keith. I'd never
seen int *argv[] before. But what do I know.

"int *argv[]" was a mistake on my part. Please ignore it.

What I meant was "char *argv[]".

To restore some context and correct my own error:

argv can be declared either as char **argv or as char *argv[].

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[santosh]

Bill Cunningham wrote:

>
"santosh" <sa*********@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

>Why republish horribly broken code when you aren't going to attempt
to correct it?

That it compiles is beside the point.

This has been re-written Santosh. [ ... ]

My question was at Richard.

[santosh]

Bill Cunningham wrote:

Santosh or anyone,

isalpha takes as its parameter an int. If it is testing to see if
something is a char it doesn't make sense to me to take an int. What
am I not seeing?

This question has been debated to death here. Just search the archives.

http://www.cppreference.com/stdstring/isalpha.html

This is a pretty good reference page. char **argv is the parameter I
am passing to main. isalpha is not going to take this.

Right.

It wants an
int. Am I going to have to use atoi in here somewhere just to test if
something is a char or not?

No. What is the type of argv[n][n]? Will that be compatible with the
type that isalpha takes?

[Keith Thompson]

"Bill Cunningham" <no****@nspam.comwrites:

"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000h sk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");
ex;
}
FILE *fp;
double x,y;
x=strtod(argv[1],NULL);
y=strtod(argv[2],NULL);
if (fp=fopen(argv[3],"a"))==EOF) {
puts("fopen error");
}
fprintf(fp,"%.2f",x,y);
if (fclose(fp))==EOF) {
puts("fclose error");
}
return 0;
}

This still has syntax errors. Look at the line with the isalpha
calls. Count the parentheses.

Here's your next assignment. Do not post code that produces an error
message containing the phrase "syntax error" or "parse error". In
most cases, that will be the very first error reported by the
compiler. Fix that error and recompile. Repeat until you have no
syntax errors. *Then* you can post your code and ask for further
help.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Bill Cunningham]

"santosh" <sa*********@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

> This has been re-written Santosh. [ ... ]

My question was at Richard.

My mistake.

Bill

[Richard]

santosh <sa*********@gmail.comwrites:

Bill Cunningham wrote:

> Santosh or anyone,

isalpha takes as its parameter an int. If it is testing to see if
something is a char it doesn't make sense to me to take an int. What
am I not seeing?

This question has been debated to death here. Just search the
archives.

So has every other question asked here. If you are not willing to
explain, why are you here? Will you refer posters to other posts about
casting the return of malloc, the return type of main etc? I doubt it.

>

>http://www.cppreference.com/stdstring/isalpha.html

This is a pretty good reference page. char **argv is the parameter I
am passing to main. isalpha is not going to take this.

Right.

>It wants an
int. Am I going to have to use atoi in here somewhere just to test if
something is a char or not?

No. What is the type of argv[n][n]? Will that be compatible with the
type that isalpha takes?

You are wrong. He might well have to use it if the characters are there
as part of a command line integer parameter. He needs to convert the
character sequence to that integer.

--

[Bill Cunningham]

"santosh" <sa*********@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

No. What is the type of argv[n][n]? Will that be compatible with the
type that isalpha takes?

Oh I see. I've never used argv[][]'s before. I see so much clearly now.
Thank you Thank you. I am going to try this code again.

Bill

[santosh]

Richard wrote:

santosh <sa*********@gmail.comwrites:

<snip>

>Why republish horribly broken code when you aren't going to attempt
to correct it?

That it compiles is beside the point.

Don't be such a moron all your life Santosh. It compiling is the first
step to get Bill to fix his own bugs.

No. Understanding C is the first step.

A typical C compiler will gladly accept highly bastardised C and will
attempt to generate an executable. Fixing errors reported by a compiler
*after* having learnt the language is one thing, but depending on
compiler diagnostics to learn the rules and semantics of C is not very
bright, IMO.

So no, compiling it is NOT beside the point.

Unless invoked in conforming mode an implementation is allowed to
silently accept anything and produce an executable. Even under
conforming mode, only diagnostics are guaranteed. Undefined behaviour
that is not a constraint violation might still be silently accepted and
typically you do *not* want that.

It's better to learn the language first and then use the compiler,
rather than depending on it to learn the language.

Bill should re-open K&R and start with the first page. I understand that
he has not progressed beyond the first few pages after several years,
but he really has no other alternative. Merely messing around with
programs written with guesswork and compiled with luck isn't going to
get him anywhere.

[santosh]

Richard wrote:

santosh <sa*********@gmail.comwrites:

>Bill Cunningham wrote:

>>char **argv is the parameter I am passing to main. isalpha is not
going to take this. It wants an int. Am I going to have to use atoi
in here somewhere just to test if something is a char or not?

No. What is the type of argv[n][n]? Will that be compatible with the
type that isalpha takes?

You are wrong. He might well have to use it if the characters are
there as part of a command line integer parameter. He needs to convert
the character sequence to that integer.

Don't you find it tiresome to disagree just for the sake of it?

My response was directed at the specific complaint by Bill that
*isalpha* won't like argv as an argument. Clearly he wants to run
through the strings to check whether any of them contain alphabetic
characters (which would be error).

So what you say above makes no sense at all.

[Richard]

santosh <sa*********@gmail.comwrites:

Richard wrote:

>santosh <sa*********@gmail.comwrites:

<snip>

>>Why republish horribly broken code when you aren't going to attempt
to correct it?

That it compiles is beside the point.

Don't be such a moron all your life Santosh. It compiling is the first
step to get Bill to fix his own bugs.

No. Understanding C is the first step.

Sigh. Obviously.

>
A typical C compiler will gladly accept highly bastardised C and will
attempt to generate an executable. Fixing errors reported by a compiler
*after* having learnt the language is one thing, but depending on
compiler diagnostics to learn the rules and semantics of C is not very
bright, IMO.

Learning by doing Santosh. its why I recommend using a debugger. Clearly
Bill is incapable of reading code.

The point, which even you in your most "clc reg" mode must see that
fixing the bugs so he can COMPILE the code can only be benefifical. He
could not even match brackets for goodness sake.

[Richard]

santosh <sa*********@gmail.comwrites:

Richard wrote:

>santosh <sa*********@gmail.comwrites:

>>Bill Cunningham wrote:

>>>char **argv is the parameter I am passing to main. isalpha is not
going to take this. It wants an int. Am I going to have to use atoi
in here somewhere just to test if something is a char or not?

No. What is the type of argv[n][n]? Will that be compatible with the
type that isalpha takes?

You are wrong. He might well have to use it if the characters are
there as part of a command line integer parameter. He needs to convert
the character sequence to that integer.

Don't you find it tiresome to disagree just for the sake of it?

I would if that were the reason. But you were wrong. Or appeared to be
wrong.

He asked if he could use atoi in there somewhere. And yes, he can
indeed. Remember we are talking about Bill. You talked about
isalpha. However he still needs the integer values from the chars passed
in.

[santosh]

Richard wrote:

santosh <sa*********@gmail.comwrites:

>Richard wrote:

>>santosh <sa*********@gmail.comwrites:

<snip>

>>>Why republish horribly broken code when you aren't going to attempt
to correct it?

That it compiles is beside the point.
Don't be such a moron all your life Santosh. It compiling is the
first step to get Bill to fix his own bugs.

No. Understanding C is the first step.

Sigh. Obviously.

>>
A typical C compiler will gladly accept highly bastardised C and will
attempt to generate an executable. Fixing errors reported by a
compiler *after* having learnt the language is one thing, but
depending on compiler diagnostics to learn the rules and semantics of
C is not very bright, IMO.

Learning by doing Santosh. its why I recommend using a debugger.
Clearly Bill is incapable of reading code.

The point, which even you in your most "clc reg" mode must see that
fixing the bugs so he can COMPILE the code can only be benefifical. He
could not even match brackets for goodness sake.

The very reason he started this thread was because he *could* *not*
understand the errors and warnings his compiler gave him. And that is a
direct result of the fact that he has only correctly learnt a minuscule
fraction of C (though he incorrectly uses a rather larger portion of
it.)

You need to know the language to understand all but the most simple of
typical compiler messages. Us telling him how to fix the code to shut
the compiler up is no good, since he doesn't understand *why* those
fixes are needed. There really is no alternative for him but to keep
trying from the very beginning of a good tutorial, if he really is
serious about this.

I'm surprised that you advocate this "learning by doing" philosophy for
Bill of all the people. Someone who can't match parenthesis isn't going
to get very far with gdb or gcc. It's better to understand than to
learn.

[Keith Thompson]

Keith Thompson <ks***@mib.orgwrites:

"Bill Cunningham" <no****@nspam.comwrites:

>"Richard" <rg****@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

Non production code!

Yes that's right Richard. Non production meant to be used only by me or I
would use exit(EXIT_FAILURE) everytime it is to be used and not the #define
ex macro.

In code meant to be used only by you, you can do anything you like.

If you want to post it here and expect to get help, I suggest that you
drop the "ex" macro and write "exit(EXIT_FILAURE)", so that it's
easier for us to read your code and offer advice.

I meant "exit(EXIT_FAILURE)", of course.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[osmium]

"Bill Cunningham" wrote:

Here's a reposting of the source.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[]) {
if (argc!=4) {
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2]) {
puts("print non alpha allowed");

--- snip ---
Someone mentioned the other day that you should cut down the size of your
program to get something more manageable and you said you didn't know how to
do that. Here is your program, cut down and reformatted to one of the
acceptable formats. It does not compile. Can you see why? Fix any
problems and *only then* start adding your original stuff back in, compiling
**very** often. If you get warnings, fix them too or at least understand
what the warnings mean and why the compiler presented them, and consciously
deciding that you can safely ignore any warnings provided.

#include <stdio.h>
#include <stdlib.h>
#include <ctype.h>
#define ex exit(EXIT_FAILURE)

int main (int argc, char *argv[])
{
if (argc!=4)
{
puts("print usage error");
ex;
}
if (isalpha(argv[1]) || isalpha(argv[2])
{
puts("print non alpha allowed");
ex;
}
return 0;
}

[Default User]

santosh wrote:

Richard wrote:

You are wrong. He might well have to use it if the characters are
there as part of a command line integer parameter. He needs to
convert the character sequence to that integer.

Don't you find it tiresome to disagree just for the sake of it?

Of course not. He is a troll. And you're playing his game -- again.


Brian

[Bill Cunningham]

"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

How do I know if it's posted through google groups ?

Bill

[Bill Cunningham]

"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

"Bill Cunningham" <no****@nspam.comwrites:

>"William Pursell" <bi**********@gmail.comwrote in message
news:d3**********************************@79g2000 hsk.googlegroups.com...

Assuming gcc & bash, try:
$ gcc foo.c 2>&1 | less

Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

Ok I will start paying attention to the headers and if it says
googlegroups I'll put a line or something somewhere to make things more
readable. I'll get this straightened out.

Bill

[Bill Cunningham]

"Anand Hariharan" <ma********************@gmail.comwrote in message
news:21**********************************@c65g2000 hsa.googlegroups.com...

Am sure you are following the posts (cf. else-thread by Barry Schwarz,
Santosh, Ian Collins et al.) that have been betting on what exactly
you are doing here?

Actually I haven't been reading all the foolishness but I am aware of what's
going on from reading a couple of posts.
Bill

[Richard]

"Bill Cunningham" <no****@nspam.comwrites:

"Anand Hariharan" <ma********************@gmail.comwrote in message
news:21**********************************@c65g2000 hsa.googlegroups.com...

Am sure you are following the posts (cf. else-thread by Barry Schwarz,
Santosh, Ian Collins et al.) that have been betting on what exactly
you are doing here?

Actually I haven't been reading all the foolishness but I am aware of what's
going on from reading a couple of posts.
Bill

Why are you duplicating what the previous poster said?

[Bill Cunningham]

"Richard" <rg****@gmail.comwrote in message
news:g7**********@registered.motzarella.org...

Why are you duplicating what the previous poster said?

Oh no not again. Posts from google groups screw up my posting Richard for
some reason.

Bill

[Keith Thompson]

"Bill Cunningham" <no****@nspam.comwrites:

"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

>Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

How do I know if it's posted through google groups ?

Check the message headers for any of:

Organization: http://groups.google.com
Message-ID: <ANYTHING.googlegroups.com>
X-Complaints-To: gr**********@google.com
Complaints-To: gr**********@google.com

Organization is the most likely to be easily accessible.

(Or get OE Quotefix to work properly, but as I mentioned I can't help
you with that.)

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Richard Heathfield]

Keith Thompson said:

"Bill Cunningham" <no****@nspam.comwrites:

>"Keith Thompson" <ks***@mib.orgwrote in message
news:ln************@nuthaus.mib.org...

>>Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

How do I know if it's posted through google groups ?

Check the message headers for any of:

He can't even learn something as simple as printf, and now you're trying to
teach him about NNTP headers?

I admire your futility^Woptimism, but I have a suggestion for you. In
future, don't try to correct his posting style. Such corrections are, in
any case, strictly off-topic. Instead, why not just ignore any article in
which he fails to quote correctly? That way, maybe we can /all/ get some
sleep.

This technique can be extended. By ignoring any article in which he posts
code where the parentheses don't match; where the code is so badly laid
out that it's unreadable; where the question is about diagnostic messages
but the article omits source or messages or both; by ignoring all such
articles, we could perhaps encourage Mr Cunningham to care about these
little details without nagging him all the time. A stony silence can
sometimes be more eloquent than a tedious regurgitation of old complaints.

--
Richard Heathfield <http://www.cpax.org.uk>
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999

[Nick Keighley]

On 4 Aug, 19:36, Keith Thompson <[e-mail]:

Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. *If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

google no longer has this particular problem

--
Nick Keighley

[Doug Miller]

In article <lnNlk.240$xv.173@trnddc02>, "Bill Cunningham" <no****@nspam.comwrote:

>
"Anand Hariharan" <ma********************@gmail.comwrote in message
news:21**********************************@c65g200 0hsa.googlegroups.com...

Am sure you are following the posts (cf. else-thread by Barry Schwarz,
Santosh, Ian Collins et al.) that have been betting on what exactly
you are doing here?

Actually I haven't been reading all the foolishness but I am aware of what's
going on from reading a couple of posts.
Bill

Dammit, Bill, will you *please* quote properly??

[Keith Thompson]

Nick Keighley <ni******************@hotmail.comwrites:

On 4 Aug, 19:36, Keith Thompson <[e-mail]:

>Bill, if you can't get OE Quotefix to work for you, then please pay
attention when you post a followup. *If the article to which you're
replying was posted through Google Groups, please do *something* to
indicate the division between the quoted material and your new text.

google no longer has this particular problem

I know that Google Groups now does proper quoting. This appears to be
a different problem, an interaction between Google Groups and Outlook
Express, the newsreader that Bill is using.

Apparently if you use OE to post a followup to an article that was
posted to Google Groups, OE doesn't quote properly. Something called
"OE Quotefix" is supposed to correct this.

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Richard Bos]

Barry Schwarz <sc******@dqel.comwrote:

Two possibilities:

This is very true and YOU are wasting our time.

You are having more fun than we can imagine jerking us around and
WE are wasting our time.

No, one possibility: either Bill is lying or he isn't, it really doesn't
matter which, because you are wasting your time either way.

Richard