typo
Source Link
Adám
  • 26.2k
  • 39
  • 73

Dfn functions and Dop operators are one or more lines of code where the first line begins with { and the last ends with }, and they refer to their right and optional left arguments as and . Dops additionally refer to their refer to their left and optional right operands as ⍺⍺ and ⍵⍵. The first expression which is not an assignment will terminate the function, returning the result of that expression. They may otherwise do additional I/O in the manner of tradfn programs (see above). On TIO, the entire dfn/dop (including braces) goes in the Code field, and the first line must be preceded by a name and , e.g. MyFn←. The name and should not be counted into the submission length. In the Input field, the first line must have the function/operators's name to call it, followed and optionally preceded by arguments and, for operators, operands, and lines immediately after that will be the lines of additional input, if any.

Dfn functions and Dop operators are one or more lines of code where the first line begins with { and the last ends with }, and they refer to their right and optional left arguments as and . Dops additionally refer to their refer to their left and optional right operands as ⍺⍺ and ⍵⍵. The first expression which is not an assignment will terminate the function, returning the result of that expression. They may otherwise do additional I/O in the manner of tradfn programs (see above). On TIO, the entire dfn/dop (including braces) goes in the Code field, and the first line must be preceded by a name and , e.g. MyFn←. The name and should not be counted into the submission length. In the Input field, the first line must have the function/operators's name to call it, followed and optionally preceded by arguments and, for operators, operands, and lines immediately after that will be the lines of additional input, if any.

Dfn functions and Dop operators are one or more lines of code where the first line begins with { and the last ends with }, and they refer to their right and optional left arguments as and . Dops additionally refer to their left and optional right operands as ⍺⍺ and ⍵⍵. The first expression which is not an assignment will terminate the function, returning the result of that expression. They may otherwise do additional I/O in the manner of tradfn programs (see above). On TIO, the entire dfn/dop (including braces) goes in the Code field, and the first line must be preceded by a name and , e.g. MyFn←. The name and should not be counted into the submission length. In the Input field, the first line must have the function/operators's name to call it, followed and optionally preceded by arguments and, for operators, operands, and lines immediately after that will be the lines of additional input, if any.

SBCS
Source Link
Adám
  • 26.2k
  • 39
  • 73

Three primitives (built-ins) added in each of versions 14.0 (, , and ) and 16.0 (, , and ) are not included inThree primitives (built-ins) added in each of versions 14.0 (, , and ) and 16.0 (, , and ) are not included in the code page, and may therefore not be used in 1 byte per character submissions without counting each as its shortest multi-character alternative:
⎕U2338⎕U2364⎕OPT
⎕U2286⎕U233A⎕U2378
Also, remember that these longer names need to be followed by a space if the next character is alphanumeric. Note that the dyadic form of can be reached by setting ⎕ML←3 and using instead, however, you must account for all other changes due to ⎕ML changing.
You can now use all the code page, and may therefore not be used in 1 byte per character submissions without counting each as its shortest multibuilt-character alternative:
⎕U2338⎕U2364⎕OPT
⎕U2286⎕U233A⎕U2378
Also, remember that these longer names need to be followedins by a space if the next character is alphanumeric. Note that the dyadic formclaiming use of can be reached by setting ⎕ML←3 and using instead, however, you must account for all other changes due to ⎕ML changingSBCS.

Three primitives (built-ins) added in each of versions 14.0 (, , and ) and 16.0 (, , and ) are not included in the code page, and may therefore not be used in 1 byte per character submissions without counting each as its shortest multi-character alternative:
⎕U2338⎕U2364⎕OPT
⎕U2286⎕U233A⎕U2378
Also, remember that these longer names need to be followed by a space if the next character is alphanumeric. Note that the dyadic form of can be reached by setting ⎕ML←3 and using instead, however, you must account for all other changes due to ⎕ML changing.

Three primitives (built-ins) added in each of versions 14.0 (, , and ) and 16.0 (, , and ) are not included in the code page, and may therefore not be used in 1 byte per character submissions without counting each as its shortest multi-character alternative:
⎕U2338⎕U2364⎕OPT
⎕U2286⎕U233A⎕U2378
Also, remember that these longer names need to be followed by a space if the next character is alphanumeric. Note that the dyadic form of can be reached by setting ⎕ML←3 and using instead, however, you must account for all other changes due to ⎕ML changing.
You can now use all the built-ins by claiming use of SBCS.

libraries and helper code
Source Link
Adám
  • 26.2k
  • 39
  • 73

A function submission may include helper code outside the function, for example

⎕CY'dfns'⋄N←NormRand
f← ...

A function submission may include helper code outside the function, for example

⎕CY'dfns'⋄N←NormRand
f← ...
added 62 characters in body
Source Link
Adám
  • 26.2k
  • 39
  • 73
Loading
Source Link
Adám
  • 26.2k
  • 39
  • 73
Loading
Post Made Community Wiki by Adám