Reference.Comments History

Hide minor edits - Show changes to markup

September 21, 2008, at 01:01 AM by Paul Badger -
Changed line 14 from:

if (gwb == 0){ // single line comment is OK inside of a multiline comment

to:

if (gwb == 0){ // single line comment is OK inside a multiline comment

September 06, 2008, at 09:26 PM by Paul Badger -
Changed line 14 from:

if (gwb == 0){ // single line comment is OK inside of multiline comment

to:

if (gwb == 0){ // single line comment is OK inside of a multiline comment

July 17, 2007, at 06:24 AM by Paul Badger -
Changed line 21 from:

Tip

to:

Tip\\

June 04, 2007, at 04:40 AM by Paul Badger -
Changed line 15 from:

x = 3; /* but not another multiline comment - this is invalid */

to:

x = 3; /* but not another multiline comment - this is invalid */

June 04, 2007, at 04:40 AM by Paul Badger -
Changed line 14 from:

if (gwb > 0){ // single line comment is OK inside of multiline comment

to:

if (gwb == 0){ // single line comment is OK inside of multiline comment

June 04, 2007, at 04:39 AM by Paul Badger -
Changed lines 10-11 from:
           // to the end of the line
to:
         // to the end of the line
June 04, 2007, at 04:39 AM by Paul Badger -
Changed lines 10-11 from:

// to the end of the line

to:
           // to the end of the line
June 04, 2007, at 04:38 AM by Paul Badger -
Changed lines 9-10 from:

[@ x = 5; // This is a single line comment. Anything after the slashes is a comment to the end of the line

to:

[@ x = 5; // This is a single line comment. Anything after the slashes is a comment // to the end of the line

June 04, 2007, at 04:38 AM by Paul Badger -
Deleted line 19:
Changed lines 21-22 from:

When experimenting with code "commenting out" parts of your program is a convenient way to remove lines that may be buggy. This leaves the lines in the code but turns them into comments, so the compiler will ignore them. This can be especially useful when trying to locate a problem, or when a program refuses to compile and the compiler error is cryptic or unhelpful.

to:

When experimenting with code, "commenting out" parts of your program is a convenient way to remove lines that may be buggy. This leaves the lines in the code, but turns them into comments, so the compiler just ignores them. This can be especially useful when trying to locate a problem, or when a program refuses to compile and the compiler error is cryptic or unhelpful.

June 04, 2007, at 04:36 AM by Paul Badger -
Changed lines 3-5 from:

Comments are parts in the program that are used to inform yourself or others about the way the program works. Comments are ignored by the compiler, and not exported to the processor, so they don't take up any space on the Atmega chip.

They are strictly useful to help you understand (or remember) how your program works or to inform others how your program works.

to:

Comments are lines in the program that are used to inform yourself or others about the way the program works. They are ignored by the compiler, and not exported to the processor, so they don't take up any space on the Atmega chip.

Comments only purpose are to help you understand (or remember) how your program works or to inform others how your program works.

Changed lines 9-10 from:

[@ x = 5; // This is a single line comment. Anything after the slashes is a comment

to:

[@ x = 5; // This is a single line comment. Anything after the slashes is a comment to the end of the line

Changed line 16 from:
to:

// don't forget the "closing" comment - they have to be balanced!

June 04, 2007, at 04:24 AM by Paul Badger -
Changed lines 3-5 from:

Comments are parts in the program that are used to inform oneself or others about the way the program works. Comments are not compiled or exported to the processor, so they don't take up any space on the Atmega chip.

They are strictly useful for you to understand what your program is doing or to inform others how your program works.

to:

Comments are parts in the program that are used to inform yourself or others about the way the program works. Comments are ignored by the compiler, and not exported to the processor, so they don't take up any space on the Atmega chip.

They are strictly useful to help you understand (or remember) how your program works or to inform others how your program works.

Changed line 14 from:

x = 3; /* but not another multiline comment - this is invalid */

to:

x = 3; /* but not another multiline comment - this is invalid */

June 04, 2007, at 04:20 AM by Paul Badger -
Changed lines 11-13 from:

/* you could use a combination of slash-asterisk --> asterisk-slash encapsulating your comments:

x = 7;

to:

/* this is multiline comment - use it to comment out whole blocks of code

Changed lines 17-23 from:

8/

 */'''
to:
  • /
June 04, 2007, at 04:17 AM by Paul Badger -
Changed lines 9-11 from:

[@ x = 5; // This is a single line comment - anything after the slashes is a comment

  • you could use a combination of slash-asterisk --> asterisk-slash encapsulating your comments: /* blabla */
to:

[@ x = 5; // This is a single line comment. Anything after the slashes is a comment

/* you could use a combination of slash-asterisk --> asterisk-slash encapsulating your comments:

x = 7; if (gwb > 0){ // single line comment is OK inside of multiline comment x = 3; /* but not another multiline comment - this is invalid */ }

8/

 */'''
June 04, 2007, at 04:14 AM by Paul Badger -
Changed lines 12-14 from:
to:

@]

June 04, 2007, at 04:13 AM by Paul Badger -
Changed lines 8-9 from:
  • you may use a double-slash in the beginning of a line: //
to:

Example

[@ x = 5; // This is a single line comment - anything after the slashes is a comment

June 04, 2007, at 04:12 AM by Paul Badger -
Changed lines 3-5 from:

Comments are parts in the program that are used to inform about the way the program works. They are not going to be compiled, nor will be exported to the processor. They are useful for you to understand what a certain program you downloaded is doing or to inform to your colleagues about what one of its lines is.

to:

Comments are parts in the program that are used to inform oneself or others about the way the program works. Comments are not compiled or exported to the processor, so they don't take up any space on the Atmega chip.

They are strictly useful for you to understand what your program is doing or to inform others how your program works.

Changed line 8 from:
  • you could use a double-slash in the beginning of a line: //
to:
  • you may use a double-slash in the beginning of a line: //
Added line 11:
Changed lines 13-14 from:

When experimenting with code the ability of commenting parts of your program becomes very useful for you to "park" part of the code for a while.

to:

When experimenting with code "commenting out" parts of your program is a convenient way to remove lines that may be buggy. This leaves the lines in the code but turns them into comments, so the compiler will ignore them. This can be especially useful when trying to locate a problem, or when a program refuses to compile and the compiler error is cryptic or unhelpful.

April 18, 2007, at 09:09 AM by David A. Mellis -
Deleted lines 11-12:
January 13, 2006, at 12:35 AM by 82.186.237.10 -
Changed lines 10-13 from:

When experimenting with code the ability of commenting parts of your program becomes very useful for you to "park" part of the code for a while.

to:

When experimenting with code the ability of commenting parts of your program becomes very useful for you to "park" part of the code for a while.

Reference Home

January 03, 2006, at 10:35 AM by 82.186.237.10 -
Added lines 1-10:

Comments

Comments are parts in the program that are used to inform about the way the program works. They are not going to be compiled, nor will be exported to the processor. They are useful for you to understand what a certain program you downloaded is doing or to inform to your colleagues about what one of its lines is. There are two different ways of marking a line as a comment:

  • you could use a double-slash in the beginning of a line: //
  • you could use a combination of slash-asterisk --> asterisk-slash encapsulating your comments: /* blabla */

Tip When experimenting with code the ability of commenting parts of your program becomes very useful for you to "park" part of the code for a while.

Share