> pretty sure its because valid_char was declared after > executable code in the function (ie. allowed in C++ but not C). > > heh heh ... guess the mind yearns for C++ ;) But then, gcc should complain as well, no? Michael.