Comments: Difference between revisions

 

=={{header|11l}}==

\\ Also single line comment (continuation of the comment in previous line)

 

 

\‘ And

 

=={{header|360 Assembly}}==

* An asterisk in column one denotes a comment line

* Comments may also follow any syntactically complete instruction:

* Comments after instructions with omitted operands require a comma ","

END , Comment (without comma, "Comment" assumed an operand of "END")

 

=={{header|4D}}==

 

=={{header|6502 Assembly}}==

Note: syntax depends on the assembler software but use of a semicolon is fairly standard

 

=={{header|68000 Assembly}}==

 

EASy68k uses * as the comment character. VASM uses a semicolon ;

 

=={{header|8086 Assembly}}==

Note: syntax depends on the assembler software but use of a semicolon is fairly standard

 

=={{header|AArch64 Assembly}}==

{{works with|as|Raspberry Pi 3B version Buster 64 bits}}

/* ARM assembly AARCH64 Raspberry PI 3B */

/* comments multi lines

 

// comment end of ligne

=={{header|ACL2}}==

Just like Common Lisp:

#| Multi-line

 

=={{header|Action!}}==

Action! supports only single line comments which begin with semicolon.

 

PROC Main() ;This is a comment as well

{{out}}

[https://gitlab.com/amarok8bit/action-rosetta-code/-/raw/master/images/Comments.png Screenshot from Atari 8-bit computer]

 

=={{header|Ada}}==

 

=={{header|Agena}}==

Agena has single line comments and two styles of multi-line comments.

 

#/ multi-line comment

/* multi-line comment - C-style

- ends with the "* followed by /" terminator on the next line

 

=={{header|ALGOL 60}}==

A comment in ALGOL 60 takes the place of a single instruction.

'COMMENT' this is a first comment;

'COMMENT'

****** this is a second comment ******

;

 

=={{header|ALGOL 68}}==

===With Extensions===

£ This is a hash/pound comment for a UK keyboard £

 

=={{header|ALGOL W}}==

A single word in the form of an identifier following the reserved word 'end' is also a comment.

 

comment a comment;

% another comment

another

%

 

=={{header|AmigaE}}==

are like C ... */

 

=={{header|AntLang}}==

 

=={{header|Apex}}==

System.debug ('I will execute'); // This comment is ignored.

/*

I am a large comment, completely ignored as well.

*/

 

=={{header|APL}}==

 

=={{header|AppleScript}}==

--This is a single line comment

 

(* Nested block comment *)

*)

 

{{works with|AppleScript|2.0}}

 

=={{header|Arendelle}}==

{{works with|as|Raspberry Pi}}

 

/* ARM assembly Raspberry PI comment one line */

/* comment line 1

mov r1,#0 // authorized comment

 

 

=={{header|Arturo}}==

 

a: 10 ; another single-line comment

 

; Now, this is a

 

=={{header|Asymptote}}==

 

See [http://asymptote.sourceforge.net/doc/Programming.html programming introduction in the Asymptote manual].

 

=={{header|AutoHotkey}}==

/*

multiline comment1

multiline comment2

 

For multi-line comments, the '''/*''' and '''*/''' '''must''' be on their own separate lines. Nothing else can be on the same line.

=={{header|AutoIt}}==

 

#cs

Everything between the cs and and the ce is commented.

#ce

;individual lines after a semicolon are commented.

 

=={{header|AWK}}==

The ''hash'' symbol # start a comment; it ends at the end of line.

 

# do something

 

=={{header|Axe}}==

 

 

This is a multi-line comment

 

This is a comment only if the condition evaluates to zero

 

This is a comment only if the condition evaluates to nonzero

 

This is a comment only if the previous conditional comment was executed (and vice versa)

 

=={{header|Babel}}==

-- This is a line-comment

 

 

dedent: 0x42 -- The comment block above is now closed

 

=={{header|BASIC}}==

{{works with|GW-BASIC}}

{{works with|ZX Spectrum Basic}}

The only truly standard method of marking a comment in BASIC is using the <code>REM</code> keyword. This dates back to (at least) the late 1970's, and ''should'' work with most BASICs available today:

 

 

{{works with|Applesoft BASIC}}

{{works with|QBasic|1.1}}

{{works with|QuickBASIC|4.5}}

Most BASICs also support alternate comment characters,

commonly an apostrophe (single quote):

 

 

{{works with|DarkBASIC}}

==={{header|Applesoft BASIC}}===

Comment by making a REMark using the REM keyword

When LISTing the program a space is added after the REM keyword

The remark extends until the end of the line. Only the first THIS IS CODE is printed.

A comment can come after a GOSUB and when the subroutine returns it continues running the statements after the GOSUB comment.

Anything after a GOTO or RETURN statement is ignored.

There are other ways to add spacing and comments to code.

40 REM

50 :

70 FOR I = 1 to 10

80 ::::PRINT I;MID$("THIS IS A COMMENT",1,0)

Typing CONTinue after the program ENDs will result in a ?SYNTAX ERROR.

Use the quotation symbol " before the comment so that spaces are included and keywords are ignored.

==={{header|BaCon}}===

BaCon accepts '''REM''' (or single quote apostrophe) for line comments.

 

==={{header|BASIC256}}===

# and this is too

 

==={{header|IS-BASIC}}===

 

==={{header|True BASIC}}===

 

==={{header|Yabasic}}===

# the hash-sign too (at beginning of line)

// even the double slash

print "Not a comment":// But this is again a valid comment

print "Not a comment" // even this.

 

=={{header|Batch File}}==

 

There is another (undocumented) option, using a double-colon <code>::</code>. However, this has issues with some syntactic constructs and therefore may raise syntax errors.

 

Yet another (undocumented) option, using (not delayed) variable expansion as long as it is undefined. This works because undefined variables result to blank line when expanded using <code>%</code>.

Since comment lines are skipped entirely by the parser, multi-line comments aren't possible even with line continuation.

 

=={{header|BBC BASIC}}==

 

=={{header|bc}}==

 

2 + /* Comment between tokens. */ 3

* of the comment are only for style. You must not nest a comment

* inside another comment; the first asterisk-slash ends the comment.

 

----

{{works with|OpenBSD bc}}

 

 

# This form of comment is an extension, not part of standard bc.

 

a = 1 # The newline is not part of the comment.

 

=={{header|Befunge}}==

 

{{works with|Befunge|93}}

 

{{works with|Befunge|98}}

^- inline comments -^ <-^- other comments

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;completely isolated comment block for the paranoid;

;(almost - you can still skip into it.) ;

 

=={{header|Blast}}==

 

 

=={{header|BQN}}==

 

=={{header|Bracmat}}==

 

=={{header|Brainf***}}==

 

Most ASCII characters may be used for comments; only the eight characters "+-<>[],." are Brainf*** commands. Extra care must be used when using punctuation, particularly the comma or period. These are I/O operators and are actually commands rather than comments, and are instead compiled into the program if used and may have to be "debugged" and removed if you forget this issue. Another workaround for this issue is to tactically place the comment inside a "[]" loop which can never be entered (The loop will only be encountered when the active memory cell value is 0).

 

=={{header|Brat}}==

 

#* Multi

Line

 

=={{header|Brlcad}}==

 

# Comments in mget scripts are prefixed with a hash symbol

ls # comments may appear at the end of a line

 

=={{header|Burlesque}}==

Burlesque does NOT have comments. However, you can comment code by pushing a string and popping it immediately.

 

"I'm sort of a comment"vv

 

Since strings are multi-line strings:

 

"I'm a

very long comment spanning

over several lines"vv

 

=={{header|C}}==

/* So is this

multiline comment.

The comment starts at the <tt>/*</tt>, and ends at the <tt>*/</tt>. A comment may be used between any tokens. It cannot be used inside tokens, that is, given the code

the function takes an argument of type char, named isma, not an unnamed argument of type charisma.

 

Comments cannot be nested; that is, if you write

the comment ends at the first <tt>*/</tt>, and <tt>inside */</tt> is again interpreted as source code (almost certainly causing a compile error). Some compilers have the option to allow nested comments, but this is not a standard feature.

 

Conditional compilation also can be used to make the compiler ignore some text:

While technically not a comment, this is also ignored by the compiler

The trick is that 0 is always false, therefore the text between <tt>#if 0</tt> and <tt>#endif</tt> is never compiled. While this should never be used for actual comments, it's an easy way to comment out some code, especially because it doesn't interfere with normal (documentation) comments.

 

Conditional compile "comments" can be nested:

This is not compiled.

#if 0

#endif

And this still is not compiled.

 

{{works with|ANSI}}

 

Even though the compiler doesn't see '''#if 0''' text, the preprocessor does. Therefore some minimal rules still have to be followed. For example, the following code is ''not'' valid:

This isn't valid.

That's because the preprocessor will interpret the apostrophe as beginning of a character constant, and will complain because that character constant isn't terminated with another apostrophe.

 

 

{{works with|C99}}

 

=={{header|C sharp|C#}}==

 

//This is other comment.

 

/* This is a

multi-line

 

=={{header|C++}}==

 

Single line C++-style comments

C++-style comments start with <tt>//</tt> and reach up to, but not including, the end of line (more exactly, up to the next unescaped newline). While formally, C++-style comments cannot be nested either, in practice they can:

That's because starting with the first <tt>//</tt> everything in the line is ignored, including the second <tt>//</tt>.

The fact that the newline is ''not'' part of the comment is important for multi-line macro definitions. It means that in the code

(macro text) // comment

the line <tt>(no more macro text)</tt> is ''not'' part of the macro definition. Also escaping the line break at the end of the comment with '\' doesn't help, because that would make the third line part of the ''comment'' instead. Comments inside macros therefore have to be C-style.

 

=={{header|Chapel}}==

 

/* multi

 

=={{header|Chef}}==

 

This is a comment.

Methods.

SingleWordCommentTwo until SingleWordCommentOned.

 

=={{header|ChucK}}==

<-- Not common

// Usual comment

 

=={{header|Clean}}==

Clean comments are similar to C++.

In contrast to C++ comments can be nested.

 

=={{header|Clojure}}==

Anything from a semicolon to the end of a line is a comment.

 

(defn foo []

 

The <code>(comment)</code> macro will prevent a form from being evaluated, returning <code>nil</code> no matter what is contained in the comment. However the forms inside the <code>comment</code> form must be properly parseable (parentheses balanced, etc.) or an exception will be thrown.

 

 

Finally, the <code>#_</code> reader macro will cause a form to be ignored by the reader. Unlike <code>(comment)</code>, this does not return <code>nil</code>; the surrounding code is evaluated as though the ignored form isn't even there.

 

 

=={{header|COBOL}}==

=== Fixed format ===

A D in the 7th column indicates a debugging line which is treated like a comment unless a compiler flag is set.

 

=== Free format ===

 

{{works with|GnuCOBOL}}

This indicates a debugging line like above, but if it is used in fixed format files, it must be in the 8th column or beyond. ''Not necessarily.'' GnuCOBOL also supports D as an indicator in column 7, the >>D format works (more by trickery than spec) if the angle brackets start in column 5, the D ending up in column 7. The >>D debug marker can then be both fixed and free form compatible.

 

=== <code>NOTE</code> statement ===

{{works with|OS/VS COBOL}}

This statement causes everything following it up to the next separator period to be treated as a comment. This statement was deleted in COBOL-74.

commented out and ignored

 

=== <code>REMARKS</code> and other statements ===

There are quite a few <code>IDENTIFICATION DIVISION</code> obsolete and extension reserved words that will work in GnuCOBOL 2.

 

IDENTIFICATION DIVISION.

PROGRAM-ID. program.

DATE-COMPILED. same.

DATE-MODIFIED. this one is handy when auto-stamped by an editor.

 

=={{header|CoffeeScript}}==

 

### multi

line

 

=={{header|ColdFusion}}==

In tags:

<!--- This is a comment. Nothing in this tag can be seen by the end user.

Note the three-or-greater dashes to open and close the tag. --->

<!-- This is an HTML comment. Any HTML between the opening and closing of the tag will be ignored, but any ColdFusion code will still run.

 

In script:

 

=={{header|Common Lisp}}==

In a common convention, header comments are prefaced with four semicolons, top-level (function level) comments use three, comments for sections of code use two, and margin comments use one.

 

 

;;; The foo function calls bar on the first argument and multiplies the result by the second.

;;; The bar function simply adds 3 to the argument

(defun bar (n)

 

However, comments should not be used for inline documentation, as most defining constructs permit a documentation string (which is then available at runtime). <!-- It would be better to make the above example not do this, instead of showing bad style -->

 

"Add 3 to the argument."

(+ n 3))

(defclass button (widget)

(label action)

 

=={{header|Component Pascal}}==

(* Comments (* can nest *)

and they can span multiple lines.

*)

 

=={{header|Crystal}}==

 

# This is a doc comment. Any line *directly* above (no blank lines) a module, class, or method is considered a doc comment

# Doc comments are used to generate documentation with `crystal docs`

class Foo

 

=={{header|D}}==

// A single line comment.

 

Nestable documenttion comment.

+/

 

=={{header|Dart}}==

 

 

/* This is also a valid single line comment. Unlike the first one, this one terminates after one of these -> */

///

/// Formatting [variable] and [function] names like so allows dartdoc to link to the documentation for those entities.

 

=={{header|dc}}==

There is no comment syntax in POSIX dc. The convention is to make a string on the stack and move it to an unused register; a no-op.

GNU dc added the comment syntax of many other scripting languages.

 

=={{header|Delphi}}==

 

In addition to Pascal, Delphi also allows C++ style single line comments:

 

=={{header|Deluge}}==

Comments are only allowed in places such as "on load" scripts. You cannot put them in form or view definitions.

 

 

=={{header|Dragon}}==

 

This is

a multiple

line comment.

 

 

showln "Hello " /* This is an inline comment */ "world"

 

 

=={{header|DWScript}}==

It may extend across multiple lines. *)

 

are supported */

 

 

=={{header|Dyalect}}==

 

multi-line comment */

 

 

=={{header|Dylan}}==

 

/*

that spans multiple

lines

 

=={{header|Déjà Vu}}==

 

=={{header|E}}==

 

 

? "This is an Updoc comment, which

> is an executable example or test case.".split(" ")

# value: ["This", "is", "an", "Updoc", "comment,", "which

 

All comments span to the end of the line; there are no paired-delimiter comment syntaxes. “<code>#</code>” begins a comment anywhere outside of quotes; “<code>?</code>” and “<code>&gt;</code>” begin comments only if they are at the beginning of a line (except for whitespace), because those characters are also used for infix operators.

 

=={{header|EasyLang}}==

 

=={{header|EchoLisp}}==

666 ; this is an end-of-line comment

 

(info 'mynumber "👀 Symbols may be commented with an information string 👺")

(info 'mynumber) → displays the above inside the 'info' field.

 

=={{header|ECL}}==

 

Single-line comments must begin with //

 

Block comments must be delimited with /* and */

 

 

=={{header|EDSAC order code}}==

EDSAC programs were handwritten on "programme sheets" designed for the purpose. The programmer, or a computer operator, then copied the "orders" (instructions) to punched tape for input to the machine. Programme sheets had a column for "notes" (comments), but these were not copied to the tape.

Modern simulators, however, accept square brackets as comment delimiters.

[

And so

this

]

 

=={{header|EGL}}==

=={{header|Eiffel}}==

 

 

=={{header|Ela}}==

 

 

/*multiple line

 

=={{header|Elena}}==

 

/*multiple line

 

=={{header|Elixir}}==

Elixir does not have multiple line comments.

# single line comment

 

=={{header|Elm}}==

-- a single line comment

 

{- can be nested -}

-}

 

=={{header|Emacs Lisp}}==

A comment is started by <code>;</code> and reaches to the end of the line.

 

There are some coding conventions for <code>;;</code> align to indentation, <code>;;;</code> sections, etc,

 

Another way to add comments is to use strings at places where the result of an expression is ignored, since they simply evaluate to themselves without any effect. Note that strings can be multi-line:

Note that strings at the beginning of function definitions are interpreted as documentation strings for the function (i.e. Emacs will display them if asked for help about the function), e.g.

"This function subtracts its second argument from its first argument."

Due to this, it's debatable if the string at that place can be considered as comment.

 

=={{header|Erlang}}==

 

 

=={{header|ERRE}}==

! Standard ERRE comments begin with ! and extend to the end of the line

 

PRINT("this is code") ! comment after statement

 

=={{header|Euphoria}}==

Single line comment:

 

 

Multiline C-style comment:

This is a comment

{{works with|Euphoria|4.0.0}}

 

=={{header|F_Sharp|F#}}==

F# accepts C++ type line comments and OCaml type block comments

(* this comments a region

 

=={{header|Factor}}==

#! Or with "#! "

! and last until the end of the line

USE: multiline

/* The multiline vocabulary implements

 

=={{header|Falcon}}==

Falcon supports C-language style single line and block comments. A single line comment begins with two slashes (//) and ends at the end of the line. A block comment begins with a slash followed by an asterisk, and terminates when an asterisk followed by a slash is met (/*...*/).

/* Start comment block

My Life Story

// set up my bank account total

bank_account_total = 1000000 // Wish this was the case

 

=={{header|FALSE}}==

 

=={{header|Fancy}}==

 

# and last until the end of the line

 

=={{header|Fermat}}==

{Comments within a function are enclosed within curly brackets.}

{You can make multi-line comments

 

Function Bar(n) =

 

=={{header|Fish}}==

Since ><> is a funge-like language, all characters not touched by the command pointer or modified by the <tt>p</tt> and <tt>g</tt> commands can be comments.

Unlike Brainf***, unknown commands are not ignored by the compiler, they just raise an error.

>0>:n1+v all comments here

^o" "< still here

 

=={{header|Forth}}==

 

Standard Forth includes a number of ways to add comment text. As with everything in Forth, comment characters are actually words that control the compiler.

 

Traditionally, the paren comments are used for "stack effect" notation:

 

This comment means "myword takes two cells on the stack and leaves one". Sometimes, stack effect comment names give clues about the word's function:

 

Some Forth systems implement other commenting words, such as these words from Win32Forth:

(( skips until the next double-paren,

stretching across multiple lines ))

enddoc

/* C-style comment */

 

=={{header|Fortran}}==

The first six columns in Fortran are traditionally reserved for labels and certain special characters. In particular the letter "C" in the first column indicates a comment:

 

 

Some Fortran compilers have the extension that comments starting with D are treated as non-comments if a special debugging flag is given at the compiler invocation. For example:

 

 

ISO Fortran 90 or later have an inline comment (!) syntax:

 

 

In ISO Fortran 90 or later, "C in first column" comments are only allowed in the "fixed" source form familiar to FORTRAN 77 programmers. The "free" source form only has inline comments (!).

ISO Fortran 95 or later has an optional conditional compilation syntax. If present, it can be used (abused?) to (in effect) comment out blocks of code:

 

do while (oh_no)

a = bad_news()

c = gigo()

end do

 

=={{header|FreeBASIC}}==

 

' This a single line comment

'/

like this

 

=={{header|Frink}}==

// This is a single-line comment

/* This is a comment

and so on.

*/

 

=={{header|Futhark}}==

 

-- Single-line comment

 

-- Multi-line

-- comment (yes, just several single-line comments).

 

=={{header|FutureBasic}}==

// Single line comment

rem Single line comment

/* Single line comment */

comment

*/

 

=={{header|FUZE BASIC}}==

# Comment (Space required)

REM Comment (Space require)

PRINT "This is an inline comment."//Comment (No space required)

 

=={{header|Gambas}}==

In gambas, comments can be inserted by prefixing them with an apostrophe. The gambas interpreter will ignore the apostrophe and any other characters that follow it until the end of the line:

 

' This whole line is a comment and is ignored by the gambas interpreter

print "Hello" ' Comments after an apostrophe are ignored

' FIXME: Fix Me comment will appear in Task Bar

' NOTE: Note commnet will appear in Task Bar

 

=={{header|GAP}}==

 

=={{header|gecho}}==

 

=={{header|Gema}}==

A shebang (#!) may be used as a comment in the first line of a file.

 

=={{header|Genie}}==

Genie allows comments in code in two different ways.

 

 

Delimited comments cannot be nested.

=={{header|GML}}==

single-line comment:

 

multi-line comment:

ends with asterisk-slash.

also note:

* A multi-line comment is ignored inside a string

* A multi-line comment can be ended inside a line

 

=={{header|gnuplot}}==

 

# backslash continues \

a comment to the next \

 

The way backslash continues a comment means that comments can't usefully be put within a multi-line function definition,

 

foo(n) = (n \

+ 2 # no good \

 

# behaves as if you wrote merely

 

=={{header|Go}}==

/* this is

a multi-line

block comment.

 

=={{header|Golfscript}}==

 

=={{header|Gri}}==

<code>#</code> through to newline.

 

 

<code>//</code> works similarly but is reckoned the "old way" (as of Gri 2.12.23)

 

 

Both forms can be used in input data files too.

{{works with|GW-BASIC}}

 

 

=={{header|Haskell}}==

 

{- I am also

This is a Haddock documentation block comment

-}

 

=={{header|Haxe}}==

 

/*

line

comment.

 

=={{header|HicEst}}==

 

=={{header|Hope}}==

 

=={{header|HTML}}==

 

=={{header|Icon}} and {{header|Unicon}}==

Any text after "#" is a comment.

 

procedure x(y,z) #: This is a comment and an IPL meta-comment for a procedure

The [[:Category:Icon_Programming_Library|The Icon Programming Library]] established conventions for commenting library additions and functions. This included both header block comments and meta comments on procedures within library files.

 

The comment character in IDL is the semicolon - everything starting with it and to the end of the line is a comment. Like this:

 

=={{header|Inform 7}}==

 

[This is a

multi-line comment.]

 

 

=={{header|Intercal}}==

 

=={{header|Io}}==

 

// Single-line comment

 

/* Multi-line

 

=={{header|Isabelle}}==

imports Main

begin

(* Top-level Isar comment. *)

 

 

=={{header|J}}==

 

0 : 0

)

 

 

=={{header|Java}}==

Java has two ways to enter normal comments, plus a third type of comment that doubles as a way to generate HTML documentation.

===C Style===

 

* This is

* a multiple

* line comment.

This ''C-style'' comment starts with <tt>/*</tt> and ends with <tt>*/</tt>.

The two delimiters may be on the same or separate lines.

This style comment may be used anywhere white space is permitted.

===C++ Style (inline)===

This ''C++-style'' comment starts with <tt>//</tt> and extends to the end of line.

 

===Java Documentation (Javadoc)===

 

* This is

* a multiple

* line Javadoc comment

[http://en.wikipedia.org/wiki/Javadoc Javadoc] is a standardized documentation code for Java. Its comments begin with a forward slash and two stars. Javadoc comments have different tags that signify different things in the methods and classes that they precede.

 

===Sneaky===

Your editor will probably colour this as great big comment, but it compiles and prints "Hello World!". Once you've figured out how this works, try this [http://stackoverflow.com/questions/4448180/why-does-java-permit-escaped-unicode-characters-in-the-source-code discussion on why it's allowed].

/*

\u002A\u002F\u0070\u0075\u0062\u006C\u0069\u0063\u0020\u0073\u0074\u0061\u0074\u0069\u0063

\u002B\u0022\u0020\u0057\u006F\u0072\u006C\u0064\u0021\u0022\u0029\u003B\u007D\u002F\u002A

*/

 

=={{header|JavaScript}}==

a multi line

comment

// with a "nested" comment

and another line in the comment

 

=={{header|JCL}}==

first form

//* This is a comment line (//* in columns 1-3)

second form

/* This is also a comment line (/* in columns 1-3)

 

=={{header|Joy}}==

 

(* this is a

 

Multi-line comments cannot be nested.

=={{header|jq}}==

Except when a hash symbol (#) appears within a string, it begins a comment that continues to the end of the line:

"Hello #world" # the first # on this line is part of the jq program

 

=={{header|Jsish}}==

/* Comments, in Jsish */

 

PASS!: err = can not execute expression: 'noname' not a function

=!EXPECTEND!=

 

{{out}}

 

=={{header|Julia}}==

 

#=

line

comment

 

=={{header|K}}==

2+2 / as is this

 

=={{header|KonsolScript}}==

 

//This is another comment.

 

/* This is a

multi-line

 

=={{header|Kotlin}}==

 

/*

println("Current stable version is $CURRENT_VERSION")

println("Next major version is $NEXT_MAJOR_VERSION")

 

=={{header|Lambdatalk}}==

 

°°°

this is

on several lines

°°°

 

=={{header|LabVIEW}}==

{{VI solution|LabVIEW_Comments.png}}

 

=={{header|Lang5}}==

 

=={{header|langur}}==

Langur has 2 types of comments.

 

 

/* inline or multi-line comment uses C-style syntax */

 

 

=={{header|Lasso}}==

 

 

/* This is also a comment. */

A multi-line

comment

 

=={{header|LaTeX}}==

In LaTeX, comments look like this:

\begin{document}

% This is a comment

LaTeX comments start with <tt>%</tt> and continue up to ''and including'' the line break. The fact that the line break itself is commented out as well makes it useful for adding line breaks in the source code of complex macros without LaTeX interpreting them (which may cause extra space or even a paragraph break in the resulting typeset text). For example, the following results in the ''one'' word "understandable":

\newcommand{\firstpart}[1]{under#1}

\newcommand{\secondpart}{able}

\begin{document}

\complete

Without the percent sign after <tt>\firstpart{stand}</tt>, it would have been the ''two'' words "understand able".

 

=={{header|Liberty BASIC}}==

REM This is a comment

 

print "This has a comment on the end of the line." 'This is a comment

 

=={{header|Lily}}==

There are two kinds of comments:

 

 

and

 

is

a

block

 

Like with C, block comments don't nest.

=={{header|Lilypond}}==

 

 

%{ This is a comment

 

=={{header|Lingo}}==

In Lingo any line starting with "--" is a comment and ignored by the interpreter.

 

 

=={{header|LiveCode}}==

// comment may appear anywhere on line

# comment may appear anywhere on line

/* this is a

block comment that

 

=={{header|Logo}}==

 

=={{header|Logtalk}}==

 

=={{header|LOLCODE}}==

multi line comment

 

=={{header|LotusScript}}==

LotusScript has two ways to enter comments.

Wherever the single quote (<tt>'</tt>) is used, the rest of the line is treated as a comment and ignored. Multi-line comments would each need a single quote mark. This style of comment is usually used for making small in-line or single line comments.

This is a multi-

line comment.

A <tt>%REM</tt> marker begins a comment block, and a <tt>%END REM</tt> marker ends the comment block. This style of comment is used for making longer multi-line comments, often at the beginning of a class, sub or function.

 

=={{header|LSE}}==

 

(* Ceci est un commentaire sur plusieurs lignes

plusieurs lignes justement... *)

 

 

=={{header|LSE64}}==

The author of LSE64 comments the stack effect of words with header comments as follows:

 

=={{header|Lua}}==

 

 

--[[A multi-line

 

{{works with|Lua|5.1 and above}}

 

=={{header|M2000 Interpreter}}==

 

 

Module Comments {

}

Comments

 

 

=={{header|M4}}==

 

 

dnl this text completely disappears, including the new line

Everything diverted to -1 is processed but the output is discarded.

A comment could take this form as long as no macro names are used.

 

{{out}}

can separate it from preceding text if necessary

 

 

<code>changecom()</code> can set a different character for <code>#</code>,

 

 

In GNU m4 an empty <code>changecom()</code> string means no such commenting char at all (but in BSD m4 means reset to the default <code>#</code>)

 

 

In GNU m4 <code>changecom()</code> also takes separate start and end strings and they can be multi-character sequences, allowing for example C style,

 

 

=={{header|Maple}}==

 

17; (* This

is

{{out}}

<pre>

 

=={{header|Mathematica}} / {{header|Wolfram Language}}==

It can be used everywhere and nested if necessary:

evaluates to:

 

=={{header|MATLAB}}==

 

 

=={{header|Maxima}}==

/* Nested comment */

 

=={{header|MAXScript}}==

 

/* This is a

 

=={{header|MBS}}==

 

 

INT n:=5 ! Comments can appear at the end of a line

 

/* A comment block can also be defined using climbstar and starclimb symbols.

 

=={{header|Metafont}}==

 

=={{header|Microsoft Small Basic}}==

Microsoft Small Basic uses the quote symbol to mark it's comments. After placing a quote everything in that line will be ignored.

 

 

=={{header|min}}==

{{works with|min|0.19.3}}

 

=={{header|Mirah}}==

/* This is

* a multiple

* line comment */

 

=={{header|MIPS Assembly}}==

This is ultimately up to the assembler, but semicolons are typically the comment character for almost all assemblers.

 

=={{header|mIRC Scripting Language}}==

/*

Multiple

Line

Comment

 

=={{header|Modula-2}}==

and they can span multiple lines.

 

=={{header|Modula-3}}==

and they can span multiple lines.

 

=={{header|Monte}}==

 

# This comment goes to the end of the line

/** This comment is multi-line.

and ends with only one.

These should only be used for docstrings. */

 

=={{header|MontiLang}}==

 

/# This is a comment #/

/#

comments can span multiple lines

nested comments are not supported #/

 

=={{header|MOO}}==

// Some compilers will, however, compile // one-liners to string literals as well (and vice-versa)

 

=={{header|Nanoquery}}==

Comments in Nanoquery must be on a single line.

 

=={{header|NATURAL}}==

 

=={{header|Neko}}==

 

/*

Documentation block

<doc>can include XML parsed nodes between doc tags</doc>

 

=={{header|Nemerle}}==

/* This

is

a

multiline

 

=={{header|NESL}}==

 

=={{header|NetRexx}}==

NetRexx supports block-comments and line comments. Block comments are started with a <code>'''/*'''</code> and terminated with a <code>'''*/'''</code>. Line comments follow a <code>'''--'''</code> sequence anywhere on a line.

NetRexx supports nested comments (see [[#REXX|REXX]]).

 

NetRexx comment block

-- NetRexx line comment

 

 

=={{header|NewLISP}}==

A comment is started by <code>;</code> and reaches to the end of the line.

 

=={{header|Nim}}==

 

var x = 0 ## Documentation comments start with double hash characters.

discard """This can be considered as a "comment" too

This is multi-line"""

 

=={{header|Nix}}==

/* This

is

a

multiline

 

=={{header|NSIS}}==

# This is a comment that goes from the # to the end of the line.

; This is a comment that goes from the ; to the end of the

multi-line

comment */

 

=={{header|Oberon-2}}==

(* this is a comment *)

(*

(* with a nested comment *)

*)

 

=={{header|Objeck}}==

#This is a comment.

# This is other comment.

multi-line

comment ~#

 

=={{header|Objective-C}}==

=={{header|OCaml}}==

(* containing nested comment *)

*)

 

 

=={{header|Octave}}==

% I am a comment till the end of line

 

multiple lines

%}

 

=={{header|Oforth}}==

Oforth has only single line comment (inside or outside definition)

 

 

=={{header|ooRexx}}==

Comments in ooRexx follow the same rules as [[#REXX|REXX]] and [[#NetRexx|NetRexx]]

 

Multi-line comment block

*/

hour = 12 /* time for lunch! works as well (and really everywhere) */

 

 

=={{header|Openscad}}==

 

The openscad geometry compiler supports C++ style comments:

// This is a single line comment

 

*/

 

 

=={{header|OxygenBasic}}==

' Basic line comment

; Assembly code line comment

// C line comment

/* C block comment */

 

=={{header|Oz}}==

 

%% often with double "%" because then the indentation is correct in Emacs

comment

*/

 

=={{header|PARI/GP}}==

 

=={{header|Pascal}}==

It may extend across multiple lines. *)

 

but not valid in [[Turbo Pascal]]. }

 

 

In Pascal, comments cannot be nested.

=={{header|PASM}}==

 

print "Hello\n" # This is also a comment

 

=={{header|Peloton}}==

Peloton encloses all comments inside <@ OMT></@> (fixed length opcode) or <# OMIT></#> (variable length opcode) whether single- or multi- line.

<@ OMT>This is a

multiline

comment</@>

OMT suppresses evaluation of everything contained. There are a variety of extra opcodes which can be used to control how OMT functions at run time.

 

Single line comment

 

 

These may also be at the end of a line

 

 

Multi-line comments for inline documentation (Plain Old Documentation, or POD in Perl parlance) follow the format:

 

 

Here are my comments

this is multi-line

 

 

Note that technically, both of the lines beginning with the equals sign must be surrounded on either side for compatibility with all "POD" parsers.

Note also that any string beginning with an equals sign, and that appears in the initial column of a line, begins a multi-line comment. It does not have to be a POD "command:" the following are all valid:

 

=head4

=over 4

 

Such blocks always end in =cut.

{{libheader|Phix/basics}}

Single line comment:

 

Nestable multiline comments:

<span style="color: #000080;font-style:italic;">/*

This is a comment

*/</span>

<span style="color: #7060A8;">puts<span style="color: #0000FF;">(<span style="color: #000000;">1<span style="color: #0000FF;">,<span style="color: #008000;">"this is not a comment"<span style="color: #0000FF;">)

{{out}}

<pre>

this is not a comment

</pre>

 

=={{header|PHP}}==

Single line comment:

 

 

These may also be at the end of a line:

 

 

Basic syntax for multi-line comments:

 

Here are my comments

this is multi-line

 

Note that; it is more common to see phpDocumentor styled multi-lined comments:

 

* phpdoc Comments

* @todo this is a todo stub

 

=={{header|Picat}}==

{{works with|Picat}}

/*

* Multi-line comment

 

% Single-line Prolog-style comment

 

=={{header|PicoLisp}}==

#{

This is a

This is typically used conditionally, with a read-macro expression like

`*Dbg

 

=={{header|Pike}}==

/* This is a

multi

comment */

 

 

=={{header|PL/I}}==

This is a multiline comment.

Note: In PL/I, comments cannot be nested.

 

Single line comment:

 

 

Multiline comment:

 

this is a multiline

comment

 

End of line comment:

 

 

=={{header|Plain English}}==

 

=={{header|plainTeX}}==

it; so the % starts a to-end-of-line comment in many TeX macro packages.

 

 

The final newline character is eaten and since it normally behaves like a space, the comment can

be used to hide the newline:

 

\def\secondpart{able}

\def\complete{\firstpart{stand}%

\secondpart}

 

 

Outputs <tt>understandable</tt>; without % it would output <tt>understand able</tt>.

begins with tree consecutive semicolons and ends at the end of line:

 

 

C-like comments may be multiline:

 

 

C-like comments (unlike C) may be nested:

 

 

One can also use conditional compilation to comment out sections of code

 

some code

 

however, commented out part must consist of valid Pop11 tokens. In particular, C-like comments must balance and strings must be terminated.

The following is an error:

 

This w'ont work

 

because apostrophe starts an unterminated string.

 

=={{header|PostScript}}==

%This is a legal comment in PostScript

 

=={{header|PowerShell}}==

 

{{works with|PowerShell|2}}

 

=={{header|Processing}}==

 

/* a multi-line

// comment at the end of a line

 

==={{header|Processing Python mode}}===

 

"""

println("foo bar") # "baz"

 

 

=={{header|ProDOS}}==

I don't know why this is even a task because it should be included in any decent programming language.

 

=={{header|Prolog}}==

 

=={{header|PureBasic}}==

PureBasic uses the ";" symbol to mark its comments. All text entered after ";" on a line is ignored by the compiler.

foo = 5 ;This is a comment

 

=={{header|Python}}==

Python uses the "#" symbol to mark it's comments. After placing a "#", everything to the right of it in that line will be ignored.

 

 

Certain 'do nothing' expressions resemble comments

 

as multi-line comments

"""

of other quote marks without any need to \escape\ them using any special characters. They also may span multiple

lines without special escape characters.

 

Note that strings inserted among program statements in Python are treated as expressions (which, in void context, do nothing). Thus it's possible to "comment out" a section of code by simply wrapping the lines in "triple quotes" (three consecutive instances of quotation marks, or of apostrophes, and terminated with a matching set of the same). Using unassigned strings as comments is frowned on and may also trigger certain linters.

 

Python makes pervasive use of strings which immediately follow class and function definition statements, and those which appear as the first non-blank, non-comment line in any module or program file. These are called "documentation" strings or "docstrings" for short; and they are automatically associated with the '''__doc__''' attribute of the class, function, or module objects in which they are defined. Thus a fragment of code such as:

# Example of using doc strings

"""My Doc-string example"""

print (Foo.__doc__)

print (Foo.__init__.__doc__)

 

 

 

=={{header|Quackery}}==

( The word "(" is a compiler directive (a builder,

in Quackery jargon) that causes the compiler to

The word "commentary" will cause the compiler to

disregard everything that comes after it to the

 

 

=={{header|QB64}}==

''CBTJD'': 2020/03/12

' This is also a remark...

 

REM $STATIC 'arrays cannot be resized once dimensioned.

REM $DYNAMIC 'enables resizing of array dimensions with REDIM.

 

=={{header|R}}==

 

=={{header|Racket}}==

 

#| balanced comment, #| can be nested |# |#

 

#; ; the following expression is commented because of the #; in the beginning

 

=={{header|Raku}}==

A single-line comment starts with # and extends to the end of the line.

 

 

'''Multi-line comments'''

A multi-line comment starts with #` and followed by the commented text enclosed by bracketing characters (e.g., (), [], {}, 「」, etc.).

 

Comments beginning with a backtick and one or more opening bracketing characters are embedded comments.

They can span more than one line…

)

 

 

Multi-line comments can also be embedded into code.

 

say #`(or print element) $_ #`(with a newline);

 

Using more than one bracketing character lets you include an unmatched close bracket, as shown below.

 

This close curly brace } won't terminate the comment early.

 

'''Pod comments'''

 

 

Pod is the successor to Perl 5's POD. This is the simplest way to use it for multi-line comments.

For more about Pod, see Pod: https://docs.perl6.org/language/pod

 

 

Pod also provides declarator blocks which are special comments that attach to some source code and can be extracted as documentation. They are either #| or #= and must be immediately followed by either a space or an opening curly brace. In short, blocks starting with #| are attached to the code after them, and blocks starting with #= are attached to the code before them.

 

sub distance(

Rat \x1, #= First point's abscissa,

){

return sqrt((x2 - x1)**2 + (y2 - y1)**2)

 

=={{header|Raven}}==

 

=={{header|REBOL}}==

 

{ Multi-line strings can

be used as comments

if you like }

 

Functions have special commenting options which make them self documenting:

 

plus2: func [

"Adds two to a number."

n + 2

]

 

If you say "help plus2" at REBOL's REPL, you'll get this help information:

 

=={{header|Relation}}==

// This is a valid comment

// A space is needed after the double slash

 

=={{header|Retro}}==

 

=={{header|REXX}}==

 

Also, some REXX interpreters show the comment (if part of a REXX statement) as part of the information displayed when (if) a &nbsp; '''syntax''' &nbsp; error occurs and an informative error message is generated. &nbsp; For instance, in the program &nbsp; (named c:\COMMENTD.REX):

y=7

'''output''' &nbsp; when using the Regina REXX interpreter:'

<pre>

 

<br>Nested comments allow an easy way to comment large chunks of code where the commented-out code has its own comments.

 

/* everything between a "climbstar" and a "starclimb" (exclusive of literals) is

/*not a real good place for a comment (above),

but essentially, a REXX comment can be

 

A Classic REXX implementation (e.g. Regina) also allow line comments which start with a &nbsp; '''--''' &nbsp; sequence and extend to the end of the line:

 

 

It should be noted that the above type of comments are not part of Classic REXX, nor are they described nor sanctioned in the REXX ANSI standard.

 

=={{header|Ring}}==

in Ring language we can use // or # for one line comments:

//this is a single line comment

#this also a single line comment!

 

and for multi-line comments we use /* */:

/*This is a multi-line

comment that will be completely

ignored by the compiler/interpreter

*/

 

=={{header|RLaB}}==

RLaB only has single line comment indicator, as in following examples

 

x = "code" # I am a comment

x = "code" // Here I comment thee

# matlab-like document line

// C++ like document line

 

=={{header|Robotic}}==

Comments can only be created in one way:

. "This is a comment line"

 

 

. "This is the only way to comment a line in Robotic"

 

Although these are comments, the interpreter doesn't completely ignore it. For one, the code speed can be affected if they are ever encountered. Also, if an @ character exists at the beginning of the comment line, then the rest of the string after it is now the Robot's new name (there is a 14 character limit).

 

Example of changing the robot's name:

. "@NewRobotName"

 

This would then change the robot's name from whatever it was before to "NewRobotName" instead.

 

=={{header|Ruby}}==

 

 

=begin hello

I a POD documentation comment like Perl

 

=={{header|Run BASIC}}==

Comments have a ' (single quote) or REM for remarks

REM This is a comment

print "Notice comment at the end of the line." 'This is a comment

print "Also notice this comment at the end of the line." : REM This is a comment

 

=={{header|Rust}}==

 

/*

(inner attributes are terminated by a semi-colon)

See also https://github.com/mozilla/rust/blob/master/doc/rust.md#attributes"];

 

=={{header|SAS}}==

 

*another comment;

may

be

 

=={{header|Sather}}==

 

=={{header|Scala}}==

 

 

/* A multi-line

 

=={{header|Scheme}}==

; While R5RS does not provide block comments, they are defined in SRFI-30, as in Common Lisp :

 

 

; See http://srfi.schemers.org/srfi-30/srfi-30.html

 

=={{header|Scilab}}==

Specify a comment starting with // to the end of line

 

=={{header|sed}}==

 

=={{header|Seed7}}==

 

 

(* A multi-line

 

(* In Seed7,

 

=={{header|SenseTalk}}==

# Hashtag is a comment

-- Dash dash is another comment

blocks of code (* and can be nested *) *)

set foo to true // all comments can append to statements

 

=={{header|Set lang}}==

 

=={{header|SETL}}==

 

=={{header|Sidef}}==

Single line comment

 

These may also be at the end of a line

 

Embedded comments

 

Multi-line comments

This is a multi-line comment

 

=={{header|Simula}}==

The same as Algol 60:

And an new form:

'''Pitfall''': it's ''not'' easy to ''comment-out'' parts of code:

 

=={{header|Slate}}==

 

=={{header|Smalltalk}}==

 

"Multiline comments are also supported.

Comments are saved as metadata along with the source to a method.

A comment just after a method signature is often given to explain the

usage of the method. The class browser may display such comments

 

=={{header|smart BASIC}}==

 

 

PRINT "Hello" 'Single line comments may follow code

/* A comment can also follow another comment */ 'Like this

 

 

=={{header|SNOBOL4}}==

 

* An asterisk in column 1 is the standard Snobol comment

* mechanism, marking the entire line as a comment. There

END

 

 

=={{header|SNUSP}}==

 

=={{header|SPL}}==

 

''This is

 

=={{header|SQL}}==

 

The comment appears on the same line as the statement:

or before:

or after:

 

=={{header|SQL PL}}==

Single line comment:

 

--This is a single line comment.

 

Multiline comment:

 

/* This is

a multiline

comment */

 

Another way to do multiline comments

 

(= This is

a multiline

comment =)

 

End of line comment:

 

declare myvar number; --This is an end of line comment.

 

Comments work the same as in [[SQL]].

 

=={{header|Squirrel}}==

 

#this is also a single line comment

/*

this is a multi-line comment

 

=={{header|SSEM}}==

The SSEM can only be programmed in pure binary, by setting front panel switches: the concepts of "text" and "source file" (both mentioned in the specification) are therefore not directly applicable to it. If binary numbers have any mnemonic or explanatory value for you, however, there is a way of including information in your program that the computer will ignore. This is a direct result of the machine's rather poor code density. Each 32-bit instruction word consists of (a) a five-bit address field giving the operand, (b) eight unused bits, (c) a three-bit instruction field giving the operation to be performed, and (d) sixteen more unused bits. If the instruction field is set to <tt>011 Test</tt> or <tt>111 Stop</tt>, even the address field is unused. In the case of a <tt>Sub.</tt> instruction, finally, the leftmost bit of the instruction field is disregarded: <tt>001</tt> and <tt>101</tt> both mean "subtract". We therefore have at least 24 and sometimes 25 or 29 bits in each instruction that we can, if we like, use for comments. The word

will be understood by the machine as <tt>Add 20 to CI</tt>, a normal instruction. But it also fits four comment characters into the unused bits, employing a simple five-bit encoding where <tt>A</tt>=0 and <tt>Z</tt>=25. The instruction breaks down as follows:

 

=={{header|Standard ML}}==

(* containing nested comment *)

 

=={{header|Stata}}==

 

// Line comment until the end of the line

/* Multiline comment

 

 

=={{header|Swift}}==

/* This a block comment

/* containing nested comment */

/**

This is a documentation block comment

 

=={{header|Symsyn}}==

| This is a comment

 

=={{header|Tcl}}==

Tcl follows the usual scripting language rules: a comment starts at a "#" symbol, which can be placed after a command if that is terminated by a semicolon:

 

set var1 $value1

 

The reason for the need for a semi-colon on a trailing comment is this:

The "#" symbol has no special meaning if it is not where a command would appear -- it's just data. (Syntax highlighters often get this wrong.)

 

lappend aList # bar

puts $aList ;# ==> prints "foo # bar"

 

TCL has no native multi-line comment format. However, in most circumstances, a multi-line comment can be faked by wrapping it within a block that will never be executed:

 

Comments...

 

=={{header|Tern}}==

 

One common approach is to put the comment in a string which is not stored anywhere:

However this will change the Ans variable.

 

This approach, while messier, does not affect the Ans variable:

 

=={{header|TI-89 BASIC}}==

 

 

=={{header|Tiny BASIC}}==

 

10 REM this is a comment

20

40 REM from above you can see that line numbers with no statement

50 REM and blank lines also are ignored

 

=={{header|Toka}}==

a line, the shebang is normally used:

 

 

The shebang comments can not be used inside of functions.

In addition, Toka also accepts parenthetical comments. These are enclosed in parenthesis, and are often used for stack comments or comments inside functions.

 

 

In addition, parenthetical comments can span multiple lines.

 

simple, multi-line

 

Since comments are provided by actual functions, the comment function must be whitespace delimited, just as with all other functions in Toka.

A final way to include text in a file is to mark a false ending with '''end.'''

 

end.

 

=={{header|TorqueScript}}==

 

 

=={{header|TPP}}==

 

 

 

=={{header|Transd}}==

/* This is a single line block comment.*/

/* This is

a multi-line

block comment.*/

 

=={{header|TUSCRIPT}}==

$$ MODE TUSCRIPT

- This is a comment

 

=={{header|TXR}}==

 

@; new-style comment to end of line

@(bind a ; comment within expression

 

=={{header|UNIX Shell}}==

{{works with|Korn Shell}}

 

# A leading hash symbol begins a comment.

echo "Hello" # Comments can appear after a statement.

# The hash symbol must be at the beginning of a word.

echo This_Is#Not_A_Comment

 

==={{header|C Shell}}===

 

# C Shell has a similar comment syntax, but only allows comments in a

# script file, not in terminal input.

 

 

==={{header|es}}===

 

 

=={{header|Unlambda}}==

=={{header|Ursa}}==

Comments in Ursa must be on a single line, and are denoted by a #

# this is another comment

 

=={{header|Ursala}}==

There are lots of ways to have comments in Ursala.

Here are the conventional ones.

 

# this is a\

###

The whole rest of the file after three hashes

 

=== Commenting out code ===

An individual item of a syntactically correct list or aggregate is commented

out like this.

The 2 is ignored but 1 and 3 aren't. This also works with

nested aggregates and multiple lines.

 

<

'not',

'to',

A syntactically correct declaration can be commented out like this.

 

##

bar = 2

 

As far as the compiler is concerned, bar is not defined, but foo and baz are.

It wouldn't matter if bar took multiple lines.

to embed comments in executable files and libraries it generates without

affecting their semantics.

I document the source text but will also be embedded in

the output library or executable file.]-

 

The latter comment puts the standard GPL license notification in the output file.

 

A function f annotated with a crash dump wrapper expressed like this

during debugging

is equivalent to just f when changed to this in the production code.

 

=== Comments as hooks ===

Compiling with the --depend command line option makes the compiler only scan for the #depend'ed

expressions and send them to standard output.

otherwise,

This way, scripts and source management tools can have information passed to them from

the programmer by running the compiler instead of re-implementing their own parsers.

=={{header|VBA}}==

A comment starts with a quote (') and it ends at end of line

 

=={{header|VBScript}}==

A comment starts with a quote (') and it ends at end of line

 

=={{header|Verbexx}}==

//////////////////////////////////////////////////////////////////////////////////////////////

//

| |

\=================================================================================================/

 

=={{header|Verilog}}==

/*

line

comment.

 

=={{header|VHDL}}==

 

=={{header|Vim Script}}==

In most cases, " will also work after a command (i.e. the rest of the line will be ignored). But some commands like <code>echo</code> treat the whole line as their argument and thus will raise an error (''Missing quote'').

 

 

=={{header|Visual Basic}}==

In addition to the methods mentioned in [[#BASIC|BASIC]] above, it is also somewhat common to effectively comment out code by including the unwanted code inside an <code>#If 0 ... #End If</code> block. (This works because 0 evaluates to False in VB.) Note, however, that the IDE will complain about actual comments inside an <code>#If 0</code> block unless it's also commented normally (i.e., using <code>Rem</code> or <code>'</code>).

 

Rem comment

#If 0

IDE won't. Note the somewhat odd formatting seen here; the IDE will likely

just mark the entire line(s) as errors.

 

=={{header|Visual Basic .NET}}==

Visual Basic .NET uses the "'" symbol or "REM" to mark it's comments. After placing a "'", or "REM", everything in that line will be ignored.

 

REM This is also a comment

Dim comment as string ' You can also append comments to statements

 

=={{header|Visual Objects}}==

// This is a comment

/* This is a comment */

NOTE This is a commen

 

 

<pre>

// This is a single line comment.

=={{header|Vorpal}}==

 

 

=={{header|Wart}}==

 

 

=={{header|Wren}}==

/* This is a single line block comment.*/

/* This is

a multi-line

block comment.*/

 

=={{header|X10}}==

 

All text from the ASCII characters “//” to the end of line is considered a comment and is ignored.

 

/*

This comment spans

multiple lines

 

=={{header|XLISP}}==

 

=={{header|Xojo}}==

 

// Comments are denoted by a preceding double slash or or single quote

' and continue to the end of the line. There are no multi-line comment blocks

 

=={{header|XPL0}}==

always terminates a comment. Consequently there is no multi-line

comment. For example:

 

Since backslashes toggle comments on and off, it could be inconvenient to

comment out a line of code that contains a comment. For example, two

additional backslashes could be used to comment out this line, as shown here:

 

However, two backslashes together comment out everything to the end of

the line regardless of any backslashes the line might contain. So the

first example could be commented out like this:

 

Conditional compilation can be used to effectively comment out multiple

lines of code. For example:

Text(0, "Hello World"); \comment

CrLf(0);

 

=={{header|XQuery}}==

 

=={{header|XSLT}}==

 

=={{header|XUL}}==

 

 

=={{header|Yacas}}==

Yacas supports C++ style comments:

/*

This comment spans

multiple lines

 

=={{header|Z80 Assembly}}==

Note: syntax depends on the assembler software but use of a semicolon is fairly standard. VASM and WinAPE use the semicolon.

 

=={{header|zkl}}==

x=2; # ala scripts

/* ala C, these comments are parsed (also ala C) */

#<<<#

"here" comment, unparsed

 

=={{header|Zoea}}==

program comments # this program does nothing

 

comments

*/

 

=={{header|Zoea Visual}}==

 

=={{header|zonnon}}==

(* this is a comment *)

(*

(* with a nested comment *)

*)

=={{omit from|Computer/zero Assembly}}==