Re: Check on correctness
- From: "Ed Weir \(ComCast\)" <Anon@xxxxxxxx>
- Date: Thu, 6 Jul 2006 21:27:56 -0700
"Alexander Grigoriev" <alegr@xxxxxxxxxxxxx> wrote in message
news:%23Ir5aYXoGHA.4996@xxxxxxxxxxxxxxxxxxxxxxx
| See C++ standard, paragraph 2.5.
You mean, http://www.open-std.org/jtc1/sc22/open/n2356/? Heh. That took
only about ten years, and they STILL didn't get it right... comittees... MY
way is always better.
|
| "Ed Weir (ComCast)" <Anon@xxxxxxxx> wrote in message
| news:4bmdnUNNwsOm9THZnZ2dnUVZ_u-dnZ2d@xxxxxxxxxxxxxx
| > "Tom Serface" <tserface@xxxxxxx> wrote in message
| > news:Ow9Xv1HoGHA.4240@xxxxxxxxxxxxxxxxxxxxxxx
| > |I agree about Gimpel lint. Once you figure out how to use the program
it
| > | becomes invaluable. I believe the compiler will still allow you to do
| > an
| > | assignment inside of a conditional statement (or just about anywhere
for
| > | that matter), but it does gripe about it now.
| > |
| > | Tom
| > |
| > | "Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
| > | news:199oa2918pojc3lq4kp4qrik7899npbl81@xxxxxxxxxx
| > |
| > | > I have found lint (I use gimpel lint) to be one of the best
| > diagnostics
| > to
| > | > run on code I'm
| > | > given. I can find 10-20 bugs just from the lint listings on any
| > | > reasonably-sized
| > | > (50K-150K lines) project. I just wish C were even more hard-nosed
| > about
| > | > diagnostics, such
| > | > as forbidding the use of int where bool is required.
| >
| > Warning: <flamebait>
| > One method I used awhile ago that was subsequently adopted by several
| > large
| > Japanese corporations was thus:
| >
| > #define is ==
| > #define isnt !=
| > #define and &&
| > #define or ||
| > #define not !
| >
| > Which resulted in ridiculously english-looking C/C++ code that any
| > numbscull
| > could intuitively understand. Any embedded assignments made by accident
| > were easily avoided and subtle bugs precluded. Later I even saw this as
a
| > ANSI proposed standard as new C/C++ keywords!
| > </flamebait>
| >
| > Hehe
| >
| > -- Ed.
| >
| > -----------------------------------------------------
| > hex->bin->b64
| > F9E7707A2AF502D0A899C6ACB43A2D35EB7E
| >
|
|
.
- References:
- Check on correctness
- From: tim@xxxxxxxxxxxxxxxxxxxxxx
- Re: Check on correctness
- From: www.fruitfruit.com
- Re: Check on correctness
- From: tim@xxxxxxxxxxxxxxxxxxxxxx
- Re: Check on correctness
- From: Joseph M . Newcomer
- Re: Check on correctness
- From: Tom Serface
- Re: Check on correctness
- From: Sgt. York
- Re: Check on correctness
- From: Ian Semmel
- Re: Check on correctness
- From: Sgt. York
- Re: Check on correctness
- From: Tom Serface
- Re: Check on correctness
- From: Joseph M . Newcomer
- Re: Check on correctness
- From: Tom Serface
- Re: Check on correctness
- From: Ed Weir \(ComCast\)
- Re: Check on correctness
- From: Alexander Grigoriev
- Check on correctness
- Prev by Date: How to disable the "X" close button of DialogBox.?
- Next by Date: Re: How to disable the "X" close button of DialogBox.?
- Previous by thread: Re: Check on correctness
- Next by thread: Re: Check on correctness
- Index(es):