Naming conventions: Difference between revisions
Content added Content deleted
Tag: Undo |
(add bqn) |
||
| Line 282: | Line 282: | ||
If the first line of the program is a comment line of the form <tt>REM >myprog</tt>, the <tt>SAVE</tt> command can be used with no filename and the program will be saved as (in this case) <tt>myprog</tt>. Otherwise, it would be necessary to use <tt>SAVE "myprog"</tt>. |
If the first line of the program is a comment line of the form <tt>REM >myprog</tt>, the <tt>SAVE</tt> command can be used with no filename and the program will be saved as (in this case) <tt>myprog</tt>. Otherwise, it would be necessary to use <tt>SAVE "myprog"</tt>. |
||
=={{header|BQN}}== |
|||
BQN uses a context-free grammar, a result of which it has explicit naming conventions defined in its interpreter. The basic types of values can be distinguished by their first and last characters as follows: |
|||
<syntaxhighlight lang="bqn"># Subjects (arrays, numbers, characters, etc) start with a lowercase letter: |
|||
var←3 |
|||
arr←⟨1,2⟩ |
|||
# Functions start with an uppercase letter: |
|||
Fun←{𝕨+𝕩} |
|||
Avg←+´÷≠ |
|||
# 1-modifiers start with an underscore and do not end with an underscore: |
|||
_mod←{𝔽𝕩} |
|||
# 2-modifiers must start and end with an underscore: |
|||
_2mod_←{𝔾𝕨𝔽𝕩}</syntaxhighlight> |
|||
=={{header|C}}== |
=={{header|C}}== |
||