45 lines
1.5 KiB
OpenEdge ABL
45 lines
1.5 KiB
OpenEdge ABL
/*
|
|
* VIM_TEST_SETUP set filetype=progress
|
|
*/
|
|
|
|
define variable customer_name as character no-undo.
|
|
|
|
/* The test setup above is an example of a multi-line comment.
|
|
This is too; the leading * and left-hand alignment are not required. */
|
|
for each customer no-lock
|
|
where customer.customer_id = 12345
|
|
:
|
|
assign cust_name = customer.customer_name. /* Comments can also appear
|
|
at the end of a line. */
|
|
end. /* for each customer */
|
|
|
|
/* Comments can be /* nested */. Here's the same query as above, but
|
|
commented out this time:
|
|
|
|
for each customer no-lock
|
|
where customer.customer_id = 12345
|
|
:
|
|
assign cust_name = customer.customer_name. /* Comments can also appear
|
|
at the end of a line. */
|
|
end. /* for each customer */
|
|
|
|
TODO: Note that /*/ does not end the comment, because it actually starts a
|
|
new comment whose first character is a '/'. Now we need two end-comment
|
|
markers to return to actual code. */ */
|
|
|
|
display customer_name.
|
|
|
|
// This is the single-line comment syntax.
|
|
|
|
//No space is required after the slashes. Also, a /* here does not begin a
|
|
//new block comment.
|
|
|
|
for each supplier no-lock:
|
|
/* However, a block comment can end inside (what looks like) a
|
|
single-line comment, because the slashes are just text as far as the
|
|
// block comment is concerned. */
|
|
display supplier.
|
|
|
|
// TODO: Observe that todo highlighting works in line comments too.
|
|
end.
|
|
|