That's not grammatical; you've just created a run-on sentence. Why not leave it as a colon?
On Sun, Oct 11, 2009 at 4:55 AM, <pugs-comm...@feather.perl6.nl> wrote: > Author: jimmy > Date: 2009-10-11 10:55:02 +0200 (Sun, 11 Oct 2009) > New Revision: 28751 > > Modified: > docs/Perl6/Spec/S02-bits.pod > Log: > [Spec/S02-bits.pod] changed colon to comma > > Modified: docs/Perl6/Spec/S02-bits.pod > =================================================================== > --- docs/Perl6/Spec/S02-bits.pod 2009-10-11 07:21:58 UTC (rev 28750) > +++ docs/Perl6/Spec/S02-bits.pod 2009-10-11 08:55:02 UTC (rev 28751) > @@ -247,7 +247,7 @@ > $object\ > .say > > -But unspace is mainly about language extensibility: it lets you continue > +But unspace is mainly about language extensibility, it lets you continue > the line in any situation where a newline might confuse the parser, > regardless of your currently installed parser. (Unless, of course, > you override the unspace rule itself...) > @@ -593,7 +593,7 @@ > > my Int $x = undef; # works > > -Variables with native types do not support undefinedness: it is an error > +Variables with native types do not support undefinedness, it is an error > to assign an undefined value to them: > > my int $y = undef; # dies > > -- Mark J. Reed <markjr...@gmail.com>
