Warning: ereg(): REG_BADBR

[millw0rm]

why i m getting error here???

Warning: ereg(): REG_BADBR
code:
if(!ereg("^(.){15,400}$",$string)) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}
Want to Achive:
$string is a textarea, i want the user to input atleast 15 characters
and shldnt exceed more then 400 characters!

thnx

[Kimmo Laine]

<mi******@gmail.com> wrote in message
news:11**********************@j73g2000cwa.googlegr oups.com...

why i m getting error here???

Warning: ereg(): REG_BADBR
code:
if(!ereg("^(.){15,400}$",$string)) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}
Want to Achive:
$string is a textarea, i want the user to input atleast 15 characters
and shldnt exceed more then 400 characters!

Don't know, but why would you need to use a regexp for so trivial case?
Remember the KISS rule: Keep it simple, stupid.

if( ($len = strlen($string)) < 15 || $len > 400) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}

--
"ohjelmoija on organismi joka muuttaa kofeiinia koodiksi" -lpk
sp**@outolempi.net | Gedoon-S @ IRCnet | rot13(xv***@bhgbyrzcv.arg)

[Kimmo Laine]

<mi******@gmail.com> wrote in message
news:11**********************@j73g2000cwa.googlegr oups.com...

why i m getting error here???

Warning: ereg(): REG_BADBR
code:
if(!ereg("^(.){15,400}$",$string)) {

^
It just occured to me, the dollar sign inside double quotes " " should
propably be escaped, otherwise php might confuse it for a variable marker,
but the variable is missing. for example: "$cat" replaces $cat with the
value of the variable. here you have "$". Either escape it or use single
quotes. "^(.){15,400}\$" or '^(.){15,400}$'. But as I already said, using
strlen is much more simple way. If you have to use the regular expression
(can't think of a reason why though), you can fix it with that.

--
"ohjelmoija on organismi joka muuttaa kofeiinia koodiksi" -lpk
sp**@outolempi.net | Gedoon-S @ IRCnet | rot13(xv***@bhgbyrzcv.arg)

[Schraalhans Keukenmeester]

mi******@gmail.com wrote:

why i m getting error here???

Warning: ereg(): REG_BADBR
code:
if(!ereg("^(.){15,400}$",$string)) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}
Want to Achive:
$string is a textarea, i want the user to input atleast 15 characters
and shldnt exceed more then 400 characters!

thnx

Although I am all pro-serverside coding, I'd rather implement these
simple input type checks on the client side, using Javascript. Much more
user-friendly than filling out forms and after each submit be told it's
wrong.

Besides, ereg is slow, compared to strlen, as Kimmo already explained
how to use.

Sh.

--
Backbone Scoliosis

[millw0rm]

wow that kool!!!

thnx alot!
Kimmo Laine wrote:

<mi******@gmail.com> wrote in message
news:11**********************@j73g2000cwa.googlegr oups.com...

why i m getting error here???

Warning: ereg(): REG_BADBR
code:
if(!ereg("^(.){15,400}$",$string)) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}
Want to Achive:
$string is a textarea, i want the user to input atleast 15 characters
and shldnt exceed more then 400 characters!

Don't know, but why would you need to use a regexp for so trivial case?
Remember the KISS rule: Keep it simple, stupid.

if( ($len = strlen($string)) < 15 || $len > 400) {
$errormsg[1] = "- Must be more then 15 Characters & less then 400
Characters";
}

--
"ohjelmoija on organismi joka muuttaa kofeiinia koodiksi" -lpk
sp**@outolempi.net | Gedoon-S @ IRCnet | rot13(xv***@bhgbyrzcv.arg)

[Gordon Burditt]

>Although I am all pro-serverside coding, I'd rather implement these

simple input type checks on the client side, using Javascript.
I hope you mean you'd rather implement these checks ALSO on the client
side.
Much more
user-friendly than filling out forms and after each submit be told it's
wrong.

User-friendly should not substitute for security and data integrity.
You still need the checks on the server side. Nothing wrong with
doing it on the client also.

Gordon L. Burditt

[Schraalhans Keukenmeester]

Gordon Burditt wrote:

Although I am all pro-serverside coding, I'd rather implement these
simple input type checks on the client side, using Javascript.

I hope you mean you'd rather implement these checks ALSO on the client
side.

Much more
user-friendly than filling out forms and after each submit be told it's
wrong.

User-friendly should not substitute for security and data integrity.
You still need the checks on the server side. Nothing wrong with
doing it on the client also.

Gordon L. Burditt

Correct on both accounts. I never assume anything to be safe sent by a
client. In fact I think I can be categorized under the 'paranoid'
section wrt security issues. Professional deformity I guess...

Thx
Sh.

Sh.

--
Love is what you've been through with somebody.
-- James Thurber