On Wed, Aug 18, 2004 at 03:34:11PM -0500, [EMAIL PROTECTED] wrote:
> MARC::Field->as_string() takes a string of subfields rather than an array.
> It would be better for as_string() and delete_subfields() to have the same
> interface. Since as_string() is used a lot i
On Wed, Aug 18, 2004 at 03:34:11PM -0500, [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> MARC::Field->as_string() takes a string of subfields rather than an array.
> It would be better for as_string() and delete_subfields() to have the same
> interface. Since as_string() is u
MARC::Field->as_string() takes a string of subfields rather than an array.
It would be better for as_string() and delete_subfields() to have the same
interface. Since as_string() is used a lot in production,
delete_subfields() should be the one to change.
Mike O&#x
Jackie Shieh at Univ of Michigan thought it would be handy to have a
delete_subfields() method on MARC::Field objects. Basically the
method takes a list of subfields to delete, and deletes each one,
returning the total subfields that were removed. If a subfield
repeats all of them are deleted
