On Fri, Dec 23, 2016 at 03:13:34PM +0000, Adam D. Barratt wrote:
> On Fri, 2016-12-23 at 08:37 -0500, James McCoy wrote:
> > On Thu, Dec 22, 2016 at 05:42:43PM -0500, Bill Blough wrote:
> > > On Thu, Dec 22, 2016 at 12:40:26PM +0000, Ian Jackson wrote:
> > > > suffers rather from leaning toothpick syndrome. Does the
> > > > `downloadurlmangle' support Perl's ability to handle nonstandard
> > > > delimiters ? Using something other than / means that / does not need
> > > > to be \-escaped. { } are often a good choice.
> > >
> > > A quick look through the uscan source suggests that it does not.
> > > However, Paul's solution is way cleaner than mine, so it's probably
> > > moot, at least in this case.
> >
> > It should be supported. The safe_replace[0] function makes no
> > assumptions about what the separator is.
> >
> > [0]:
> > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/tree/scripts/uscan.pl?id=bce34b8d7fa410e64c411bd780f8e21603167ae7#n4441
>
> Indeed. There was a fair amount of time spent during the development of
> that code to support as many native Perl features as were reasonable and
> actually used in watch files at the time (hence the \l etc support).
Apparently my "quick look through the code" was too quick. :-)
Thanks for the correction/info. That will defintely be helpful in the
future.
