Re: strtok ( ) help
- From: "rayw" <ray.webster@xxxxxxxxx>
- Date: Sat, 21 Jan 2006 03:41:32 GMT
w00t
:-)
--
===============================================================
In an attempt to reduce ?unwanted noise? on the ?signal? ...
Disclaimer:
Any comment/code I contribute might =NOT= be 100% portable, nor
semantically correct [read - ?not 100% pedantically correct?].
I don?t care too much about that though, and I reckon it?s the
same with most ?visitors? here. However, rest assured that any
?essential? (?) corrections WILL almost certainly appear v.soon
[read - ?to add noise as they see fit, *a pedant* will be along
shortly?].
WARNINGS: Always read the label. No beside-the-point minutiae
filter supplied. Keep away from children. Do not ignite.
===============================================================
"pemo" <usenetmeister@xxxxxxxxx> wrote in message
news:dqs3bo$p61$1@xxxxxxxxxxxxxxxx
> Default User wrote:
>> pemo wrote:
>>
>>
>>> Now, it's late [here] and I've not bothered to parse all the previous
>>> paras in the std to see if there's a case for categorically stating
>>> that 'token', in this context, is necessaraily a member of the set of
>>> things in the set of inputs to strtok(). But, if there's not a case,
>>> then "returns a pointer to the first character of a token" doesn't, I
>>> think, preclude strtok returning a pointer into some local [or any
>>> other] buffer, rather than the one encoding the original string [the
>>> input] ... just that [perhaps], at the time, the semantics of what
>>> token it is pointing to tallys with what its input is?
>>
>> What's unclear about this?
>>
>> A sequence of calls to the strtok function breaks the
>> string pointed to by s1 into a sequence of tokens, each of
>> which is delimited by a character from the string pointed to
>> by s2.
>>
>> "Breaks the string". Not forms some copies. Read how tokens are found
>> and formed. It pretty well lays out the state machine for you.
>
> Ho && Hum
>
> --
> ===============================================================
> In an attempt to reduce ?unwanted noise? on the ?signal? ...
>
> Disclaimer:
>
> Any comment/code I contribute might =NOT= be 100% portable, nor
> semantically correct [read - ?not 100% pedantically correct?].
> I don?t care too much about that though, and I reckon it?s the
> same with most ?visitors? here. However, rest assured that any
> ?essential? (?) corrections WILL almost certainly appear v.soon
> [read - ?to add noise as they see fit, *a pedant* will be along
> shortly?].
>
> WARNINGS: Always read the label. No beside-the-point minutiae
> filter supplied. Keep away from children. Do not ignite.
> ===============================================================
>
>
.
- References:
- strtok ( ) help
- From: ern
- Re: strtok ( ) help
- From: pemo
- Re: strtok ( ) help
- From: Default User
- Re: strtok ( ) help
- From: pemo
- Re: strtok ( ) help
- From: Default User
- Re: strtok ( ) help
- From: pemo
- Re: strtok ( ) help
- From: Default User
- Re: strtok ( ) help
- From: pemo
- strtok ( ) help
- Prev by Date: Re: C programme
- Next by Date: Re: C programme
- Previous by thread: Re: strtok ( ) help
- Next by thread: Re: strtok ( ) help
- Index(es):
Relevant Pages
|