Re: C internals cleanup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The general rule of thumb is to do such a clean-up before you start to
work on something of substance.

I guess that's all in how one defines "substance." :-)

My ultimate goal is to get more stringent error-checking, to get more compiler warnings enabled, and to get a splint target. splint is fantastic for tracking all sorts of memory and logic problems, but benefits greatly from getting the const qualifiers in place. Even gcc will be happier.

Thanks for the recap. It's hard to absorb what you just described just from reading mailing list history.

xoa

--
Andy Lester => andy@xxxxxxxxxxxx => www.petdance.com => AIM:petdance




--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]