[SOLVED] Replacing/Ignoring bad characters in code

[vigilant]

How can I accomplish this?
Lets say the nickname has a character such as \
how can I get rid of it or ignore it?

please suggest

[user]

What "bad" characters? Are you sure you want to ignore them? Here's a line that will get rid of alot of characters:

Code: Select all

regsub -all \\W+ $string "" string

...but I'm not sure this is what you really need (your wording makes me think you might be having problems related to treating strings as lists)

[vigilant]

What "bad" characters? Are you sure you want to ignore them? Here's a line that will get rid of alot of characters:

Code: Select all

regsub -all \\W+ $string "" string

...but I'm not sure this is what you really need (your wording makes me think you might be having problems related to treating strings as lists)

Yes , hello for your prompt reply. I guess so, like first when you receive the nickname argument using a normal bind... and it has characters like, \ / [] and so on. What's the easiest way to capture the nickname including the [ ] , because it's not when it has \ / characters...

[nml375]

It sounds to me like you are looking for ways to avoid being exploited by nicknames such as [die].

The proper way of avoiding this is not to do massive regexp's, and other mangling, but rather use proper tcl-scripting, being aware of the command and variable substitutions done by the tcl engine, and when it does this.
This, of course, isn't something can can expect from a fresh tcl-coder, but comes from experience. If you post examples of where you are having problems, we could better point you in the right way in those specific issues.

One "rule of thumb" however, if you need to build a command line to be passed to the tcl interpreter (such as when you use timer/utimer), make it a list, as this will protect the individual items from substitutions during the next parsing.

[vigilant]

It sounds to me like you are looking for ways to avoid being exploited by nicknames such as [die].

The proper way of avoiding this is not to do massive regexp's, and other mangling, but rather use proper tcl-scripting, being aware of the command and variable substitutions done by the tcl engine, and when it does this.
This, of course, isn't something can can expect from a fresh tcl-coder, but comes from experience. If you post examples of where you are having problems, we could better point you in the right way in those specific issues.

One "rule of thumb" however, if you need to build a command line to be passed to the tcl interpreter (such as when you use timer/utimer), make it a list, as this will protect the individual items from substitutions during the next parsing.

Okay.. thanks. I was thinking of list Thanks for clarifying.

[Sir_Fz]

Script Security

[vigilant]

Script Security

I think better than that is, http://www.peterre.info/characters.html

[Sir_Fz]

That is mentioned in the "Script Security" thread vigilant

[vigilant]

That is mentioned in the "Script Security" thread vigilant

lolllllllll Well great then :O