|
@@ -1045,14 +1045,19 @@ config UCLIBC_HAS_REGEX
|
|
only be included in your apps if you use regular expressions.
|
|
only be included in your apps if you use regular expressions.
|
|
|
|
|
|
config UCLIBC_HAS_REGEX_OLD
|
|
config UCLIBC_HAS_REGEX_OLD
|
|
- bool "Use the older (stable) Regular Expression Support"
|
|
+ bool "Use the older (stable) regular expression code"
|
|
depends on UCLIBC_HAS_REGEX
|
|
depends on UCLIBC_HAS_REGEX
|
|
default y
|
|
default y
|
|
help
|
|
help
|
|
- POSIX regular expression code is really big -- 27k all by itself.
|
|
+ There are two versions of regex. The older (stable) version has
|
|
- If you don't use regular expressions, turn this off and save space.
|
|
+ been in uClibc for quite a long time but hasn't seen too many
|
|
- Of course, if you only staticly link, leave this on, since it will
|
|
+ updates. It also has some known issues when dealing with uncommon
|
|
- only be included in your apps if you use regular expressions.
|
|
+ corner cases and multibyte/unicode strings. However, it is quite
|
|
|
|
+ a bit smaller than the newer version.
|
|
|
|
+
|
|
|
|
+ If the older version has worked for you and you don't need unicode
|
|
|
|
+ support, then stick with the old version (and say Y here).
|
|
|
|
+ Otherwise, you should use the new version (and say N here).
|
|
|
|
|
|
config UCLIBC_HAS_WORDEXP
|
|
config UCLIBC_HAS_WORDEXP
|
|
bool "Support the wordexp() interface"
|
|
bool "Support the wordexp() interface"
|