--- In [email protected], "entropyreduction"
<alancampbelllists+ya...@...> wrote:
>
> Just a reminder: even now regex only _attempts_ to load unicode
> plugin. If it fails, no problem, it just never looks for a
> unicode handle in pattern, subject, or replacement string. So not
> sure I see advantage of not attempting to find unicode plugin.
>
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.
> 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. Since the setting is manipulated by the unicode plugin, regex could
have a reasonable expectation that if enabled, the unicode plugin is loaded.
Regards,
Sheri
>
> --- In [email protected], "Sheri" <sherip99@> wrote:
>
> > BTW, would it be feasible to remove auto-loading of unicode from
> > regex plugin? Instead of giving a unicode handle as subject (for
> > regex.pcre_functions), it is straightforward to use
> > unicode.to_utf8(handle) instead. The possibility to use the
> > actual handle was never documented, so I highly doubt anyone is
> > using that feature. Even if the feature is retained, the user
> > would obviously need to use the unicode plugin (and thereby load
> > it him or herself) in order to create the unicode handle/string
> > wanted for use as a regex subject.
