--- In [email protected], "Sheri" <sheri...@...> wrote:
>
> --- In [email protected], "entropyreduction"
> <alancampbelllists+yahoo@> wrote:
> Its even checking the pattern for unicode handles? I'm not sure unicode
> handles are sensible anywhere except as the subject. I hope this had nothing
> to do with the failure of callouts back when.
Probably not related.
If you've got unicode subjec,t why wouldn't one want to search it with a
unicode pattern?
> > If you want it not to, I'll put it under control of an config ini
> > file setting.
> OK. Please make it default to off. Can achieve the same now only by renaming
> the unicode plugin prior to starting Powerpro. Its an all or nothing approach.
> Suppose instead there was a global variable that could be set/unset with a
> new unicode service, e.g.,
> unicode.toregex("on")
> unicode.toregex("off")
> If would default to off, and unicode.unload would always set it off.
> While enabled, regex would be checking for unicode handles. This would be
> better than all or none, because the user could enable the setting only if
> and when actually needed, and could still use the unicode plugin for other
> purposes.
Sorry, I'm missing something. Why can't unicode plugin be used for
whatever you want to use it for even if regex plugin makes calls to it now and
again? Have you found some problem with doing so?
> Since the setting is manipulated by the unicode plugin, regex could have a
> reasonable expectation that if enabled, the unicode plugin is loaded.
unicode plugin doesn't know it's being used by another plugin, and can't
prevent being so used.
Could be a regex service:
regex.allow_unicode_handles(0/1)
to override config ini setting -- but again, don't undertand why it should be
necessary. If for some reason you can't use unicode because regex is
interfering, there's an error of some kind in my code.
