Re: Size-specific memory access words


Jeff M. wrote:
> > Now, we have C@/C! for characters (bytes)

> I could be wrong, but I don't believe there is anything in ANS to
> specify that C@ and C! are for fetching and storing /bytes/ per se,
> just the same as CHARS doesn't have to be a NOP. If the Forth system
> were built for unicode, they could very well return 16-bit values (and
> CHARS be 2*).

feel free to read that (e.g., bytes) rather than (ie., bytes). Bernd
does specify a little further down, "where B@/! is an alias to C@/! on
64 bit Gforth" ...

.

Relevant Pages

  • Re: Size-specific memory access words
    ... for characters ... but I don't believe there is anything in ANS to ... specify that C@ and C! ... just the same as CHARS doesn't have to be a NOP. ...
    (comp.lang.forth)
  • Re: unix filename restriction
    ... underscore _ and the dot. ... You could use other characters, ... never met a *human* defined path of more than 80 chars (most of the ... If you want to be very sure, limit your filename to the DOS limit of 8 ...
    (comp.os.linux.development.apps)
  • Re: Predefined Cell Character Length
    ... =LEFTreturns up to 10 characters. ... If 3 chars in a cell just those 3 will be returned. ... Gord Dibben MS Excel MVP ... cells in clumn A can only be 10 characters at the most, ...
    (microsoft.public.excel.worksheet.functions)
  • Re: 128 bit password
    ... Joe Richards Microsoft MVP Windows Server Directory Services ... Assumption would be that it would get truncated at 127/128 characters... ... then these are 16 bit chars. ...
    (microsoft.public.security)
  • What is the exact meaning of Octal Sequences ooo-ooo in tr utility of UNIX03 Specification
    ... Octal sequences can be used to represent characters with specific coded ... The characters or collating elements in the range shall be ... specify multi-byte characters. ...
    (comp.unix.shell)