public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@redhat.com>
To: "Игорь Пашев" <pashev.igor@gmail.com>
Cc: libc-ports@sourceware.org
Subject: Re: bufsplit equivalent
Date: Thu, 16 May 2013 22:23:00 -0000	[thread overview]
Message-ID: <51955C41.6000605@redhat.com> (raw)
In-Reply-To: <CALL-Q8y_6_QYxarP=2xusr5tbnnTNf19CqvMNpCfUFY8=9KV2g@mail.gmail.com>

On 05/16/2013 06:04 PM, Игорь Пашев wrote:
> Hi, all!
> 
> Is there an equivalent of bufsplit() function in glibc?
> 
> bufsplit– split buffer into fields:
> http://docs.oracle.com/cd/E19683-01/817-0679/6mgfb870d/index.html

Please email libc-help@sourcware.org for questions like this.

We don't have anything like bufsplit in glibc.

Given that it's not in POSIX or ISO C, and it appears to have
very limited appeal, we are unlikely to add it to the library.

Cheers,
Carlos.
 

      reply	other threads:[~2013-05-16 22:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 22:05 Игорь Пашев
2013-05-16 22:23 ` Carlos O'Donell [this message]

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=51955C41.6000605@redhat.com \
    --to=carlos@redhat.com \
    --cc=libc-ports@sourceware.org \
    --cc=pashev.igor@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).