Skip Menu |

This queue is for tickets about the MP3-Tag CPAN distribution.

Report information
The Basics
Id: 49849
Status: open
Priority: 0/
Queue: MP3-Tag

People
Owner: Nobody in particular
Requestors: BitCard [...] ResonatorSoft.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in:
  • 0.90
  • 0.91
  • 0.92
  • 0.93
  • 0.94
  • 0.95
  • 0.96
  • 0.97
  • 0.9701
  • 0.9702
  • 0.9703
  • 0.9704
  • 0.9705
  • 0.9706
  • 0.9707
  • 0.9708
  • 0.9709
  • 0.9710
  • 0.9712
  • 0.9713
  • 0.9714
  • 1.00
  • 1.10
  • 1.11
Fixed in: (no value)



Subject: Docs have wrong example for ID3v2 tag reading
In the MP3::Tag::ID3v2 docs, the section called: * Reading a tag, very low-level: There is a line that says: my ($name, @info) = $id3v2->get_frame($frame); However, according to your own docs further down, this is the wrong subroutine to report those variables. It should be get_frames, with the s: ($name, @info) = get_frames($ID); ($name, @info) = get_frames($ID, 'raw'); Same as get_frame() with different order of the returned values. $name and elements of the array @info have the same semantic as for get_frame(); each frame with id $ID produces one elements of array @info.
CC: undisclosed-recipients: ;
Subject: Re: [rt.cpan.org #49849] Docs have wrong example for ID3v2 tag reading
Date: Mon, 21 Sep 2009 17:05:58 -0700
To: Brendan Byrd via RT <bug-MP3-Tag [...] rt.cpan.org>
From: Ilya Zakharevich <nospam-abuse [...] ilyaz.org>
On Sat, Sep 19, 2009 at 08:53:16PM -0400, Brendan Byrd via RT wrote: Show quoted text
> In the MP3::Tag::ID3v2 docs, the section called: > > * Reading a tag, very low-level: > > There is a line that says: > > my ($name, @info) = $id3v2->get_frame($frame); > > However, according to your own docs further down, this is the wrong > subroutine to report those variables. It should be get_frames, with the s: > > ($name, @info) = get_frames($ID); > ($name, @info) = get_frames($ID, 'raw'); > > Same as get_frame() with different order of the returned values. $name > and elements of the array @info have the same semantic as for > get_frame(); each frame with id $ID produces one elements of array @info.
Confirmed, and fixed in my local version (tobe 1.12). A lot of thanks, Ilya
Looks like this is still a bug in the latest version.