From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom To: 9fans@cse.psu.edu, Charles Forsyth References: <15577233041e4238e7a9c8e58d670ddd@terzarima.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 In-Reply-To: <15577233041e4238e7a9c8e58d670ddd@terzarima.net> Subject: Re: [9fans] Brdline Message-Id: <20060117005616.DEFB01140E3@dexter-peak.quanstro.net> Date: Mon, 16 Jan 2006 18:56:16 -0600 Cc: Topicbox-Message-UUID: da93e730-ead0-11e9-9d60-3106f5b1d025 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 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.