Message-ID: <667066515.301239.1369113014937.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_301238_32749621.1369113014937" ------=_Part_301238_32749621.1369113014937 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Boo scripts have a set structure you need to follow to avoid err= ors when compiling. All of the items are optional, but order of the items = is not:
The structure is like:
There is one issue with the above structure, however. What if you are c= reating a library (dll), and you want to have "global" properties= or fields? Also, what if you want to do some things when your dll is load= ed by another application?
Now in Boo, you can do this by specifying a "global" class for= your module. You tell the Boo compiler to use your class as the global, m= odule-wide class by adding a [Module] attribute:
Also in Boo you can define which method the compiler should use as the m= ain entry point method. This is useful for example when you want to add an= attribute (like STAThread) to the main method. This main method can be an= ywhere in your boo script, or you can put it inside your main module class = if you want to combine both of these techniques.------=_Part_301238_32749621.1369113014937--