Re: [PATCH] struct loop_info64

Linus Torvalds (torvalds@transmeta.com)
Fri, 18 Apr 2003 10:50:31 -0700 (PDT)


On Fri, 18 Apr 2003 Andries.Brouwer@cwi.nl wrote:
>
> I agree less with the statement that they must be u32 instead of int.
> My main reason is historical: the Unix interface is defined in terms
> of char/int/long.

Yes, but it sucks. Look at how _hard_ it has been to add standard sized
types even just to user-mode C.

It so happens that "int" has been fairly stable at 32 bits for a long
time, and largely continues to be so. That's make it less painful than
most other things. "long" has certainly long since stopped being a good
type for doing any portable stuff.

So while "char" and "int" have happened to not be painful, it's still
wrong to depend on types that aren't explicitly sized, because it _will_
break eventually.

Linus

-
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/