473,320 Members | 1,853 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

regexp validator - wrong?

ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any values) - this is wrong
d+ expression does not match, for example "g24" string - this is also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is reporting "not match" for the first one and "match" for the second one. I am suspecting using different framework version from regexplib, and this being the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #1
8 1991
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it does not
match "g24". You probably intended "^\w+$", meaning a single line string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second one. I am
suspecting using different framework version from regexplib, and this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #2
Thanks Steve.

1) Why the first example works the opposite (to what I see and what you have explained) at www.regexplib.com ? They have set up a testing area where you can test various regexps and see if they match or not the strings you enter.

2) \d+ means one or more digits. They can be anywhere within the string. This means "g2323" should match the regular expression, but it doesn't (although it does on the testing area of www.regexplib.com and in any other regexp-compatible language). Note that if I wanted a string which contains digits only, I'd use ^\d+$ regexp.

So I guess there should be some more ideas...

P.S. I'm still thinking of the different versions of the framework.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"Steve Jansen" <st*****@dev.nul> wrote in message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it does not
match "g24". You probably intended "^\w+$", meaning a single line string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second one. I am
suspecting using different framework version from regexplib, and this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #3
Obviously I made a typo in the initial message, there should be \d+ instead of just d+

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"Steve Jansen" <st*****@dev.nul> wrote in message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it does not
match "g24". You probably intended "^\w+$", meaning a single line string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second one. I am
suspecting using different framework version from regexplib, and this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #4
1) .NET defines what it means for the regular expression validator to fire. And it ignores the empty string. The documentation says so - and it says to use a required field validator in addition, if your requirements are that the field be filled in.

How others chose to implement their regular expression validator is irrelevant.

2) '\d+' means that the entire string is just one or more digits. Not that there exists a substring of the original string with one or more digits.

The link you keep referring to, seems to see if there is a substring that matches.

For example, I put in '\d' for the expression, and 'asdf2sdf' for the test string.

Now, in reality, '\d' should only match a 1 character string that contains a digit. However, my string matched!

I disagree that this is actually a regular expression match for the string. There is a substring of my string that matches - but not the entire thing. In fact, absolutely anything will match, as long as there is at least one digit somewhere in it.

So the result from this web site is very misleading, and as far as I am concerned incorrect. If I am validating that someone enters a 5 digit zip code, but something 'a string 12345' is allowed to match - well, that's just plain wrong!
"Dmitry Korolyov [MVP]" <d_**@removethispart.mail.ru> wrote in message news:%2****************@tk2msftngp13.phx.gbl...
Thanks Steve.

1) Why the first example works the opposite (to what I see and what you have explained) at www.regexplib.com ? They have set up a testing area where you can test various regexps and see if they match or not the strings you enter.

2) \d+ means one or more digits. They can be anywhere within the string. This means "g2323" should match the regular expression, but it doesn't (although it does on the testing area of www.regexplib.com and in any other regexp-compatible language). Note that if I wanted a string which contains digits only, I'd use ^\d+$ regexp.

So I guess there should be some more ideas...

P.S. I'm still thinking of the different versions of the framework.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"Steve Jansen" <st*****@dev.nul> wrote in message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it does not
match "g24". You probably intended "^\w+$", meaning a single line string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second one. I am
suspecting using different framework version from regexplib, and this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #5
Agree on the first one - if that is how it works by design. Yet it is still wrong from the position of the common sense. Since an empty string does not contain one or more digits, it should not match the regexp, still it does.

"How others chose to implement their regular expression validator is irrelevant." umm well if you say so. I've used regexp with perl some time before the whole .NET thing was here. And

And disagree on the second. '\d+' means a sting containing 1 or more digits anywhere. An entire string which contains only digits - that would be '^\d+$'. Therefore, regexp is handled incorrect here also. You're making wrong assumtions regarding the entire string thing. The entire string consists of:
1. Start of the string. This is '^' character in regular expressions syntax (if placed at the very beginning of the regular expression)
2. The string itself. This is the '\d+' pattern we use for "one or more digits"
3. End of the string. This is '$' character in regular expressions sytnax (if placed at the very end of the regular expression).
This is documented in .NET regexp help so you can look yourself.

In other words, 'asdf2sdf' will match the '\d' regexp as this is a string which contains a digit. If you need a regexp for 5-digit zip code, you should use ^\d\d\d\d\d$ or ^\d{5}$ pattern. The test area at www.regexplib.com returns absolutely correct results - in terms of what is referred to as "regular expressions" by anyone who works with regular expressions. In my initial message I was wondering why my .NET framework gives incorrect results, and my suggestion is that the website uses some different version.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"Marina" <nospam> wrote in message news:u1**************@tk2msftngp13.phx.gbl...
1) .NET defines what it means for the regular expression validator to fire. And it ignores the empty string. The documentation says so - and it says to use a required field validator in addition, if your requirements are that the field be filled in.

How others chose to implement their regular expression validator is irrelevant.

2) '\d+' means that the entire string is just one or more digits. Not that there exists a substring of the original string with one or more digits.

The link you keep referring to, seems to see if there is a substring that matches.

For example, I put in '\d' for the expression, and 'asdf2sdf' for the test string.

Now, in reality, '\d' should only match a 1 character string that contains a digit. However, my string matched!

I disagree that this is actually a regular expression match for the string. There is a substring of my string that matches - but not the entire thing. In fact, absolutely anything will match, as long as there is at least one digit somewhere in it.

So the result from this web site is very misleading, and as far as I am concerned incorrect. If I am validating that someone enters a 5 digit zip code, but something 'a string 12345' is allowed to match - well, that's just plain wrong!
"Dmitry Korolyov [MVP]" <d_**@removethispart.mail.ru> wrote in message news:%2****************@tk2msftngp13.phx.gbl...
Thanks Steve.

1) Why the first example works the opposite (to what I see and what you have explained) at www.regexplib.com ? They have set up a testing area where you can test various regexps and see if they match or not the strings you enter.

2) \d+ means one or more digits. They can be anywhere within the string. This means "g2323" should match the regular expression, but it doesn't (although it does on the testing area of www.regexplib.com and in any other regexp-compatible language). Note that if I wanted a string which contains digits only, I'd use ^\d+$ regexp.

So I guess there should be some more ideas...

P.S. I'm still thinking of the different versions of the framework.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"Steve Jansen" <st*****@dev.nul> wrote in message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it does not
match "g24". You probably intended "^\w+$", meaning a single line string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com test validator works fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second one. I am
suspecting using different framework version from regexplib, and this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
Nov 17 '05 #6
Dmitry Korolyov [MVP] wrote:
Thanks Steve.

1) Why the first example works the opposite (to what I see and what you
have explained) at www.regexplib.com <http://www.regexplib.com> ? They
have set up a testing area where you can test various regexps and see if
they match or not the strings you enter.

The RegularExpressionValidator is documented to succeed if the input
control is empty (ie., the Regexp is not even run in this case). That
might not be intuitive for you, but it's how MS decided it should work.
2) \d+ means one or more digits. They can be anywhere within the string.
This means "g2323" should match the regular expression, but it doesn't
(although it does on the testing area of
<http://www.regexplib.com> www.regexplib.com <http://www.regexplib.com>
and in any other regexp-compatible language). Note that if I wanted a
string which contains digits only, I'd use ^\d+$ regexp.

So I guess there should be some more ideas...
Looking at the IL for the RegularExpressionValidator, it appears that MS
made an undocumented decision such that it will return a successful
validation only when the regex matches the entire contents of the control.

I'd agree with you that this is counter-intuitive, and it appears to be
undocumented. I'm not sure whether MS would consider this a bug in
implementation or a bug in documentation. In any case, the behavior
exists in both current versions of the Framework (1.0 SP2 and 1.1).

So, if you want your Regex's to match with the behavior that MS
hard-coded for RegularExpressionValidator, the ValidationExpression
should always be bounded by the ^ and $ characters.

P.S. I'm still thinking of the different versions of the framework.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory

"Steve Jansen" <st*****@dev.nul <mailto:st*****@dev.nul>> wrote in
message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a
value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it
does not
match "g24". You probably intended "^\w+$", meaning a single line
string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru
<mailto:d_**@removethispart.mail.ru>> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't
enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com <http://www.regexplib.com> test validator works
fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second
one. I am
suspecting using different framework version from regexplib, and
this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory


--
mikeb

Nov 17 '05 #7
That's warmer Mike. But regexplib website shows us absolutely correct behavior - or do they use custom handling?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory
"mikeb" <ma************@mailnull.com> wrote in message news:OV**************@tk2msftngp13.phx.gbl...
Dmitry Korolyov [MVP] wrote:
Thanks Steve.

1) Why the first example works the opposite (to what I see and what you
have explained) at www.regexplib.com <http://www.regexplib.com> ? They
have set up a testing area where you can test various regexps and see if
they match or not the strings you enter.

The RegularExpressionValidator is documented to succeed if the input
control is empty (ie., the Regexp is not even run in this case). That
might not be intuitive for you, but it's how MS decided it should work.
2) \d+ means one or more digits. They can be anywhere within the string.
This means "g2323" should match the regular expression, but it doesn't
(although it does on the testing area of
<http://www.regexplib.com> www.regexplib.com <http://www.regexplib.com>
and in any other regexp-compatible language). Note that if I wanted a
string which contains digits only, I'd use ^\d+$ regexp.

So I guess there should be some more ideas...
Looking at the IL for the RegularExpressionValidator, it appears that MS
made an undocumented decision such that it will return a successful
validation only when the regex matches the entire contents of the control.

I'd agree with you that this is counter-intuitive, and it appears to be
undocumented. I'm not sure whether MS would consider this a bug in
implementation or a bug in documentation. In any case, the behavior
exists in both current versions of the Framework (1.0 SP2 and 1.1).

So, if you want your Regex's to match with the behavior that MS
hard-coded for RegularExpressionValidator, the ValidationExpression
should always be bounded by the ^ and $ characters.

P.S. I'm still thinking of the different versions of the framework.

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory



"Steve Jansen" <st*****@dev.nul <mailto:st*****@dev.nul>> wrote in
message news:uv**************@TK2MSFTNGP10.phx.gbl...
Per MSDN on the RegularExpressionValidatorControl:

"Note: Validation succeeds if the input control is empty. If a
value is
required for the associated input control, use a RequiredFieldValidator
control in addition to the RegularExpressionValidator control."

This is why it appears ^\d+$ is matched with an empty string.

Also, "d+" means match one or more "d" characters, which is why it
does not
match "g24". You probably intended "^\w+$", meaning a single line
string
with only alphanumerics [a-zA-Z_0-9].

-Steve Jansen

---------------------------
"Dmitry Korolyov" <d_**@removethispart.mail.ru
<mailto:d_**@removethispart.mail.ru>> wrote in message
news:%2***************@TK2MSFTNGP10.phx.gbl...
ASP.NET app using c# and framework version 1.1.4322.573 on a IIS 6.0 web
server.

A single-line asp:textbox control and regexp validator attached to it.

^\d+$ expression does match an empty string (when you don't
enter any
values) - this is wrong
d+ expression does not match, for example "g24" string - this is
also wrong

www.regexplib.com <http://www.regexplib.com> test validator works
fine for both cases, i.e. it is
reporting "not match" for the first one and "match" for the second
one. I am
suspecting using different framework version from regexplib, and
this being
the source of the error. Do you have any other ideas?

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory


--
mikeb

Nov 17 '05 #8
Dmitry Korolyov [MVP] wrote:
That's warmer Mike. But regexplib website shows us absolutely correct
behavior - or do they use custom handling?

There's extra code in the handling of the RegularExpressionValidator.
Pseudo-code looks something like:

string len = controlToValidate.Text.Length;

if (len == 0) {
// nothing in the control - automatically validated
return( true);
}

Match m = regex.Match( controlToValidate.Text);

if (m.Success && (m.Length == len)) {
return( true);
}

return( false);

--
Dmitry Korolyov [d_**@removethispart.mail.ru]
MVP: Windows Server - Active Directory

"mikeb" <ma************@mailnull.com
<mailto:ma************@mailnull.com>> wrote in message
news:OV**************@tk2msftngp13.phx.gbl...
Dmitry Korolyov [MVP] wrote:
> Thanks Steve.
>
> 1) Why the first example works the opposite (to what I see and

what you
> have explained) at www.regexplib.com <http://www.regexplib.com>

<http://www.regexplib.com> ? They
> have set up a testing area where you can test various regexps and

see if
> they match or not the strings you enter.
>


The RegularExpressionValidator is documented to succeed if the input
control is empty (ie., the Regexp is not even run in this case). That
might not be intuitive for you, but it's how MS decided it should work.
> 2) \d+ means one or more digits. They can be anywhere within the

string.
> This means "g2323" should match the regular expression, but it

doesn't
> (although it does on the testing area of
> <http://www.regexplib.com> www.regexplib.com

<http://www.regexplib.com> <http://www.regexplib.com>
> and in any other regexp-compatible language). Note that if I

wanted a
> string which contains digits only, I'd use ^\d+$ regexp.
>
> So I guess there should be some more ideas...


Looking at the IL for the RegularExpressionValidator, it appears
that MS
made an undocumented decision such that it will return a successful
validation only when the regex matches the entire contents of the
control.

I'd agree with you that this is counter-intuitive, and it appears to be
undocumented. I'm not sure whether MS would consider this a bug in
implementation or a bug in documentation. In any case, the behavior
exists in both current versions of the Framework (1.0 SP2 and 1.1).

So, if you want your Regex's to match with the behavior that MS
hard-coded for RegularExpressionValidator, the ValidationExpression
should always be bounded by the ^ and $ characters.
>
> P.S. I'm still thinking of the different versions of the framework.
>
> --
> Dmitry Korolyov [d_**@removethispart.mail.ru]
> MVP: Windows Server - Active Directory
>
>
>
> "Steve Jansen" <st*****@dev.nul <mailto:st*****@dev.nul>

<mailto:st*****@dev.nul>> wrote in
> message news:uv**************@TK2MSFTNGP10.phx.gbl...
> Per MSDN on the RegularExpressionValidatorControl:
>
> "Note: Validation succeeds if the input control is empty. If a
> value is
> required for the associated input control, use a

RequiredFieldValidator
> control in addition to the RegularExpressionValidator control."
>
> This is why it appears ^\d+$ is matched with an empty string.
>
> Also, "d+" means match one or more "d" characters, which is

why it
> does not
> match "g24". You probably intended "^\w+$", meaning a

single line
> string
> with only alphanumerics [a-zA-Z_0-9].
>
> -Steve Jansen
>
> ---------------------------
> "Dmitry Korolyov" <d_**@removethispart.mail.ru

<mailto:d_**@removethispart.mail.ru>
> <mailto:d_**@removethispart.mail.ru>> wrote in message
> news:%2***************@TK2MSFTNGP10.phx.gbl...
> ASP.NET app using c# and framework version 1.1.4322.573 on a

IIS 6.0 web
> server.
>
> A single-line asp:textbox control and regexp validator

attached to it.
>
> ^\d+$ expression does match an empty string (when you don't
> enter any
> values) - this is wrong
> d+ expression does not match, for example "g24"

string - this is
> also wrong
>
> www.regexplib.com <http://www.regexplib.com>

<http://www.regexplib.com> test validator works
> fine for both cases, i.e. it is
> reporting "not match" for the first one and "match" for the

second
> one. I am
> suspecting using different framework version from regexplib, and
> this being
> the source of the error. Do you have any other ideas?
>
> --
> Dmitry Korolyov [d_**@removethispart.mail.ru]
> MVP: Windows Server - Active Directory
>


--
mikeb


--
mikeb

Nov 17 '05 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

10
by: Andrew DeFaria | last post by:
I was reading my O'Reilly JavaScript The Definitive Guide when I came across RegExp and thought I could tighten up my JavaScript code that checks for a valid email address. Why does the following...
24
by: Nick Kew | last post by:
There's a new beta of the W3C Markup Validation Service now live at <URL:http://validator.w3.org:8001/> Probably the most important change is verbose output, including attempts to explain the...
195
by: Torbjørn Pettersen | last post by:
As you might have noticed I'm trying to clean up my web site's HTML code. The way I do it is simply more or less redoing to complete site, testing it on a web server I have set up on my local...
6
by: Edward | last post by:
I need to validate a text box entry, but ONLY if it is 17 characters, otherwise I have to ignore it. My regular expression for the validation is: ^(({9})()()(\d{6}))$ Can I adapt this to...
7
by: Csaba Gabor | last post by:
I need to come up with a function function regExpPos (text, re, parenNum) { ... } that will return the position within text of RegExp.$parenNum if there is a match, and -1 otherwise. For...
23
by: codefire | last post by:
Hi, I am trying to get a regexp to validate email addresses but can't get it quite right. The problem is I can't quite find the regexp to deal with ignoring the case james..kirk@fred.com, which...
2
by: Nathan Sokalski | last post by:
I have the following script that I am using to test some JavaScript RegExp code: function RE() { var testing1=new RegExp("*"); var testing2=new RegExp("{0,}"); var testing3=new RegExp("+");...
4
by: Matt | last post by:
Hello all, I have just discovered (the long way) that using a RegExp object with the 'global' flag set produces inconsistent results when its test() method is executed. I realize that 'global'...
4
by: r | last post by:
Hello, It seems delimiters can cause trouble sometimes. Look at this : <script type="text/javascript"> function isDigit(s) { var DECIMAL = '\\.'; var exp = '/(^?0(' + DECIMAL
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
0
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: af34tf | last post by:
Hi Guys, I have a domain whose name is BytesLimited.com, and I want to sell it. Does anyone know about platforms that allow me to list my domain in auction for free. Thank you

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.