Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[5.005_63] pod problems #975

p5pRT opened this issue Dec 19, 1999 · 1 comment

[5.005_63] pod problems #975

p5pRT opened this issue Dec 19, 1999 · 1 comment


Copy link

p5pRT commented Dec 19, 1999

Migrated from (status was 'resolved')

Searchable as RT1923$

Copy link

p5pRT commented Dec 19, 1999

From @vanstyn


The latest pod2man using Pod​::Man and Pod​::Parser highlights some
problems during installation.

The majority of the problems revolve around the enhancement to permit
'->' and '=>' to appear within a pod escape without terminating it;
there are a number of examples in the current pods where such sequences
appear and _are_ intended to terminate the escape. Here is the first
example, from perldebug.pod​:

  List lines C<min> through C<max>. C<l -> is synonymous to C<->.

Each such example results in a warning during installation; the full
list (though I haven't checked them all) is​:

** Unterminated C<...> at perldebug.pod line 148
** Unterminated C<...> at perldelta.pod line 1920
** Unterminated C<...> at perldiag.pod line 3102
** Unterminated C<...> at perlport.pod line 1497
** Unterminated C<...> at perlvar.pod line 188
** Unterminated C<...> at perlvar.pod line 188
** Unterminated C<...> at perlvar.pod line 424
** Unterminated C<...> at perlos2.pod line 1139
** Unterminated C<...> at File/ line 241
** Unterminated C<...> at Class/ line 358
** Unterminated C<...> at Class/ line 373

I think it would be helpful if, on detecting a termination error,
Pod​::Parser were to attempt to reparse the line without the ARROW_RE
check to see if that permits the line to be parsed properly; I'm not
sure how easy that would be, nor whether the consequences would be
desirable in all cases.

One other error was reported, from Pod​::Man​::cmd_back()​:

Unmatched =back at ../pod/pod2man line 40

It is unfortunate that this uses a simple 'carp' rather than the
errorsub() mechanism - I'm not sure if there is some reason it can't
do that - but the problem turned out to be in pod/perlos2.pod, which
has 17 '=over' directives and 18 '=back'.


Perl Info

Site configuration information for perl 5.00563:

Configured by hv at Sat Dec 11 09:36:24 GMT 1999.

Summary of my perl5 (revision 5.0 version 5 subversion 63) configuration:
    osname=linux, osvers=2.2.5-16, archname=i686-linux
    uname='linux 2.2.5-16 #1 sun may 30 23:00:18 bst 1999 i686 unknown '
    config_args='-des -Doptimize=-g -O6 -Dprefix=/opt/perl5.005_63'
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef useperlio=undef d_sfio=undef
    use64bits=undef usemultiplicity=undef
    cc='cc', optimize='-g -O6', gccversion=egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
    cppflags='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing'
    ccflags ='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing'
    stdchar='char', d_stdstdio=define, usevfork=false
    intsize=4, longsize=4, ptrsize=4, doublesize=8
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
    alignbytes=4, usemymalloc=n, prototype=define
  Linker and Libraries:
    ld='cc', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /lib /usr/lib
    libs=-lnsl -lndbm -lgdbm -ldb -ldl -lm -lc -lposix -lcrypt
    libc=/lib/, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
    cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'

Locally applied patches:

@INC for perl 5.00563:

Environment for perl 5.00563:
    LANG (unset)
    LANGUAGE (unset)
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PERL_BADLANG (unset)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant