Tom Lane wrote: > Peter, any thoughts on this one way or the other? At the moment > plpgsql's scan.l seems to be the only use of '%option > case-insensitive' but we have enough flex lexers laying about that I > wouldn't be surprised to have this same risk elsewhere. Is it > reasonable to try to force LANG=C in some global fashion during the > build?
You'd have to set LC_ALL=C to be really sure to override everything. But I would stay away from doing that globally, because all the translation work in gcc and make would go to waste. I would also suggest that Nicolai report this issue to the flex developers. It's only bound to reappear everywhere case-insensitive flex scanners are used. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
