Category:J: Difference between revisions
Content added Content deleted
m (fix types typo) |
|||
Line 82: | Line 82: | ||
For example, if language did not have an internal stack, a word's definition could not be used during the execution of that word. All current J implementations support recursion, but in some sense this is a convenience, and it's reasonable to imagine J implementations which do not (perhaps in a "compile to silicon" implementation). |
For example, if language did not have an internal stack, a word's definition could not be used during the execution of that word. All current J implementations support recursion, but in some sense this is a convenience, and it's reasonable to imagine J implementations which do not (perhaps in a "compile to silicon" implementation). |
||
=== Types == |
=== Types === |
||
Perhaps also worth noting is that when thinking about J programs, it can be convenient to think of an instance of an array as a type. This is somewhat different from the usual treatment of type (where all potential values in a context are treated as a type). |
Perhaps also worth noting is that when thinking about J programs, it can be convenient to think of an instance of an array as a type. This is somewhat different from the usual treatment of type (where all potential values in a context are treated as a type). |