Lines Matching full:we

35 How do we prepare to fix this up? First we locate the code in question
37 F<pp> files. Sure enough, C<pp_pack> is in F<pp.c>. Since we're going
43 Now let's look over C<pp_pack>: we take a pattern into C<pat>, and then
45 C<datum_type>. Then for each possible format character, we swallow up
50 How do we know if the C<U> is the first format in the C<pat>? Well, if
51 we have a pointer to the start of C<pat> then, if we see a C<U> we can
52 test whether we're still at the start of the string. So, here's where
62 We'll have another string pointer in there:
72 And just before we start the loop, we'll set C<patcopy> to be the start
81 Now if we see a C<U> which was at the start of the string, we turn on
93 Oops, we forgot one thing: what if there are spaces at the start of the
96 case, we have to advance C<patcopy> along with C<pat> when we see
109 OK. That's the C part done. Now we must do two additional things before
110 this patch is ready to go: we've changed the behaviour of Perl, and so
111 we must document that change. We must also provide some more regression
117 The regression tests for each operator live in F<t/op/>, and so we make
118 a copy of F<t/op/pack.t> to F<t/op/pack.t~>. Now we can add our tests
119 to the end. First, we'll test that the C<U> does indeed create Unicode
122 t/op/pack.t has a sensible ok() function, but if it didn't we could use
134 we can write the more sensible (see L<Test::More> for a full
140 Now we'll test that we got that space-at-the-beginning business right:
145 And finally we'll test that we don't make Unicode strings if C<U> is
161 We now compile up Perl, and run it through the test suite. Our new
167 is over, so let's describe the change we've just made. The relevant
168 place is F<pod/perlfunc.pod>; again, we make a copy, and then we'll