9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] dns vs. textrr
Date: Thu, 19 Jan 2012 19:14:37 -0500	[thread overview]
Message-ID: <5e454df178d1b71e46a9b4d2390a366f@coraid.com> (raw)
In-Reply-To: <7A76A074-BE06-4FCC-BD78-7E4DFC12CA43@orthanc.ca>

On Thu Jan 19 19:13:14 EST 2012, lyndon@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



  reply	other threads:[~2012-01-20  0:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 16:01 erik quanstrom
2012-01-19 17:00 ` Jeff Sickel
2012-01-19 17:17   ` erik quanstrom
2012-01-19 22:12     ` erik quanstrom
2012-01-19 23:32       ` Lyndon Nerenberg
2012-01-19 23:56         ` erik quanstrom
2012-01-20  0:11           ` Lyndon Nerenberg
2012-01-20  0:14             ` erik quanstrom [this message]
2012-01-20  0:39               ` Lyndon Nerenberg
2012-01-20  6:31     ` Jeff Sickel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e454df178d1b71e46a9b4d2390a366f@coraid.com \
    --to=quanstro@labs.coraid.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).