Re: replacing the monster regex

[Derek Pomery <pomerydc@thc-tsg.com>]

Well, I ended up with it locating 30 matches in 0 files, 1 match in 0 
files, etc etc.
Trying to figure out what is going wrong, which should be easier in the 
much better commented and debugable code.

Say, do you use AIM, Yahoo!, or ICQ?  Might be faster than e-mail (plus 
the fact some of my e-mails repeatedly bounced last week)

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 1/29/02, 11:18:55 AM, Derek Pomery <pomerydc@thc-tsg.com> wrote 
regarding Re: replacing the monster regex:


> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

> On 1/29/02, 2:17:10 AM, "Golda Velez" <golda@iwhome.com> wrote regarding
> replacing the monster regex:


> > Ok, I think I've got the replacement done, just need to test some - one
> question, though

> > What did you mean by "the splits work much better when the substr() is
> removed"?  Unless >maxchars was set very low, the substr should not have
> affected the part of the line that we're >actually splitting up...did you
> maybe have it set low, or what errors did you get?

> What I got was consistently broken links.  Over n over.  I couldn't
> figure out why it wasn't parsing the filename correctly.  Until I took
> out the substr() -  I had not modified the default value, either.
> However, when you have a path like:
> http://thiserver.thislongveryverylongdomainname.net/project/subproject/s
> ubsubproject/somefurtherdivision/andanother/oneortwo/forfurtherorganizat
> ion/A ridiculously long file name that describes exactly what the use
> case is.html

> I was finding it was unsurprisingly breaking the splits || regex.
> Hadn't gone back to see what the actual value for the substr was, since
> everything worked fine without it. :)




> * Will paste this into my version, and see what happens :)
> > Here's the replacement code (which still needs to be tested), now off in
> a subroutine:
> > --------------------------

> > ------------------------------

> > Thanks again for your suggestion, I need to do a bunch of testing and
> integrate a few other changes, it will be about a week before the next
> actual release, I think.

> > --G