Re: does urlregexpmapping work correctly?

some comments, in case it's helpful

Jacob Kjome <hoju@xxxxxxxx> writes:
> Hi Kyle,
> 
> At 09:21 AM 7/30/2003 -0600, you wrote:
> >I have been doing more tests on the -urlregexpmapping arg to the xmlc 
> >command. It seems that the xmlc command will support two -urlregexpmapping 
> >args but not more. To test this, I created an index.htm that has a three 
> >images in it with the urls ../images/im1.gif, ../images/im2.gif, 
> >and  ../images/im3.gif. I use three -urlregexpmapping args to replace each 
> >../images/im<num>.gif to be images/im<num>.jpg. Only two of the mappings 
> >take place. The third is ignored.

There is no restriction on the number of mappings other than physical memory.
Given the way the code is implemented, I doubt if there is a bug that cause
only two to be used.  I would suggest trying only the failed mapping
and see what happens and see what happens.

> >Also, for some reason the -urlregexpmapping does not support the lookahead 
> >feature. This feature is supported by GNU but only with the expression 
> >syntax set to Perl 5. The default xmlc is using is another syntax that 
> >does not support lookahead.
> 
> Any idea where this is set?  I haven't looked at how XMLC implements 
> -urlregexpmapping as of yet, so any pointers would be helpful.  I don't see 
> why XMLC's default shouldn't allow full functionality?  Anyone else have 
> comments on this?

The goal was to use only POSIX regular expressions.  Since it wasn't clear
that we would stick with the GNU package, non-standard features were avoided.
I believe there are incompatibilities between the posix and perl regular
expressions, so it would not be possible to simply enable them.  There
would need to be a seperate option to specify them.

Mark