Hi folks,
this is preliminary information that Busybox does
not possess a full command of regular expression
to the extent desirable for the 3.1 of Bering.
I know for certain that this disturbs the validation
I have implemented for Webconf, but those of you who
rely on regular expressions in other subsystems of
Bering ought to read the following exposition.
The problem is that the regex handling in Busybox
cannot correctly resolve repetitions using "\{n\}".
The following is a reduction of the actual case
that disturbs my validation of ip-addresses inside
/var/webconf/lib/validator.sh.
firewall# ### Matches exactly {0,...,25}
firewall# tjugufem="\(1\?[0-9]\|2[0-5]\)"
firewall# ### Should match "n-m-k", where n,m,k in {0,...,25}
firewall# Trenne="$tjugufem\(-$tjugufem\)\{2\}"
firewall#
firewall# echo "25-19-25" | grep "^$Trenne$"
25-19-25
firewall# echo "25-20-25" | grep "^$Trenne$"
firewall#
Using the fullgrown sed on my Debian system, the
expected match on "25-20-25" does appear, but not
so on Bering 3.1.
It is not very probable that some other subsystem
uses this kind of regular expression, but you ought
to take this into consideration until I find time to
develop a patch for Busybox, and which still will not
take effect until next release of Bering!
Best regards
Mats Erik Andersson
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel
