Skip Menu |

This queue is for tickets about the XML-SAX-Writer CPAN distribution.

Report information
The Basics
Id: 91382
Status: resolved
Priority: 0/
Queue: XML-SAX-Writer
People
Owner: cpan [...] prather.org
Requestors: herve [...] guillemet.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Fri Dec 13 08:28:47 2013 herve [...] guillemet.org - Ticket created
Subject: Bug in XML::SAX::Writer::escape
Date: Fri, 13 Dec 2013 14:28:28 +0100
To: bug-XML-SAX-Writer [...] rt.cpan.org
From: Hervé Guillemet <herve [...] guillemet.org>
Hi, In sub escape from XML/SAX/Writer.pm, there is : $str =~ s/($self->{EscaperRegex})/$self->{Escape}->{$1}/oge; In my application I have several writers that may not be initialized with the same Escape hash, thus not the same EscaperRegex. The /o option in the line above causes the first escaping rule being used to be applied to all subsequent escapes fromm all writers, which is not what is expected. Could you release a new version with a fix ? Thanks, -- Hervé
  Fri Dec 13 12:45:47 2013 cpan [...] prather.org - Correspondence added
On Fri Dec 13 08:28:47 2013, herve@guillemet.org wrote: Show quoted text
> > Hi, > > In sub escape from XML/SAX/Writer.pm, there is : > > $str =~ s/($self->{EscaperRegex})/$self->{Escape}->{$1}/oge; > > In my application I have several writers that may not be initialized > with the same Escape hash, thus not the same EscaperRegex. > The /o option in the line above causes the first escaping rule being > used to be applied to all subsequent escapes fromm all writers, which is > not what is expected. > > Could you release a new version with a fix ? > > Thanks, >
This should be fixed in 0.54 that just got pushed. -Chris
  Fri Dec 13 12:45:48 2013 The RT System itself - Status changed from 'new' to 'open'
  Fri Dec 13 12:45:48 2013 cpan [...] prather.org - Status changed from 'open' to 'resolved'
  Fri Dec 13 12:45:48 2013 cpan [...] prather.org - Taken