[svn:parrot] r38097 - trunk/docs/book
Util at svn.parrot.org
Util at svn.parrot.org
Tue Apr 14 02:20:24 UTC 2009
Author: Util
Date: Tue Apr 14 02:20:22 2009
New Revision: 38097
URL: https://trac.parrot.org/parrot/changeset/38097
Log:
[book] Typo corrections
Modified:
trunk/docs/book/ch02_getting_started.pod
trunk/docs/book/ch03_pir_basics.pod
trunk/docs/book/ch04_pir_subroutines.pod
trunk/docs/book/ch05_pasm.pod
trunk/docs/book/ch06_library.pod
trunk/docs/book/ch09_pct.pod
trunk/docs/book/ch11_pmcs.pod
trunk/docs/book/ch12_opcodes.pod
trunk/docs/book/ch13_reference.pod
Modified: trunk/docs/book/ch02_getting_started.pod
==============================================================================
--- trunk/docs/book/ch02_getting_started.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch02_getting_started.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -24,7 +24,7 @@
Once you've compiled Parrot, you can run your first small script. Create
a test file in the main F<parrot> directory called F<fjord.pasm>. C<.pasm>
-files are written in primative Parrot Assembly Language (PASM) which is a
+files are written in primitive Parrot Assembly Language (PASM) which is a
low-level programming interface to Parrot.
=begin PASM
@@ -159,7 +159,7 @@
download the most recent point release for your system. Point releases
are usually packaged up for easy download and install for various
platforms, including Windows, Debian, and Redhat. Point releases are
-avaliable from U<http://www.parrot.org/download>.
+available from U<http://www.parrot.org/download>.
If you plan to get involved in development, you'll want to check out
the source from the subversion repository directly. Anyone can get
Modified: trunk/docs/book/ch03_pir_basics.pod
==============================================================================
--- trunk/docs/book/ch03_pir_basics.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch03_pir_basics.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -344,7 +344,7 @@
of one another. C<$S0> is assigned a value in line 2, and is read in line 3,
but is never accessed after that. So, Parrot determines that its lifespan
ends at line 3. The register C<$S1> is used first on line 4, and is accessed
-again on line 5. Sinec these two do not overlap, Parrot's compiler can
+again on line 5. Since these two do not overlap, Parrot's compiler can
determine that it can use only one register for both operations. This saves
the second allocation. Notice that this code with only one register performs
identically to the previous example:
@@ -401,11 +401,11 @@
PIR is a dynamic language, and that dynamicism is readily displayed in
the way PMC values are handled. Primitive registers like strings,
numbers, and integers perform a special action called I<autoboxing>
-when they are assigned to a PMC. Autoboxing is when a primative scalar
+when they are assigned to a PMC. Autoboxing is when a primitive scalar
type is automatically converted to a PMC object type. There are PMC
classes for String, Number, and Integer which can be quickly converted
to and from primitive int, number, and string types. Notice that the
-primative types are in lower-case, while the PMC classes are
+primitive types are in lower-case, while the PMC classes are
capitalized. If you want to box a value explicitly, you can use the C<box>
opcode:
@@ -417,7 +417,7 @@
$P2 = "This is a string!"
The PMC classes C<Integer>, C<Number>, and C<String> are thin overlays on
-the primative types they represent. However, these PMC types have the benefit
+the primitive types they represent. However, these PMC types have the benefit
of the X<PMC;VTABLE Interface> VTABLE interface. VTABLEs are a standard
API that all PMCs conform to for performing standard operations. These PMC
types also have special custom methods available for performing various
@@ -845,7 +845,7 @@
base types, by sharing the same VTABLE methods and underlying data types.
However, the subclass can define additional methods and attribute data
storage. If necessary new VTABLE interfaces can be defined in PIR and old
-VTABLE methods can be overriden using PIR. We'll talk about defining
+VTABLE methods can be overridden using PIR. We'll talk about defining
methods and VTABLE interface overrides in the next chapter.
Creating a new subclass of an existing PMC class is done using the
Modified: trunk/docs/book/ch04_pir_subroutines.pod
==============================================================================
--- trunk/docs/book/ch04_pir_subroutines.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch04_pir_subroutines.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -712,7 +712,7 @@
X<.namespace>
Namespaces provide a mechanism where names can be reused. This may not
sound like much, but in large complicated systems, or systems with
-many included libraries, it can be very handy. Each namespace get's its
+many included libraries, it can be very handy. Each namespace gets its
own area for function names and global variables. This way you can have
multiple functions named C<create> or C<new> or C<convert>, for
instance, without having to use I<Multi-Method Dispatch> (MMD) which we
Modified: trunk/docs/book/ch05_pasm.pod
==============================================================================
--- trunk/docs/book/ch05_pasm.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch05_pasm.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -330,7 +330,7 @@
Z<CHP-5-SECT-2.2.3>
-X<Auboboxing>
+X<Autoboxing>
As we've seen in the previous chapters about PIR, we can convert between
primitive string, integer, and number types and PMCs. PIR used the C<=>
operator to make these conversions. PASM doesn't have any symbolic operators
Modified: trunk/docs/book/ch06_library.pod
==============================================================================
--- trunk/docs/book/ch06_library.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch06_library.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -28,7 +28,7 @@
Libraries are precompiled code files that can be loaded into Parrot. There
are ways to load a library into Parrot, each with a slightly different
mechanism. The C<.loadlib> PIR directive causes the library file to be loaded
-at compile-time. The C<load_lib> obcode causes the library to be loaded
+at compile-time. The C<load_lib> opcode causes the library to be loaded
dynamically at runtime.
=head1 General Parrot Libraries
Modified: trunk/docs/book/ch09_pct.pod
==============================================================================
--- trunk/docs/book/ch09_pct.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch09_pct.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -436,7 +436,7 @@
are optimized for use with expressions and equations. The "things" in an
equation are split into two subtypes: I<terms> and I<operators>. Operators
themselves are split into a number of types including prefix (C<-a>),
-postfix (C<i++>), infix (C<x + y>), circumfix (C<[z]>), postcircumix
+postfix (C<i++>), infix (C<x + y>), circumfix (C<[z]>), postcircumfix
(C<a[b]>), and list (C<1, 2, 3>). Each operator gets its own precedence
number that specifies how closely it binds to the terms. In the example above,
the expression is parsed
@@ -546,7 +546,7 @@
=head2 Actions and NQP
Protofunction signatures aren't the only way to apply functions to rules
-matched by the parser. In fact, they might be the most primative because
+matched by the parser. In fact, they might be the most primitive because
they use PIR code to implement the operator logic. Another way has been made
available, by programming function actions in a language that's almost, but
Not Quite Perl (NQP).
@@ -566,7 +566,7 @@
used for hashes N<Perl 6 aficionados will know that this isn't entirely
true, but an in-depth look at Perl 6's context awareness is another topic
for another book>. A "scalar" is really any single value, and can
-interchangably be given a string value, or an integer value, or an object.
+interchangeably be given a string value, or an integer value, or an object.
In NQP we can write things like this:
$scalar := "This is a string"
Modified: trunk/docs/book/ch11_pmcs.pod
==============================================================================
--- trunk/docs/book/ch11_pmcs.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch11_pmcs.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -35,7 +35,7 @@
program that converts PMCs defined in a special C-like script to ordinary
C code. The PMC compiler adds all the necessary boiler plate code and installs
the PMC type into Parrot for use. The PMC script is like a macro superset
-N<although the functionality is a litte bit more involved then is available
+N<although the functionality is a little bit more involved than is available
in the normal C preprocessor> over the C language. All valid C is valid in
PMC scripts, but there are also a few additions that help to make common tasks
a little easier.
Modified: trunk/docs/book/ch12_opcodes.pod
==============================================================================
--- trunk/docs/book/ch12_opcodes.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch12_opcodes.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -218,7 +218,7 @@
L<src/dynoplibs/>. These are small libraries of mostly nonsensical but
demonstrative opcodes that can be used as an example to follow.
-Dynops can be writte in a C<.ops> file like the normal built-in ops are.
+Dynops can be written in a C<.ops> file like the normal built-in ops are.
The ops file should use C<#include "parrot/extend.h"> in addition to any
other libraries the ops need. They can be compiled into C using the opcode
compiler, then compiled into a shared library using a normal C compiler. Once
Modified: trunk/docs/book/ch13_reference.pod
==============================================================================
--- trunk/docs/book/ch13_reference.pod Mon Apr 13 19:19:27 2009 (r38096)
+++ trunk/docs/book/ch13_reference.pod Tue Apr 14 02:20:22 2009 (r38097)
@@ -2487,7 +2487,7 @@
subclass R<DEST>, R<CLASS>
subclass R<DEST>, R<CLASS>, R<NAME>
-Create a sublass of R<CLASS>. Without R<NAME> an anonymous subclass is
+Create a subclass of R<CLASS>. Without R<NAME> an anonymous subclass is
created.
I<Arguments: P, S or P, P or P, S, S or P, P, S>
More information about the parrot-commits
mailing list