Named array element (Bug or Feature)?

[j_dodek]

Hi

I have a named array of containers. I like to increase the arry if the name is not present in the

array. For doing this i am using the PropertyObject members.

This is working well if you are using strings without 2 or more "\" (Backslash).

So whats the reason. 

I have used. T4.5 and 4.2 

Regards

Juergen

[RayFarmer]

can you post a 4.2 example?

[j_dodek]

Hi Ray,

Demo as 4.2

Regards

Juergen

[RayFarmer]

Its probably because \T puts a tab in your string whereas \M does nothing.

If you do \\T then the Exists() is True and it doesn't add it again.

[j_dodek]

HI Ray,

Thanks for testesting "\\T". Have also tought about this.But not tested, because i am getting string from TS itself.

It is the path from DLL CodeModule apater. So my opinion is that TestStand should handle the "\" stuff internally.

My workaround was just replacing the "\" with a "/".

Regards

Juergen

[dug9000 · Accepted solution]

The backslashes for escaping only apply to string literals in expressions. In all other cases they do not apply. If you take a string from somewhere else and try to convert it into a string literal for an expression you need to escape it (i.e. all backslashes should be escaped with another backslash and all quotes should be escaped with a backslashes, and potentially carriage returns and linefeeds and tabs should also be escaped). Also, there is a function in the engine that will do this for you, Engine.Utility.Escape().

Hope this helps clarify things,

-Doug

[j_dodek]

Hi Doug,

Thanks for pointing out.

Engine.Utility.Escape() is exactly what i need.

Just a note. I was getting the string from Engine.FindFile()

It would be nice to add a remark to function's help in future relase that founded string should be escaped.

Regards

Juergen

[dug9000]

The issue is, the string returned by FindFile doesn't necessarily need to be escaped. The escaping is only necessary when you are creating a string literal in an expression. It really doesn't have anything to do with FindFile because in all other cases there is no escaping so FindFile returning an unescaped string is no different than anything else returning a string. How exactly are you using the string? Maybe what should be documented or looked into is that the way in which you are using it requires escaping.

-Doug

[j_dodek]

Hi Doug,

Upps, I told you something wrong!!!  Engine.Find() File is NOT the problem here.

Excuse me.

The problem is as mentioned in topic on named arrays:

Here is the way iam getting the string.

1. Statement

// Modul Name

Locals.strFileName = Locals.hModule.AsCommonCModule.ModulePath,

// Lookup String

Locals.strArrayName = Locals.strFileName,

// Workaround

SearchAndReplace(Locals.strArrayName ,"\\","/"),

Locals.strLookup ="[\""+Locals.strArrayName+"\"]"

If Expression:

!Locals.objModules.AsPropertyObject.Exists(Locals.strLookup ,0)

     2. Statement

     // Set Array Elements name

     Locals.pObj.AsPropertyObject.Name = Locals.strArrayName,

Regards

Juergen

[dug9000]

I see that it's lookup strings of the format:

MyarrayVar["elementName"]

where the escaped string is also expected. This is similar to the string literal in expressions case. Generally, if you are adding the quotes for a string, then the contents between the quotes likely needs escaping. I've logged a request to update the documentation for lookupstrings to mention this issue and explain about escaping strings.

-Doug