Skip to main content
Code Golf

Return to Answer

added 192 characters in body
Source Link
Bubbler
Bubbler
  • 78.4k
  • 52
  • 61

"input" and "output"

Any of these are acceptable for input/output respectivelyRefer to Default for Code Golf: Input/Output methods. The list includes, but not is limited to:

  • STDIN/STDOUT
  • function argument/return value
  • command line arguments/program exit code
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Refer to Default for Code Golf: Input/Output methods. The list includes, but not is limited to:

  • STDIN/STDOUT
  • function argument/return value
  • command line arguments/program exit code
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)
Defaults change.
Source Link
S.S. Anne
S.S. Anne
  • 3.3k
  • 5
  • 13

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value (within a complete program)
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value (within a complete program)
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)
added 28 characters in body
Source Link
Doorknob
Doorknob
  • 71.7k
  • 2
  • 63
  • 134

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value (within a complete program)
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)

"input" and "output"

Any of these are acceptable for input/output respectively:

  • STDIN/STDOUT
  • function argument/return value (within a complete program)
  • reading from/writing to a file
  • dialog boxes
  • popping from/pushing to the stack (for stack-based languages like GolfScript; this is essentially the equivalent of a function's arguments/return values for those languages)
Source Link
Doorknob
Doorknob
  • 71.7k
  • 2
  • 63
  • 134