Linux 4GL convert-"matches" problem
4GL 7.3 on Linux has a problem compiling this. . . CASE WHEN fieldName MATCHES "col.titles\\[[123]\\].*" unexpected character "[" after "\\" This code has compiled on 3 completely different environments during various versions in the last 10 years. It is obviously not valid to escape a "[" or "]", anymore. Ok. So what is the solution. In this particular instance changing source code would be a monumental job. -- mkuhn@rhlab.com
The online 4gl manual does indicate that the special characters in the "matches" can be escaped. This appears to be a problem, that I hope someone has a workaround for. Mike Kuhn wrote: > > 4GL 7.3 on Linux has a problem compiling this. . . > > CASE > WHEN fieldName MATCHES "col.titles\\[[123]\\].*" > > unexpected character "[" after "\\" > > This code has compiled on 3 completely different > environments during various versions in the last > 10 years. > > It is obviously not valid to escape a "[" or "]", anymore. > > Ok. So what is the solution. > > In this particular instance changing source code would > be a monumental job. > > -- > mkuhn@rhlab.com -- mkuhn@rhlab.com
Mike, I had a similar problem with PHP4 on RedHat Linux 7.0. A PHP application complained about bad regular expressions. The solutions was to install a new glibc (2.1.94) and the error went away. Hope this helps. Paul "Mike Kuhn" <mkuhn@rhlab.com> schrieb im Newsbeitrag news:3A797AE0.F4AD51FA@rhlab.com... > 4GL 7.3 on Linux has a problem compiling this. . . > > CASE > WHEN fieldName MATCHES "col.titles\\[[123]\\].*" > > unexpected character "[" after "\\" > > This code has compiled on 3 completely different > environments during various versions in the last > 10 years. > > It is obviously not valid to escape a "[" or "]", anymore. > > Ok. So what is the solution. > > In this particular instance changing source code would > be a monumental job. > > > > -- > mkuhn@rhlab.com