Yes/No

[Meenu]

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

[Ian Malone]

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

Google "C++ operator precedence"
(yes, unless you have some funny #define going round)

--
imalone

[Meenu]

Ian Malone wrote:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

Google "C++ operator precedence"
(yes, unless you have some funny #define going round)

--
imalone

Even I thought so, but the answer mentioned is no, and I can't figure
out a reason

[Ian Malone]

Ian Malone wrote:

Google "C++ operator precedence"

Oops, wrong ng. Obviously that says 'c operator precedence'

--
imalone

[Meenu]

Ian Malone wrote:

Ian Malone wrote:

Google "C++ operator precedence"

Oops, wrong ng. Obviously that says 'c operator precedence'

--
imalone

I didn't get it...:(
pls elaborate

[Ian Malone]

Meenu wrote:

Ian Malone wrote:

Ian Malone wrote:

Google "C++ operator precedence"

Oops, wrong ng. Obviously that says 'c operator precedence'

I didn't get it...:(
pls elaborate

Thought I was reading comp.lang.c++, not comp.lang.c.

Incidentally, since the ternary operator is meant to
return a value, the assignments need to be parenthesised,
since they have a lower priority (they are statements to
be evaluated). You need
a<=20?(b=30):(c=30);

--
imalone

[Simon Morgan]

On Fri, 22 Jul 2005 03:39:33 -0700, Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

How's the homework going? Obviously not very well if you still haven't
grasped basic operator precedence. May I suggest reading a book or
actually attending class?

[Meenu]

Simon Morgan wrote:

On Fri, 22 Jul 2005 03:39:33 -0700, Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

How's the homework going? Obviously not very well if you still haven't
grasped basic operator precedence. May I suggest reading a book or
actually attending class?

Well thanks,
my confusion was that since parentheses only make the condition part
easier to see, other than that, i don't feel there would be any change
in the output.

[Dik T. Winter]

In article <11**********************@g14g2000cwa.googlegroups .com> "Meenu" <me******@yahoo.com> writes:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

The same in what way? Both should give an error message from the compiler.
--
dik t. winter, cwi, kruislaan 413, 1098 sj amsterdam, nederland, [phone]
home: bovenover 215, 1025 jn amsterdam, nederland; http://www.cwi.nl/~dik/

[CBFalconer]

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

I wouldn't even bother to read them. They are infested with blank
elidation.

--
Chuck F (cb********@yahoo.com) (cb********@worldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!

[lawrence.jones]

Ian Malone <ib***@cam.ac.uk> wrote:

Incidentally, since the ternary operator is meant to
return a value, the assignments need to be parenthesised,
since they have a lower priority (they are statements to
be evaluated). You need
a<=20?(b=30):(c=30);

The ? and : act like parentheses, so you only need to parenthesize the
final assignment:

a <= 20 ? b = 30 : (c = 30);

-Larry Jones

Mom must've put my cape in the wrong drawer. -- Calvin

[Eric Sosman]

CBFalconer wrote:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

I wouldn't even bother to read them. They are infested with blank
elidation.

The word you seek is "elision." As in "The Elision Fields,"
where one forgets one's past lives -- Egad! I'm turning Buddhist.

(Interesting thought: How can something be "infested with"
an absence? Maybe I'd understand better if I were infested
with an absinthe ...)

--
Eric Sosman
es*****@acm-dot-org.invalid

[CBFalconer]

Eric Sosman wrote:

CBFalconer wrote:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

I wouldn't even bother to read them. They are infested with blank
elidation.

The word you seek is "elision." As in "The Elision Fields,"
where one forgets one's past lives -- Egad! I'm turning Buddhist.

(Interesting thought: How can something be "infested with"
an absence? Maybe I'd understand better if I were infested
with an absinthe ...)

Yeah, it didn't look right. Would you settle for Pernod?

--
Chuck F (cb********@yahoo.com) (cb********@worldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!

[junky_fellow]

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

No. In fact both will generate compilation error.
Since precedence of conditional operator is higher than
assignement operator, the following statement
a<=20?b=30:c=30; will be interpreted like

(a<=20?b=30:c)=30;
LHS is not an lvalue, so the error.
Same is the reason for second statement.
Now, if you enclose "c=30" in parenthesis, it would
be interpreted as:
(a<=20?b=30:(c=30)); which would complile OK.

[Keith Thompson]

ju**********@yahoo.co.in writes:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

No. In fact both will generate compilation error.

Doesn't that make them equivalent?

--
Keith Thompson (The_Other_Keith) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.

[Chris Croughton]

On Fri, 22 Jul 2005 21:39:12 -0400, Eric Sosman
<es*****@acm-dot-org.invalid> wrote:

CBFalconer wrote:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;
I wouldn't even bother to read them. They are infested with blank
elidation.

The word you seek is "elision." As in "The Elision Fields,"
where one forgets one's past lives -- Egad! I'm turning Buddhist.

elide: omit by elision [Concise OED]. And it was the Elysian Fields,
which were Greek ("The Isles of the Blest"); the Romans later moved
them into the underworld for the Grateful Dead (er, I mean the righteous
dead <g>).

Not to be confused with Harlan Ellison...
(Interesting thought: How can something be "infested with"
an absence? Maybe I'd understand better if I were infested
with an absinthe ...)

Absinthe makes the font grow harder...

(But being infested with an absence of blanks is an interesting idea. I
knew exactly what he meant, but the mental image is fascinating.
Probably worth a thesis for a doctorate in philosophy...)

Chris C

[Eric Sosman]

Chris Croughton wrote:

On Fri, 22 Jul 2005 21:39:12 -0400, Eric Sosman
<es*****@acm-dot-org.invalid> wrote:

CBFalconer wrote:

Meenu wrote:
Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

I wouldn't even bother to read them. They are infested with blank
elidation.

The word you seek is "elision." As in "The Elision Fields,"
where one forgets one's past lives -- Egad! I'm turning Buddhist.

elide: omit by elision [Concise OED]. And it was the Elysian Fields,
which were Greek ("The Isles of the Blest"); the Romans later moved
them into the underworld for the Grateful Dead (er, I mean the righteous
dead <g>).

pun: the humorous use of a word in such a way as to suggest
different meanings or applications or of words having the same
or nearly the same sound but different meanings [Webster's
Seventh New Collegiate Dictionary]

elide: e told a taradiddle, e did!

--
Eric Sosman
es*****@acm-dot-org.invalid

[junky_fellow]

Keith Thompson wrote:

ju**********@yahoo.co.in writes:

Meenu wrote:

Are the two statements same:
a<=20?b=30:c=30;
(a<=20)?b=30:c=30;

No. In fact both will generate compilation error.

Doesn't that make them equivalent?

I am sorry. Yes, they are both equivalent, but both will give
compilation
error.