--- In [email protected], "Sheri" <sheri...@...> wrote: > > That would make the only remaining issue with regex relative to > the older release: creation of unknown local variables. Would be > nice to find that, though Bruce pointed out the possibility for > users to move all command list calls to regex.pcreservices into > scripts. >
By debugging content of regex variables at various times with the old and new, I figured out the difference is treatment of regex_status. With the old regex release, the predeclared global variable regex_status gets updated when using regex.pcreservices unless a local regex_status also exists. If no global variable exists, the user needs to declare a script variable. But, if not created by the user as a local or global variable and not referenced by name, there is no error. So at least sometimes no regex_status variable is needed unless referenced by user by name. If user has created global and local regex_status, local one is updated. With the test version, any existing global regex_status variable is being ignored. The test plugin tries to create a local variable. It succeeds in script context, so (at least in scripts) the user can retrieve it by name without having declared it himself. Regards, Sheri
