home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!wupost!eclnews!swarm.wustl.edu!wilcox
- From: wilcox@swarm.wustl.edu (Don Wilcox)
- Subject: Re: incrementation differences/THINK C 4.0 vs. 5.0
- Message-ID: <1992Aug28.151228.28438@wuecl.wustl.edu>
- Sender: usenet@wuecl.wustl.edu (Usenet Administrator)
- Nntp-Posting-Host: swarm
- Organization: Washington University in St. Louis, MO
- References: <D2150035.c21d0r@outpost.SF-Bay.org> <1992Aug27.182157.16567@qualcomm.com> <38188@unix.SRI.COM>
- Date: Fri, 28 Aug 1992 15:12:28 GMT
- Lines: 28
-
- In article <38188@unix.SRI.COM> mxmora@unix.SRI.COM (Matt Mora) writes:
- >In article <1992Aug27.182157.16567@qualcomm.com> sdorner@qualcom.qualcomm.com (Steve Dorner) writes:
- >
- >What about this common bug that I think even shut down ATT long distance
- >system:
- >
- >if (a=b) {
- > //then do something
- >}
- >
- >When the programmer really meant a==b. Should there be a option to check
- >if statements?
-
- Borland's C++ compiler, which can optionally generate 50+ style warnings, can
- do this. And since I never write code like this where I mean '=', this works
- well for me.
-
- BTW, I had heard that it was a missing comma in a shared Fortran COMMON block
- that shut down ATT.
-
- >
- >Matt
- >
- Don
- --
- Don Wilcox | "For I am not ashamed of the Gospel of
- Washington University in St. Louis | Christ, for it is the power of salvation
- email: wilcox@swarm.wustl.edu | to all who believe."
-