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

Documentation bug in 5.005_03 #391

Closed
p5pRT opened this issue Aug 17, 1999 · 1 comment
Closed

Documentation bug in 5.005_03 #391

p5pRT opened this issue Aug 17, 1999 · 1 comment

Comments

@p5pRT
Copy link

p5pRT commented Aug 17, 1999

Migrated from rt.perl.org#1226 (status was 'resolved')

Searchable as RT1226$

@p5pRT
Copy link
Author

p5pRT commented Aug 17, 1999

From neufeld@physics.utoronto.ca

The section as follows​:

=== BEGIN INCLUDED TEXT ===

You are guaranteed that if you concatenate *path*, *name*, and
*suffix* together in that order, the result will be identical to the
input file specification.

EXAMPLES

Using UNIX file syntax​:

  ($base,$path,$type) = fileparse('/virgil/aeneid/draft.book7',
  '\.book\d+');

would yield

  $base eq 'draft'
  $path eq '/virgil/aeneid',
  $tail eq '.book7'

=== END INCLUDED TEXT ===

This section is internally inconsistent. Specifically, if you concatenate
$base, $path, and $tail together, you don't get back the original text,
you're missing the '/' after "aeneid".

Also, that shouldn't be "$tail", that should be "$type".

--
Christopher Neufeld neufeld@​physics.utoronto.ca
Home page​: http​://caliban.physics.utoronto.ca/neufeld/Intro.html
"Don't edit reality for the sake of simplicity"

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

No branches or pull requests

1 participant