public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mike Mason <mmlnx@us.ibm.com>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: systemtap@sourceware.org
Subject: Re: Mistake in man on tokenize
Date: Thu, 11 Oct 2007 15:16:00 -0000	[thread overview]
Message-ID: <470E3E39.50007@us.ibm.com> (raw)
In-Reply-To: <02c601c80bd8$e93a4250$85697c0a@guest004>

Good catch.  I'll update the man page.  I need to make some other changes anyway, plus I need to update the Language Reference.

Regards,
Mike

Zhaolei wrote:
> Hi, everyone
> 
> In man stapfuncs, tokenize is explained as following:
>   tokenize:string (str:string, delim:string)
>     Given a string and a token delimiter, return the next token in the
>     string. If str is non-NULL, returns the first token. If str is NULL,
>     returns the next token in the str passed in the previous call to
>     tokenize(). Only the first character in delim is used as the delimiter.
>     Returns NULL when no more tokens are left.
> 
> But I found if delimiter includes more than 1 chars, Not only the first
>  character, but also all of characters will used as the delimiter.
> So I think it is necessary to update man as following:
> 
> - Only the first character in delim is used as the delimiter.
> + Each character in delim is taken as a delimiting character.
> 
> If no objection, I will commit it.
> 
> Regards
> Zhaolei
> 

  reply	other threads:[~2007-10-11 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09  5:08 [patch] Close fds before execute a cmd Lai Jiangshan
2007-10-09  5:37 ` Stone, Joshua I
2007-10-09  7:51 ` Is it necessary to add _qs_update before qsq_utilization(and etc.) Zhaolei
2007-10-11  7:32   ` Mistake in man on tokenize Zhaolei
2007-10-11 15:16     ` Mike Mason [this message]
2007-10-09 16:12 ` [patch] Close fds before execute a cmd Martin Hunt

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=470E3E39.50007@us.ibm.com \
    --to=mmlnx@us.ibm.com \
    --cc=systemtap@sourceware.org \
    --cc=zhaolei@cn.fujitsu.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).