On Tue, 04 Apr 2000, you wrote:
> strcmp() never returns a char, it always returns a signed integer.
> (specifically and int). Whether the compiler generates the exact same parse
> tree depends on the compiler and lexer.
> tom r wrote:
Oops, you are exactly right, my mistake. strcmp returns an int and therefor
its return value is never (correctly) evaluated in a pointer context.
Pick a function that does return a char* and the rest of my statement (I think)
holds true.
>
> > I just recently read a C FAQ that points out that if the right template is in
> > scope, so that the compiler knows that strcmp returns a char* they are not
> > merely equivalent but REALLY exactly the same. Same parse tree is generated,
> > everything. There are some interesting subtlties with if(!expr) and if(expr
> > == 0) in a pointer context.
> --
> Jerry Feldman <[EMAIL PROTECTED]>
> Boston Linux and Unix user group
> http://www.blu.org
--
email me at [EMAIL PROTECTED]
"Somebody once told me that in basketball you can't hold the ball and run.
I got a basketball and tried it and it worked just fine. He obviously didn't
understand basketball." Attributed to Roger Miller.
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
