

==== Step 0:
File Name      : MP_0.txt
Author         : Michael Preslar / E_Maus
Author Note    : Heres some info about the language..
Example Source : none
Date           : September 27th, 1998
Length         : 5 pages
Layout         : - Yay pascal! (good things about pascal)
                 - boo pascal! (bad things about pascal)
                 - basic syntax
====
Please refer back to "intro.txt" for complete documentation of copyrights,
and author information.

Step 0 foreword
---------------
This text is a basic look at the language itself. It should answer a few
questions you have before we start and make your learning process and our
teaching experience easier.

As youre reading over this, you might see quite a few new terms. Dont worry.
They will all be explained eventually. Just remember to follow the rules.
If a rules says "during a unit.." but youre not working on a unit, you dont
have to follow that one, and can "forget" it, right?

  =========================== Yay pascal! =================================

Pascal is a very "kind" language. Meaning that for the end user (the
programmer), its very easy to use. What makes it easy to use?

1) There are different programming language types. High-, middle-, and low-
   end languages. The assembly programming language is a low end lanuage
   since you work with the computers memory explicity. Since BASIC acts
   somewhat like a translator for the programmer and does the memory work
   itself, but doesnt have a lot of capabilites, its called a middle-end
   language. Pascal, on the other hand, is a translator with a lot of
   capabilities, making it a high-end language.

2) Pascal is easy to read. Granted C, assmebly, and other languages are
   powerful, they are cryptic to whoever is reading them. Pascal, on the
   other hand, is fluid with a simple syntax.

3) Pascal is a "modular" language. Meaning, you can have several different
   source files that all compile together to make one program. This leads
   to easy to read, easy to use, and reusable code.

4) Pascal is a "free flowing" language. Pascal compilers dont care how
   something is capatilized, or how your sentences are stretched out.
   For example:

      writeln('Hi there!');

   would have the same effect as

      wRiTeLn
             ('Hi there!')
             ;

5) All math functions are built into the language. They are (in precedence):
   First  : @, not
   Second : *, /, div, mod, and, shl, shr
   Third  : +, -, or, xor,
   Fourth : =, <> (doesnt equal), < (less), > (greater), <= (less or equal),
            >= (greater or equal), ( ), [ ], < >


  ============================= Boo pascal! ===============================

As much as I like pascal, there are some bad points about it..

1) You must write your programs with what platform it is to be used on in
   mind. In other words, if youre working on a project that will be used on
   a DOS based machine, you have to program for the DOS based machine.
   However, that same code wont be usable on an OS/2 machine without certain
   changes.

2) As far as I know (i could be wrong), pascal code cant be used on *nix
   machines without some sort of DOS emulator. Not sure why..

3) Some say that the optimization the pascal compiler uses to compile code
   could be better: more memory efficient, faster, etc.. But then again,
   I usually dont hear things like that outside of a Pascal versus C debate.

  ============================= Basic syntax ==============================
Every pascal program must have the same basic syntax. In other words, you
have to use the language the way it was designed.

1) Every block of code must be identified. If the code your currently working
   on is the main code of the program, you must have "program <program name>"
   at the top. If your working on a unit, it must be identified at the top.
   Procedures and functions should also be identified before the actual
   coding takes place as well.

2) Once youve identified what the code is for, you have to tell it to "begin"
   the block of code. You do this by simply putting a "begin" there.

3) Once youve finished the block of code, you have to tell it to "end".
   Again, you simply do this with an "end". However, if its the last "end"
   of the project, it must have a period after it.

4) All other lines have a semi-colon after it.

5) You cant declare variables, constants, or types within a block of code.

6) Comments.. Suppose you wanted to write something in with your source that
   would not get compiled. How could you do it? Comment it.. Surround the
   text with fancy brackets.. { to begin, } to end.. or comment it with
   (* to begin, and *) to end.. Note that the (* *) pair over-rides the
   fancy bracket method.

  =============================== In closing.. =============================
Hope this clears things up a bit..
