On Thu Jan 19 19:13:14 EST 2012, lyn...@orthanc.ca wrote: > > On 2012-01-19, at 3:56 PM, erik quanstrom wrote: > > > it's probablly the best option, > > if the goal is to rehabilitate Brdline(). i'm wondering if it shouldn't > > just be considered depricated. > > If you don't think of Brdline() as a 'C char *' construct, it's a useful > vessel to escape from one of the most evil parts of parsing text. I won't > begin to recount the pain I've endured dealing with text protocol parsers > that didn't get the \r\n split across the buffer boundary right. > > If you're claiming to read a line, just do it. I don't care if you have to > buy dictionaries to hold the words, and front-end loaders from which to fill > them! > > Certainly some smarts can be added to deal with inflated buffers when they > are no longer needed. But for now, dying from malloc(HUGE) isn't much worse > than the current behaviour.
depricated, as in use Brdstr(2) instead which does its own dynamic allocation. - erik
