J
JavaScriptDude
Well, after 5 years of using Pointy Ears's RegExp hack, I now have to
update my libraries. The original solution is here:
https://groups.google.com/group/com...e=utf-8&q=error.stack+parser#c1e442efaabfb9cd
It appears that this logic now fails as it perpetuates in the for
loop. I don't really want to troubleshoot why the regexp is now doing
this but need a fix so I can support FF 4x+ in my frameworks. I know
that someone probably has this done already.
Does anybody have any latest and greatest ways of parsing Firefox
Error.stack into usable elements: Function name, Line number, Path/
Resource that would support FF 3.6 thru FF 5?
Cheers,
JsD
update my libraries. The original solution is here:
https://groups.google.com/group/com...e=utf-8&q=error.stack+parser#c1e442efaabfb9cd
It appears that this logic now fails as it perpetuates in the for
loop. I don't really want to troubleshoot why the regexp is now doing
this but need a fix so I can support FF 4x+ in my frameworks. I know
that someone probably has this done already.
Does anybody have any latest and greatest ways of parsing Firefox
Error.stack into usable elements: Function name, Line number, Path/
Resource that would support FF 3.6 thru FF 5?
Cheers,
JsD