This will not teach you how to write scenes nor bodies. It just tells you how to
write you files to be compatible with X2 and about BOD syntax enhancements of
x2bc. It is primary meant for people interested in BOD syntax but anybody using
my compiler should read about the "special operators"

All the "extensions" are based around extension of the standard comment
operator:

/   comment - rest of line is ignored (usually written as // to make it look
like C comments)

Special operators:
==================
These are special operators recognized only by x2bc - other programs (X2, BOD
viewer) will ignore them because they start with /

/#  header info - rest of line will be inserted into INFO section of BOB1/CUT1.
It acts as persistent remark.

/!  beginning of instruction block
instruction block is special block which is invisible for X2 (because it begins
with / ) and can contain any other tokens. It is used to specify values which
are not normally supported by BOD format.
Instruction block can span across multiple lines but such file will not be
compatible with X2! You must open and close instruction block on same line in
order to achieve compatibility with X2.

!/  end of instruction block

BOD format syntax:
==================

(you may skip this if not interested)

delimeters: { } ; : 'white space' 'new line' 'tabulator'

Curly brackets are only used in CUT1 and the define block of data with variable
length (frame definitions and embedded BOBs)

Semicolon is statement delimeter. Every statement must be terminated with it.
The only exception is body flag definition in body header which must NOT be
followed by semicolon.

Colon is probably not delimeter in X2 but I treat is so. It must be placed
immediately after previous token.
This is correct: VER: 1;
This is not: VER : 1;
because there is white space between colon and 'VER'

New line is delimeter but not statement separator, so you can write files this
way if you want:

VER:
1;

P
1
;

B
123;

N some name;

{
0x2; 1;2;
3;4;

}

This is perfectly valid CUT1 file (well except the fictive frames). Note that if
you will write (or change) BOB1 BOD files in this way, BOD Viewer will not load 
them (it relies on the "standard" form of the source file). But X2 will load 
them ok.

