> Rod Pemberton <do_not_h...@notemailnotz.cnm> wrote:
>> "Hugh Aguilar" <hughaguila...@yahoo.com> wrote in message
>> news:45d4f07b-8d85-43e7-acc9-614966bdae14@uk1g2000pbb.googlegroups.com...
>>> On Nov 6, 6:53 pm, "Rod Pemberton" <do_not_h...@notemailnotz.cnm>
>>> wrote:

>>>> What about a word like COUNT ?

>>>> COUNT ( addr -- addr len )

>>> This is the stack picture for COUNT :

>>> : count ( adr1 -- adr2 len )

>>> COUNT does consume adr1 --- and then it gives you back
>>> some other data

>> That's a matter of interpretation.  len is definately different.

>>> (adr2 is not the same datum as adr1).

>> False.  "adr2 is" _typically_ "not the same datum as adr1", but can be.

>> There is no requirement that adr2 be different from adr1.

> Of course there is, because the count is at c-addr1, and c-addr2 is
> the start of the string:

> 6.1.0980 COUNT
> CORE

>          ( c-addr1 -- c-addr2 u )

> Return the character string specification for the counted string
> stored at c-addr1. c-addr2 is the address of the first character after
> c-addr1. u is the contents of the character at c-addr1, which is the
> length in characters of the string at c-addr2.

>> There is only a requirement that COUNT returns an address to the
>> start of the string.  Historically, since counted strings are used
>> in Forth, where the count precedes the string, they are different.
>> But, if no count precedes the string, they'll be the same.

> The count precedes the string, as COUNT's glossary entry makes clear.

> Andrew.