Re: [ jEdit-devel ] gnu.regex must stay (for now)

[Alan E. <ala...@gm...>]

I still am worried about the stability of jedit, for depending on
java.util.regex for its mode parsing.  Are there any other mode files
that cause this? I don't know, but I only use popular open-source
modes, and there are LOTS of mode files that would need to be looked
at and manually debugged... Anyone who is debugging these mode files
doesn't want to have to deal with lockups IN ADDITION to the other
parse errors that can be caused by either xml or regex being
incorrect.

Jedit is normally rock-solid stable, and it should never lockup like this.

Here's an idea:

<MODE REGEX="gnu">
<!-- all regexes are parsed by gnu.regexp instead of java.util -->
</MODE>

I know getting this to work will be a bit of effort, but those lockups
are driving me nuts.

On 6/24/06, Marcelo Vanzin <va...@us...> wrote:
> Also note that if you change "substr" to just "tr" then the rule will
> fire and the regex will go into "infinite loop" mode. So we still need
> to fix the regex.
>
> Marcelo Vanzin wrote:
> > You're right! :-)
> >
> > I fixed the mode parser and now that snippet doesn't cause any problems
> > for me. Could you sync up to CVS and try it?
> >
> >> my $prevpos = 0;
> >>
> >> sub FIRSTKEY {
> >>    $prevpos = 0;
> >>    substr($Config_SH_expanded, 1, index($Config_SH_expanded, '=') - 1 );
> >> }
>
>
> --
> Marcelo Vanzin
> va...@us...
> "Life is too short to drink cheap beer"
>