Comments: Difference between revisions

403 bytes added ,  18 days ago
m
Remove FutureBasic apostrophe single line comment as it's deprecated
(Add bruijn)
m (Remove FutureBasic apostrophe single line comment as it's deprecated)
 
(4 intermediate revisions by 3 users not shown)
Line 734:
<syntaxhighlight lang="lisp">(+ 1 (comment "foo") 3) ;; Throws an exception, because it tries to add nil to an integer
(+ 1 #_"foo" 3) ;; Returns 4</syntaxhighlight>
 
=={{header|CMake}}==
 
Line comments use the common <code>#</code> syntax:
 
<syntaxhighlight lang="cmake"># A single-line comment</syntaxhighlight>
 
Multi-line comments use a Lua-like square-bracket syntax.
 
<syntaxhighlight lang="cmake">
#[[A multi-line
comment ]]
' Single#[==[A multi-line comment
with [[nested brackets]]. ]==]</syntaxhighlight>
 
The number of equals signs (<code>=</code>) in the opening bracket determines the number expected in the closing bracket.
 
=={{header|COBOL}}==
Line 1,128 ⟶ 1,144:
# and last until the end of the line
</syntaxhighlight>
 
=={{header|Fennel}}==
<syntaxhighlight lang="fennel">; This is a single-line comment</syntaxhighlight>
 
=={{header|Fermat}}==
Line 1,249 ⟶ 1,268:
<syntaxhighlight lang="futurebasic">
// Single line comment
' Single line comment
rem Single line comment
/* Single line comment */
Line 1,699 ⟶ 1,717:
</syntaxhighlight>
 
As of 0.6.11, commentsComments allow characters designated as "Graphic" by Unicode, Spaces, and Private Use Area code points. Also, certain invisible "spaces," to make it easier to paste in international text (see langurlang.org). The idea around the "allowed" characters is to keep source code from having hidden text or codes and to allay confusion and deception.
 
=={{header|Lasso}}==
408

edits