From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <15577233041e4238e7a9c8e58d670ddd@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Brdline
From: Charles Forsyth <forsyth@terzarima.net>
Date: Mon, 16 Jan 2006 13:57:20 +0000
In-Reply-To: <599f06db0601160537j28ecb776hec7ebfe8b392615a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: d9db8514-ead0-11e9-9d60-3106f5b1d025

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