Messages in this thread | | | From | dewar@gnat ... | Subject | Re: [PATCH] C undefined behavior fix | Date | Fri, 4 Jan 2002 17:43:25 -0500 (EST) |
| |
<<Sorry, you are correct. I should have written "One of the reasons why C used to be a good language for writing operating system kernels ..." >>
C is perfectly well suited for writing operating system kernels, but you absolutely HAVE to know what you are doing, and that includes knowing the C standard accurately, and clearly identifying any implementation dependent behavior that you are counting on.
The "used to be" is bogus. The (base + offset) memory model of C has been there since the earliest days of the definition of C. The only thing that "used to be" the case is that people ignored these rules freely and since compilers were fairly stupid, they got away with this rash behavior.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |