On 10 Dec 2009, at 06:43, D.J. Stachniak wrote: > with him. char *foo is really the "right" way to do it
How (other than by awkward convention) is it "right"? int *x; *x = 1; // makes perfect sense: we declared *x an int! Just a little bugbear of mine. Goes back to when I first encountered C, and noone told me about malloc until I explicitly asked about an equivalent of pascal's new. My coworkers at the time didn't know, there was no online resource, and most unforgiveably, my only reference at the time (K&R first edition) makes no mention of malloc/free or any memory issues! Please ignore useless rant :/ Any C style (other than typedef) leads to logical nonsense! -- Nick Kew
