in reply to Re^2: Unpack unexpectedly trimming trailing spaces
in thread Unpack unexpectedly trimming trailing spaces

... I did look pretty carefully in the Camel ...

As a general rule, I think it's best to look at the on-line pack documentation or, better yet, at your local perldoc -f pack (and see also perlpacktut).

Give a man a fish:  <%-{-{-{-<

Replies are listed 'Best First'.
Re^4: Unpack unexpectedly trimming trailing spaces
by stevieb (Canon) on Nov 20, 2015 at 22:14 UTC
    Even though unpack states to look to pack for further info, would it be a sensible use of time if I updated unpack to reflect at least info that's directly relevant? Thoughts?

    My thinking is that it might not be overly clear if someone uses unpack without using pack first.

[reply]
[d/l]
[select]
      ... info that's directly relevant ...

      Info that's directly relevant to unpack? The unpack docs already seem to have a lot (all?) of that. What did you have in mind? The first sentence in unpack already says "unpack does the reverse of pack ...". There is little discussion of the  TEMPLATE and its specifiers, but then in the fourth paragraph, this: 'The TEMPLATE has the same format as in the "pack" function.'

      It might be more newbie-frendly if, in each pack/unpack documentation entry, there were, very close to the beginning, a paragraph to the effect

      "pack and unpack are complementary functions; please consult (un)pack and perlpacktut for a full understanding of these functions."
      but I'm not sure this would necessarily be much more helpful than what is already there; at some point, one must just carefully RTFM.

      Update: Fixed mispeling: complemenetary vice complementary.

      Give a man a fish:  <%-{-{-{-<

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom