Path with slash

[MyEarth 9]

When a user put a path with FileSelectFolder, i see some coder adding a slash at the end of the path like:

C:My FolderImages

Instead of

C:My FolderImages

It's better to add this slash ( for proper use of path, with _FileListToArray or function like that ) or it's a misuse?

Have a nice day

Edited April 23, 2013 by MyEarth

[guinness 1,434]

I would get into the habit of not adding a backslash, because it will save you a lot of work when it comes to debugging. You may have noticed AutoIt & Windows don't append a backslash. For example if you know that folder paths don't have a backslash, then the following would be easy to debug. But if you mix and match, then you would have to find $sFolderPath and work out did a backslash get appended. Any questions please ask.

$sFolderPath & "Example"

Edited April 23, 2013 by guinness

[MyEarth 9]

If it's better and best method to not adding a backslash i will not add it

[guinness 1,434]

It's not a written rule and you're entitled to do what you want with your code. I'm just providing an example of how it can save you that second or two of checking for something that can be eradicated by having a process. Others might say always append. But then why doesn't @ScriptDir have a backslash appended?

Edited April 23, 2013 by guinness

[MyEarth 9]

I know it's not a written rule and everyone with their script do whatever they want, but if i want to make a """"good"""" code i need to know what is the best approach with it, in this case is the path and the backslash

[guinness 1,434]

So what are you going with?

[Decipher 26]

MyEarth,

I second guinness's opinion.

My style:

$sPath = $sDirectory & "\" & $sFileName

Ensuring that the file paths don't have a solidus suffix allows for better readabillity when concatenating string variables.

Anonymous

Edited April 23, 2013 by Decipher