On 14 Nov 2001, Russ Allbery wrote: > > It would be good to include more of the technical syntax in here. For > example, how should the following be parsed? > > L<"Parsing and/or Formatting"> > L<"Parsing/Formatting"> > L<"Fun Times"/"Summer Vacation"> > L< Time::HiRes > > L< perlfunc / $. > > L< > perlfunc > / > $. > > > L< perlpodspec / " About LE<lt>...E<gt> Codes "> > > What I'm currently implementing retains the behavior of stripping off > surrounding double-quotes from the section, as well as leading or trailing > whitespace inside or outside the double-quotes. It also interprets L<> > entries that are fully contained in double-quotes as links to sections for > backward compatibility, not just looking at internal whitespace. > > I'm implementing a parser that breaks down link text into the five items > described here and will include it in the next release of podlators. > (Called Pod::ParseLink.) >
Russ, Why don't you use Pod::ParseUtils that is already in the core and does exactly what you want (although it will need updating to match any changes to L<>). I think that releasing a new link parser is sure to confuse people (and we don't really want two link parsers in the core distribution). > -- Tim Jenness JAC software http://www.jach.hawaii.edu/~timj
