From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] csipinfo
Date: Thu, 19 Oct 2006 09:29:41 +0100 [thread overview]
Message-ID: <1a22bd77975b0037bb99c22b0ff96f76@terzarima.net> (raw)
In-Reply-To: <99c53c1560bbfb05dd10f07176bb441a@terzarima.net>
>sorry, i meant: see getfields, tokenize, etc. instead of strtok
i ought to have included an explanation, but i was short of time.
the biggest problem is that strtok keeps some hidden
state between calls, so it's a nuisance in concurrent programming.
i usually find having the result as an array of strings more
helpful than having to make several calls, as well.
probably POSIX has fixed the concurrency problem by implying thread-local
storage for strtok's state (thus creating a different problem elsewhere)
tokenize is often useful because it handles quoting,
which is useful for space-separated fields that need to be able to contain white space.
next prev parent reply other threads:[~2006-10-19 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61d9157e8f6994d999d7f257cd2b05b4@coraid.com>
2006-10-18 18:44 ` Joel “chesky” Salomon
2006-10-18 19:14 ` rog
2006-10-18 19:26 ` erik quanstrom
2006-10-18 19:38 ` Joel “chesky” Salomon
2006-10-18 19:57 ` C H Forsyth
2006-10-18 23:51 ` Charles Forsyth
2006-10-19 8:29 ` Charles Forsyth [this message]
2006-10-18 20:17 ` Joel “chesky” Salomon
2006-10-18 21:29 ` geoff
2006-10-18 19:56 ` Charles Forsyth
2006-10-18 19:59 ` erik quanstrom
2006-10-18 20:15 ` rog
2006-10-18 19:30 ` erik quanstrom
2006-10-18 3:10 Joel “chesky” Salomon
2006-10-18 3:36 ` geoff
2006-10-18 5:20 ` Joel “chesky” Salomon
2006-10-18 5:37 ` geoff
2006-10-18 5:53 ` Joel “chesky” Salomon
2006-10-18 12:38 ` Joel “chesky” Salomon
2006-10-18 15:32 ` Russ Cox
2006-10-18 16:43 ` Joel Salomon
2006-10-18 16:59 ` rog
2006-10-18 20:38 ` andrey mirtchovski
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=1a22bd77975b0037bb99c22b0ff96f76@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).