From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Brdline() and continuation lines
Date: Wed, 19 Sep 2012 09:35:51 -0400 [thread overview]
Message-ID: <18674d790afd2a7602091b8d8e704712@brasstown.quanstro.net> (raw)
In-Reply-To: <22e43e02e32dd37beb7f8c52105e45b6@quintile.net>
> Anyone worked out an idiom that would allow me to
> use Brdline()/Blinelen() to read a file which
> contains continuation lines?
>
> I want to read a text file which consists of lines terminated
> by newlines, but lines with leading whitespace are considered
> to be continuation lines.
>
> Brdline() is very neat allowing me to parse input lines inside the
> Biobuf buffer without copying them to "user space", however if I
> do a Brdline(), get a line and then attempt to do another Brdline()
> I am in danger of releaseing the buffer space used by the first read.
>
> I am happy if the answer is "Brdline() cannot do this", I just feel like
> I am missing a trick, and there is elegant solution.
/*
* Bgetrune seems like overkill, but avoids passing up bad runes.
*/
int
Brdlinec(Biobuf *b, char *s, char *e)
{
char *p;
int x, slash;
Rune r;
for(p = s; e-p > UTFmax+1;){
x = Bgetrune(b);
if(x == -1)
return -1;
r = x;
if(r == '\\'){
x = Bgetrune(b);
if(x == -1)
return -1;
if(x == '\n')
continue;
p += runetochar(p, &r);
r = x;
}else if(r == '\n')
break;
p += runetochar(p, r);
}
*p = 0;
return p-e;
}
next prev parent reply other threads:[~2012-09-19 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 8:48 Steve Simon
2012-09-19 13:35 ` erik quanstrom [this message]
2012-09-19 13:49 ` Charles Forsyth
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=18674d790afd2a7602091b8d8e704712@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).