Pragmatic directives: Difference between revisions
Content added Content deleted
(Add NetRexx implementation) |
|||
| Line 257: | Line 257: | ||
['nested_scopes', 'generators', 'division', 'absolute_import', 'with_statement', 'print_function', 'unicode_literals'] |
['nested_scopes', 'generators', 'division', 'absolute_import', 'with_statement', 'print_function', 'unicode_literals'] |
||
>>> </lang> |
>>> </lang> |
||
=={{header|Racket}}== |
|||
Racket eschews pragmas that are specified outside of the language. However, one can view Racket's <tt>#lang</tt> mechanism as a much more powerful tool for achieving similar things. For example, normal code starts with <tt>#lang racket</tt> -- giving you a very Scheme-like language; change it to <tt>#lang typed/racket</tt> and you get a similar language that is statically typed; use <tt>#lang lazy</tt> and you get a Racket-like language that has lazy semantics; use <tt>#lang algol60</tt> and you get something that is very different than Racket. (And of course, you can implement your own language quite easily.) |
|||
=={{header|Tcl}}== |
=={{header|Tcl}}== |
||