+1
i like the approach toward standard regex.
ones that use it most likely will be sysadmins, so they should at least know
how to use regex in their tools like shell, awk, perl, python or powershell.
it will be nice if the standard regex is in place.
---
daniel baktiar
http://savinggaia.tritiumapp
I am thinking from an admin point of view. While you can combine OR
conditionals in regex's - when you get something more complicated - you
may encounter a nasty nesting of () to get all the nested OR's correct.
So while one COULD to it in a single regex - most mere mortals might not
be able to
On 25/12/2010 13:37, Konstantin Kolinko wrote:
> 1) It it were configurable, in certain places it makes sense to use
> space as a separator (e.g. in IP addresses).
> -> any whitespace? -> \w+ and we end up with using a regex to split a
> list of regexes.
Yes, space could work but I'd rather stick
On 25/12/2010 01:49, Tim Funk wrote:
> +0.5 - I wonder if in some cases - it may be preferable to use a
> property called split which lets the user define the separator which we
> can pass to String.split(). [Which OTOH may be more confusing (yet
> powerful) since the user is using a regex to split
1) It it were configurable, in certain places it makes sense to use
space as a separator (e.g. in IP addresses).
-> any whitespace? -> \w+ and we end up with using a regex to split a
list of regexes.
2) It might make sense to require regex expressions to be surrounded by '/'.
E.g. "/192\.168\.1\.
