egghelp.org community

[walker]

i have code like this:

[raider2k]

not sure what you are trying to do, but I put up this one and also returns $data

[walker]

thanks bro raider2k, i must explain what i want to do.

[raider2k]

so you want to show everything between <a href="b.php"> and </b>, but not show the rest of it?

please show me example content of your var $data and what it is meant to look like, Ill try to build something for you.

[walker]

[arfer]

The most likely issue here is that substitution of the variable named arg_date by its value using $arg_date will not occur because the braces that are surrounding the regsub pattern prevent normal variable, command and backslash substitution.
_________________
I must have had nothing to do

[walker]

[arfer]

It can be done by various means. Generally I choose the following method of including a variable within a regexp/regsub pattern

[walker]

[raider2k]

not sure if the following is what you are looking for, heres a try:

[speechles]

[arfer]

Your solution will probably not work for two reasons :-

The \s will be substituted in setting the variable and come out as simply s, thus negating its real meaning in the regsub pattern (space character).

The text portion $arg_date(.+) may be interpreted as an array. Since arg_date is not an array, an error will occur.

Thats my reading of it anyway.

I don't think the command subst is foolish in the right circumstances, but like I said, each to his own. The main thing is choosing an option that works.
_________________
I must have had nothing to do

[Sir_Fz]

The \s issue can be avoided by adding an extra \ (i.e. \\s) and to avoid the array conflict use ${arg_date} instead.
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts

[arfer]

Yes, Sir_Fz, I agree. In fact I pretty much said as much in one of my earlier posts under this thread. Patterns need to be modified to account for them being defined outside braces. Possibly the quotes would need to be double backslashed too, though without testing I'm not certain of that. Even the < and > from html tags look a mite dubious, since these characters have meaning in tcl.

This is exactly why I long ago chose to use the command subst where suitable. I simply made too many silly mistakes in switching between patterns inside braces and patterns outside braces. This is rather more likely to make me look foolish than using an extra command. I can't see an extra few milliseconds execution time as generally being an issue.
_________________
I must have had nothing to do

[Sir_Fz]

The objective here is to have a valid regexp pattern, even though < and > have a special meaning in Tcl they won't be interpreted as such since they're in a string (and not in an expression), a single escape for a quotation is sufficient to return and match it. Basically, there's no need to complicate things, perhaps by trial and error you'll finally reach the desired result (if things get difficult).
_________________
Follow me on GitHub

- Opposing

Public Tcl scripts