From: Nikolai Weibull Date: 2005-03-14T01:31:55+09:00 Subject: off_t weirdness Try this on a Linux+glibc+GCC system: #include #include #include int main(void) { return sizeof(off_t); } on my system the result is 4. Now, if I write this as #include #include #include int main(void) { return sizeof(off_t); } instead, the result is 8. This "bug" set me back about an hour of work, which kind of sucked. This behavior worries me a bit, as there may be places where ruby.h isn't included and the sizeof(off_t) will be 4 and others where it is included and the sizeof(off_t) will be 8, causing all weird kinds of behavior. Is there a reason for why this is so, or is it simply a problem in how my system has set up its headers?, nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}