# New Ticket Created by Saleem A. Ansari # Please include the string: [perl #63036] # in the subject line of all future correspondence about this issue. # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=63036 >
Fixed typos in docs/book ch09_pct.pod | 2 +- ch11_pmcs.pod | 2 +- ch12_opcodes.pod | 8 ++++---- 3 files changed, 6 insertions(+), 6 deletions(-)
Index: docs/book/ch09_pct.pod =================================================================== --- docs/book/ch09_pct.pod (revision 36357) +++ docs/book/ch09_pct.pod (working copy) @@ -95,7 +95,7 @@ automatically creating all the necessary stub files for creating a new compiler for Parrot. It generates the driver file, parser grammar and actions files, builtin functions stub file, makefile, and test harness. -All of these are demonstrative stubs and wil obviously need to be +All of these are demonstrative stubs and will obviously need to be edited furiously or even completely overwritten, but they give a good idea of what is needed to start on development of the compiler. Index: docs/book/ch12_opcodes.pod =================================================================== --- docs/book/ch12_opcodes.pod (revision 36357) +++ docs/book/ch12_opcodes.pod (working copy) @@ -18,7 +18,7 @@ pretty advanced compared to the functionality supplied by regular assembly language opcodes. -Before we talk about opcodes, we have to a little bit of talking about +Before we talk about opcodes, we shall discuss a little bit about the various runcores that invoke them. =head2 Runcores @@ -44,7 +44,7 @@ Parrot has multiple runcores. Some are useful for particular maintenance tasks, some are only available as optimizations in certain compilers, -some are intended for general use, and some are just interesing flights +some are intended for general use, and some are just interesting flights of fancy with no practical benefits. Here we list the various runcores, their uses, and their benefits. @@ -116,7 +116,7 @@ opcode becomes simply a label in a very large function, and pointers to the labels are stored in a large array. Calling an opcode is as easy as taking that opcode's number as the index of the label array, and calling the -associated label. Sound complicated? It is a little, especially to C +associated label. Sounds complicated? It is a little, especially to C programmers who are not used to using labels, much less treating them as first class data items. @@ -172,7 +172,7 @@ The precomputed goto core is an amazingly fast optimized core that uses the same computed goto feature, but performs the array dereferencing before the core even starts. The compiled bytecode is fed into a -preprocessor that converts the bytecode instruction numbers into lable +preprocessor that converts the bytecode instruction numbers into label pointer values. In the computed goto core, you have this operation to move to the next opcode: Index: docs/book/ch11_pmcs.pod =================================================================== --- docs/book/ch11_pmcs.pod (revision 36357) +++ docs/book/ch11_pmcs.pod (working copy) @@ -144,7 +144,7 @@ The PMC compiler enables us to use a few pre-defined variable names throughout the file to make things easier. The C<INTERP> keyword always contains a reference to the current interpreter structure. This keyword is -include by default in all VTABLE interfaces and all PMC methods. It is not +included by default in all VTABLE interfaces and all PMC methods. It is not automatically included in any extra helper functions that you define in the PMC file.
