Difference between revisions of "Basic Pascal Tutorial/Chapter 1/Program Structure"

From Lazarus wiki
Jump to navigationJump to search
m (Text replace - "delphi>" to "syntaxhighlight>")
Line 2: Line 2:
  
 
The basic structure of a Pascal program is:
 
The basic structure of a Pascal program is:
<delphi>
+
<syntaxhighlight>
 
PROGRAM ProgramName (FileList);
 
PROGRAM ProgramName (FileList);
  
Line 19: Line 19:
 
   (* Executable statements *)
 
   (* Executable statements *)
 
END.  
 
END.  
</delphi>
+
</syntaxhighlight>
 
The elements of a program must be in the correct order, though some may be omitted if not needed. Here's a program that does nothing, but has all the required elements:
 
The elements of a program must be in the correct order, though some may be omitted if not needed. Here's a program that does nothing, but has all the required elements:
<delphi>
+
<syntaxhighlight>
 
program DoNothing;
 
program DoNothing;
 
begin
 
begin
end. </delphi>
+
end. </syntaxhighlight>
 
Comments are portions of the code which do not compile or execute. Pascal comments start with a (* and end with a *). You cannot nest comments:
 
Comments are portions of the code which do not compile or execute. Pascal comments start with a (* and end with a *). You cannot nest comments:
<delphi>
+
<syntaxhighlight>
 
       {  (* (* *) *)
 
       {  (* (* *) *)
</delphi>
+
</syntaxhighlight>
 
will yield an error because the compiler matches the first '<tt>(*</tt>' with the first '<tt>*)</tt>', ignoring the second '<tt>(*</tt>' which is between the first set of comment markers. The second '<tt>*)</tt>' is left without its matching '<tt>(*</tt>'. This problem with begin-end comment markers is one reason why many languages use line-based commenting systems.
 
will yield an error because the compiler matches the first '<tt>(*</tt>' with the first '<tt>*)</tt>', ignoring the second '<tt>(*</tt>' which is between the first set of comment markers. The second '<tt>*)</tt>' is left without its matching '<tt>(*</tt>'. This problem with begin-end comment markers is one reason why many languages use line-based commenting systems.
  
Line 36: Line 36:
  
 
In addition, comments are often used to take problematic code out of action without deleting it. Remember the earlier restriction on nesting comments? It just so happens that braces <tt>{}</tt> take precedence over parentheses-stars <tt>(* *)</tt>. You will not get an error if you do this:
 
In addition, comments are often used to take problematic code out of action without deleting it. Remember the earlier restriction on nesting comments? It just so happens that braces <tt>{}</tt> take precedence over parentheses-stars <tt>(* *)</tt>. You will not get an error if you do this:
<delphi>
+
<syntaxhighlight>
 
{ (* Comment *) }
 
{ (* Comment *) }
</delphi>
+
</syntaxhighlight>
  
 
Whitespace (spaces, tabs, and end-of-lines) are ignored by the Pascal compiler unless they are inside a literal string. However, to make your program readable by human beings, you should indent your statements and put separate statements on separate lines. Indentation is often an expression of individuality by programmers, but collaborative projects usually select one common style to allow everyone to work from the same page.
 
Whitespace (spaces, tabs, and end-of-lines) are ignored by the Pascal compiler unless they are inside a literal string. However, to make your program readable by human beings, you should indent your statements and put separate statements on separate lines. Indentation is often an expression of individuality by programmers, but collaborative projects usually select one common style to allow everyone to work from the same page.

Revision as of 14:51, 24 March 2012

Basics 1A - Program Structure (author: Tao Yue, state: unchanged)

The basic structure of a Pascal program is:

PROGRAM ProgramName (FileList);

CONST
  (* Constant declarations *)

TYPE
  (* Type declarations *)

VAR
  (* Variable declarations *)

(* Subprogram definitions *)

BEGIN
  (* Executable statements *)
END.

The elements of a program must be in the correct order, though some may be omitted if not needed. Here's a program that does nothing, but has all the required elements:

program DoNothing;
begin
end.

Comments are portions of the code which do not compile or execute. Pascal comments start with a (* and end with a *). You cannot nest comments:

      {  (* (* *) *)

will yield an error because the compiler matches the first '(*' with the first '*)', ignoring the second '(*' which is between the first set of comment markers. The second '*)' is left without its matching '(*'. This problem with begin-end comment markers is one reason why many languages use line-based commenting systems.

Turbo Pascal and most other modern compilers support brace comments, such as {Comment}. The opening brace signifies the beginning of a block of comments, and the ending brace signifies the end of a block of comments. Brace comments are also used for compiler directives.

Commenting makes your code easier to understand. If you write your code without comments, you may come back to it weeks, months, or years later without a guide to why you coded the program that way. In particular, you may want to document the major design of your program and insert comments in your code when you deviate from that design for a good reason.

In addition, comments are often used to take problematic code out of action without deleting it. Remember the earlier restriction on nesting comments? It just so happens that braces {} take precedence over parentheses-stars (* *). You will not get an error if you do this:

{ (* Comment *) }

Whitespace (spaces, tabs, and end-of-lines) are ignored by the Pascal compiler unless they are inside a literal string. However, to make your program readable by human beings, you should indent your statements and put separate statements on separate lines. Indentation is often an expression of individuality by programmers, but collaborative projects usually select one common style to allow everyone to work from the same page.

previous contents next