On Wed, 4 Jul 2012 05:14:45 -0400, "Rod Pemberton"
<do_not_h...@notemailnot.cmm> wrote:<snip FORTH part>
> What a specification actually *requires* and what is *meant* can be twoI'm not sure what you include in C's 'parsing procedures'.
> different things. Part of the reason I asked was because the C
> specification doesn't specify or require "parse in place" for it's parsing
> procedures, although that's what's meant. However, if you *don't* implement
> those C procedures by parsing the words in their original location, i.e.,
> using an intermediate buffer, some C code breaks. I.e., some C programmers
> assume or use that "feature". So, the C specification fails to capture all
> of the required information necessary to correctly implement parsing
> procedures. Historically, that was the way C's did it. So, I suspected ANS
> Forth was the same way. Specifications are usually an abstraction, i.e.,
> all the foundation is missing or intracacies are abstracted away.
strtok definitely parses in place -- the standard talks explicitly
atoi, atof, strtol, strtod, etc. are specified as 'conversions',
sscanf does certain limited kinds of parsing, but the only way a
strchr, strspn, etc. can be used as building blocks for parsing,
Is there anything else?
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.