Message-ID: <1943566140.27097.1394333602809.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_27096_1359877702.1394333602809" ------=_Part_27096_1359877702.1394333602809 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The import construct makes all the members of the imported targ= et available to the current module. So instead of writing:=20 =20
one can write:=20 =20
The target can be either a namespace or a type. When it's a type, all th= e type's static members can be referenced directly by name. So the previous= example could be simplified even further:=20 =20
The from clause can be used to specify an additional assembly r= eference as well as to disambiguate namespaces. When using a Namespace that= is not defined in an assembly with the name of the Namespace, you = should use from:=20 =20
from also accepts a quoted string as argument for weird named a= ssemblies:=20 =20
And speaking of assembly references, the boo compiler automatically add = 4 assembly references before compiling any code: Boo, Boo.Lang.Compiler, (m= s)corlib and System.