9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "有澤 健治" <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Brdline and the last line
Date: Thu, 10 Oct 2013 12:46:03 +0900	[thread overview]
Message-ID: <9BDABDE6-950E-4532-B895-ED2115DD2F4E@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <25ea711db6f83d26ca16faf38466bdcc@ladd.quanstro.net>

Hello,

If speed is matter, try rdline() in Kirara.
http://plan9.aichi-u.ac.jp/netlib/kirara/kirara-1.2a.tgz

More improved version will be included in kirara-2.0 (to be released).

On 2013/10/10, at 1:04, erik quanstrom wrote:

> On Wed Oct  9 11:54:41 EDT 2013, steve@quintile.net wrote:
>> Hi all
>>
>> It has long been an irritation that Brdline returns failure (to match the
>> end of line token) at end of file if the file does not end with a newline.
>>
>> This is correct but annoying.
>>
>> does anyone had a neat snippet of code which ensures we parse the
>> last line correctly?
>>
>> For files on the filesystem I just fix them, but I am wrapping Brdline
>> around a tcp connection so I am not in control of how people terminate
>> their files...
>
> how about
>
> int
> brdline(Biobuf *b, char *buf, int nbuf)
> {
> 	int i, rv;
> 	Rune r;
>
> 	for(i = 0; i < nbuf - UTFmax - 1; ){
> 		rv = Bgetrune(b);
> 		if(rv == -1 || rv == '\n')
> 			break;
> 		r = rv;
> 		i += chartorune(&r, buf+i);
> 	}
> 	buf[i] = 0;
> 	return i;
> }
>
> - erik
>




  reply	other threads:[~2013-10-10  3:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 15:53 Steve Simon
2013-10-09 16:04 ` erik quanstrom
2013-10-10  3:46   ` 有澤 健治 [this message]
2014-05-27  3:49 ` 有澤 健治

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=9BDABDE6-950E-4532-B895-ED2115DD2F4E@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --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).