[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] [PATCH] Improved resilience in gps_shm_close() in case it
From: |
Hal Murray |
Subject: |
Re: [gpsd-dev] [PATCH] Improved resilience in gps_shm_close() in case it is called after an unsuccessful gps_shm_open() |
Date: |
Tue, 02 Aug 2016 18:33:20 -0700 |
address@hidden said:
> The first time it catches a typo you'll likely be sold. How often have you
> spent hours looking for a bug like this:
> if ( my_pointer =3D NULL)
No need to wait for an example. I'm already convinced.
I remember when I learned about type checking. I'd been working in assembly
language. (It was a long time ago.) I was adapting to a new language and
new environment. At first, the new part was taking most of my time. Before
long, I learned how to drive the editor and got the ()s and BEGIN/END and ;
level sorted out. Then the compiler gave me an obscure error message. It
was a missing * or &. As soon as I figured out what it was telling me, I was
sold. The stronger the checking the better.
--
These are my opinions. I hate spam.