likewise, seek takes a vlong "where"so that a -1 "don't care" value can be used. this was the source of the sign-extension issue p9p's GBIT64 macro.
if you know you're stuck with gcc, uvlong and ~0ULL may well have be a less error- prone option. - erik Charles Forsyth <[EMAIL PROTECTED]> writes | | > What about Brdstr? it seems to me a superset of Brdline and it returns | > a char *.... | | perhaps it was added later and they didn't think of that? | i'm not sure it makes a big difference. | the whole char*/uchar* interaction is bad though. | uchar* is important to ensure no sign-extension, | but it isn't compatible with the str* functions, and explicit casts | can mask mistakes.
