Lines Matching full:foo*
178 =head1 Foo
182 $foo->bar
186 Here, "=head1 Foo" and "=cut" are command paragraphs because the first
187 line of each matches C<m/\A=[a-zA-Z]/>. "I<[space][space]>$foo->bar"
239 sub foo { # This is the second.
411 B<< $foo->bar(); >>
521 C<$foo->bar>
525 C<$foo-E<lt>bar>
528 only "$foo-", and then a "bar>" outside the "C" formatting code. This
531 C<< $foo->bar >>
744 code from being broken across lines. For example, "Foo::Bar" in some
746 as "Foo::" newline "Bar" or even "Foo::-" newline "Bar". This should
772 line 633 of Thing/Foo.pm!"), instead of merely noting the paragraph
773 number ("Nested EE<lt>>'s in Paragraph #52 of Thing/Foo.pm!"). Where
776 Paragraph #52 of Thing/Foo.pm, which begins 'Read/write accessor for
786 use Foo;
788 print Foo->VERSION
790 should be unified into one paragraph ("\tuse Foo;\n\n\tprint
791 Foo->VERSION") before being passed to the formatter or other
1001 "EE<lt>nbsp>" code); and Pod can contain "SE<lt>foo
1004 parsers should consider supporting the optional parsing of "SE<lt>foo
1006 "fooI<NBSP>IE<lt>barE<gt>I<NBSP>baz", and, going the other way, the
1135 crontab". "Section Foo" in the Pod sense means the part of the text
1136 that's introduced by the heading or item whose text is "Foo".)
1163 L<Foo::Bar>
1165 "Foo::Bar", # possibly inferred link text
1166 "Foo::Bar", # name
1169 "Foo::Bar" # original content
1269 use the first such anchor. That is, C<LE<lt>Foo/BarE<gt>> refers to the
1270 I<first> "Bar" section in Foo.
1295 "C<LE<lt>BE<lt>Foo::BarE<gt>E<gt>>".
1302 LE<lt>Foo::Bar> man page>" should be treated as an error.
1320 either the name of a Pod page like C<LE<lt>Foo::BarE<gt>> (which
1331 given C<LE<lt>fooE<gt>> code.