Roger (K8RI) wrote:
And they finally gave us the ability to turn the type checking on.
:-)) Originally it just assumed the programmer knew what they were
doing and let you do it what ever it was. Lordy...pointers with
dynamic memory, dynamic arrays, linked lists, circular linked lists
and bidirectional linked lists. It gave the programmer a good feel
for the two words, new and free. :-)) Oh yah, and memory leaks.

Wow, expecting engineers to do it correctly... Radical concept, eh? grin

With regards to type checking, well, you just ran 'lint' on your code to
give yourself a better feel for it... I liked the level of strictness
with regards to type checking in standard 'C'... I hated what Ada
required us to do... More often than not, things became a system.address
type in Ada for what I was having to do...

You can be object oriented in standard 'C', it just takes the right
frame of mind... While I was working on a NASA contract for the MCC and
SSCC, we utilized this technique. Here's a write-up that I did on it
awhile back describing it:

http://grumman581.googlepages.com/object-oriented-c

We had a lot of different groups each working on different portions of
the entire system and these would be linked at a later date and expected
to work together. Collisions at link time were not acceptable.