Jerome Quelin wrote: > Melvin Smith wrote: > > I just checked in an intial IMCC faq (parrot/imcc/docs/imcfaq.pod) > Great job. Attached you'll find some corrections for typos.
And of course I forgot the patch file. Here it is. Jerome -- [EMAIL PROTECTED]
Index: imcfaq.pod =================================================================== RCS file: /cvs/public/parrot/imcc/docs/imcfaq.pod,v retrieving revision 1.1 diff -u -d -r1.1 imcfaq.pod --- imcfaq.pod 24 Nov 2003 06:53:16 -0000 1.1 +++ imcfaq.pod 24 Nov 2003 17:43:39 -0000 @@ -199,13 +199,13 @@ $I2 = $I1 * 3 -This uses symbolic STRING and INTVAL registers as temporaries. This is they typical sort of code +This uses symbolic STRING and INTVAL registers as temporaries. This is the typical sort of code that compilers generate from the syntax tree. =head3 Named Variables Named variables are either local, global or namespace qualified. Currently IMCC only -supports locals transparently, however globals are support in an explicit syntax. +supports locals transparently, however globals are supported in an explicit syntax. The way to declare locals in a subroutine is with the B<.local> directive. The B<.local> directive also requires a type (B<int>, B<num>, B<string> or a classname such as B<PerlArray>). @@ -287,8 +287,8 @@ This one is very simple. Use the B<.include> directive to include other .imc source files. Do keep in mind that currently Parrot starts execution with the first sub it sees in the bytecode; so if your main includes external .imc files it needs -to include them after the your "main" start sub. If you .include them first (in -typical C or Perl style, Parrot will execute the first sub in the first included +to include them after your "main" start sub. If you .include them first (in +typical C or Perl style), Parrot will execute the first sub in the first included source file. This is because B<.include> is a preprocessed directive and simply creates one huge .imc source module.
