Commit | Line | Data |
360aca43 |
1 | BEGIN { |
92e3d63a |
2 | use File::Basename; |
3 | my $THISDIR = dirname $0; |
4 | unshift @INC, $THISDIR; |
360aca43 |
5 | require "testp2pt.pl"; |
6 | import TestPodIncPlainText; |
7 | } |
8 | |
9 | my %options = map { $_ => 1 } @ARGV; ## convert cmdline to options-hash |
10 | my $passed = testpodplaintext \%options, $0; |
11 | exit( ($passed == 1) ? 0 : -1 ) unless $ENV{HARNESS_ACTIVE}; |
12 | |
13 | |
14 | __END__ |
15 | |
16 | |
17 | =pod |
18 | |
19 | This is a test to see if I can do not only C<$self> and C<method()>, but |
66aff6dd |
20 | also C<< $self->method() >> and C<< $self->{FIELDNAME} >> and |
21 | C<< $Foo <=> $Bar >> without resorting to escape sequences. If |
22 | I want to refer to the right-shift operator I can do something |
23 | like C<<< $x >> 3 >>> or even C<<<< $y >> 5 >>>>. |
360aca43 |
24 | |
66aff6dd |
25 | Now for the grand finale of C<< $self->method()->{FIELDNAME} = {FOO=>BAR} >>. |
26 | And I also want to make sure that newlines work like this |
27 | C<<< |
28 | $self->{FOOBAR} >> 3 and [$b => $a]->[$a <=> $b] |
29 | >>> |
360aca43 |
30 | |
31 | Of course I should still be able to do all this I<with> escape sequences |
32 | too: C<$self-E<gt>method()> and C<$self-E<gt>{FIELDNAME}> and C<{FOO=E<gt>BAR}>. |
33 | |
34 | Dont forget C<$self-E<gt>method()-E<gt>{FIELDNAME} = {FOO=E<gt>BAR}>. |
35 | |
e9fdc7d2 |
36 | And make sure that C<0> works too! |
37 | |
66aff6dd |
38 | Now, if I use << or >> as my delimiters, then I have to use whitespace. |
39 | So things like C<<$self->method()>> and C<<$self->{FIELDNAME}>> wont end |
40 | up doing what you might expect since the first > will still terminate |
41 | the first < seen. |
42 | |
8a523ae0 |
43 | Lets make sure these work for empty ones too, like C<< >> and C<< >> >> |
44 | (just to be obnoxious) |
45 | |
360aca43 |
46 | =cut |