Host introspection: Difference between revisions
Content added Content deleted
No edit summary |
|||
| Line 4: | Line 4: | ||
=={{header|Forth}}== |
=={{header|Forth}}== |
||
: endian |
|||
cr 1 cells . ." bytes per cell" |
|||
cr 1 cells . ." address units per cell" |
|||
s" ADDRESS-UNIT-BITS" environment? if cr . ." bits per address unit" then |
|||
cr 1 here ! here c@ if ." little" else ." big" then ." endian" ; |
|||
This relies on '''c@''' being a byte fetch (4 chars = 1 cells). Although it is on most architectures, ANS Forth only guarantees that 1 chars <= 1 cells. Some Forths like OpenFirmware have explicitly sized fetches, like b@. |
This relies on '''c@''' being a byte fetch (4 chars = 1 cells). Although it is on most architectures, ANS Forth only guarantees that 1 chars <= 1 cells. Some Forths like OpenFirmware have explicitly sized fetches, like b@. |
||
Revision as of 23:49, 10 October 2008
You are encouraged to solve this task according to the task description, using any language you may know.
Print the word size and endianness of the host machine.
Forth
: endian cr 1 cells . ." address units per cell" s" ADDRESS-UNIT-BITS" environment? if cr . ." bits per address unit" then cr 1 here ! here c@ if ." little" else ." big" then ." endian" ;
This relies on c@ being a byte fetch (4 chars = 1 cells). Although it is on most architectures, ANS Forth only guarantees that 1 chars <= 1 cells. Some Forths like OpenFirmware have explicitly sized fetches, like b@.
J
":&> (|: 32 64 ;"0 big`little) {"_1~ 2 2 #: 16b_e0 + a. i. 0 { 3!:1 ''
32
little