Adding spaces to a string

dparsons · March 23rd, 2009, 12:25 PM

You could do something like this:

joesref = reIn.Replace(joesref, "$1 " )

It would really help if you could tell us WHAT code is failing. Did you create the function that Old Pendant provided or are you using the inline style?

Which line of the code that he provided is failing?

-doug

jroxit · March 23rd, 2009, 12:37 PM

I'm using it inline, not as a function because I have to set the variable after I received a response from another webserver. The line of Old's code that's failing is:

Response.Write reIn.Replace( input, "$1 " )

Thanks.

dparsons · March 23rd, 2009, 12:45 PM

Hmm. I am out of ideas. This code, as written (testd on IIS 6 and 7), outputs: A B C D E F G

vb Code:

<%
Dim input
Dim reIn
input = "ABCDEFG"
Set reIn = New RegExp
reIn.Pattern = "(.)"
reIn.Global = True
Response.Write reIn.Replace( input, "$1 " )
%>

Troubleshooting code that I can't see is a painstaking endevour. ;]

-Doug

Old Pedant · March 23rd, 2009, 03:46 PM

SO work around company policy.

PARAPHRASE your actual code by creating something that exhibits the same problem but doesn't give away any of how you are actually using this.

In my code, there's no SUB involved. BUT... But if you USED the code wrong, there could be an IMPLIED SUB.

As Doug showed you, in VBScript whenever you use a subroutine--NO MATTER IF IT IS CALLED SUB or FUNCTION, you can *NOT* use parens when you have two arguments unless you *USE* the subroutine *AS* a function.

SO you could have

Code:

Function Foo(a,b)
     ...
End Function

Foo(1,3) ' -- ERROR:  "Can't use parens when calling a sub"
dummyVariable = Foo(1,3) ' would work
CALL Foo(1,3) ' would work
Foo 1, 3 ' would work

So the solution *MIGHT* be as simple as either getting rid of your extra parens *OR* putting the keyword CALL in front.

But get around the company rules by posting some "parallel" code.

After all, that's what you did in your FIRST post in this thread, isn't it? Why can't you do that again?

Old Pedant · March 23rd, 2009, 03:51 PM

If you changed my code from

Code:

Response.Write reIn.Replace( input, "$1 " )

to just

Code:

reIn.Replace( input, "$1 " )

then you have done exactly as both Doug and I suspected.

And you could get rid of the error by coding ANY of my suggested fixes:

Code:

reIn.Replace input, "$1"
Call reIn.Replace( input, "$1")
dummy = reIn.Replace( input, "$1")

BUT NONE OF THOSE WILL HELP YOU!

I think you are under the impression that the code reIn.Replace is going to *CHANGE* the contents of the input variable. NO NO NO! NOT AT ALL!

If you WANTED that variable to be changed, you would need to code

Code:

input = reIn.Replace( input, "$1 " )

And now you *ARE* using the function *AS* a function, so no more complaints about the parentheses usage.

But next time, don't spend so much time spinning your wheels. If you can post a problem and show code, surely you can post an attempt at fixing the problem that includes code. Just make sure the code doesn't give away company secrets. (That probably aren't all that secret, anyway.)