Hey Tijs, > > > In general it's good to inform/promise the compiler when the program is > > > not > > > going to change data (using const). However, you'll have to adjust to the > > > function definition types of the other functions that you are going to use > > > in your new function. > > [Snip example code] > This is what I meant ;-) Supplying a const pointer to a function which > requires a non-const pointer as argument should make the compiler complain, > because the function "intents" to change the data in the memory address the > pointer is referring to.
Ah, right. I misinterpreted your "by definition" to mean "always and unchangeable", where you actually (of course) meant "in the function definition". Heh, language... Gr. Matthijs _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
