www.delorie.com/archives/browse.cgi | search |
From: | gpt20 AT thor DOT cam DOT ac DOT uk (G.P. Tootell) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: how to interpret this... |
Date: | 3 Dec 1996 11:07:11 GMT |
Organization: | University of Cambridge, England |
Lines: | 18 |
Sender: | gpt20 AT hammer DOT thor DOT cam DOT ac DOT uk (G.P. Tootell) |
Distribution: | world |
Message-ID: | <5811kv$o3u@lyra.csx.cam.ac.uk> |
References: | <57ve1o$rfk AT lyra DOT csx DOT cam DOT ac DOT uk> <coUZoAAwf2oyEwxk AT chocolat DOT foobar DOT co DOT uk> |
NNTP-Posting-Host: | hammer.thor.cam.ac.uk |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
hmm. i noticed that it gave a warning when i forgot to bracket a <<, which turned out to be a good thing because it did indeed need brackets. it would just seem nice to have warned me about this problem. oh well. whine moan complain etc :) heh nik |> Because all the '==' operators have equal precedence C is allowed to |> evaluate them in *any* order it likes. |> About the only one it won't use is a==b && b==c && c==0 ;) since each |> '==' evaluation reduces its 2 inputs to a boolean value (destroying the |> value you planned on testing ;) |> |> -- |> Paul Shirley --
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |