DIFFER questions....

[vefatica]

Vince - how about trying to find a simple collisions for sha512 ?

As noted previously, that would take a very long time.

 

[AnrDaemon]

So back to using @CRC32 ?

Why?

 

[AnrDaemon]

@FULL doesn't care about paths.

https://www.jpsoft.com/forums/threads/realpath-variable-function.8660/

 

[rps]

This thread is getting a little to long and covers more than a few questions and answers.

https://www.jpsoft.com/forums/threads/realpath-variable-function.8660/

I think much of what the referenced suggestion for a @REALPATH[] function can be accomplished by:

echo "%@rtrim[\,%@path[%@search[tcmd.exe]]]"
"D:\tcmd v22"

This should yield a path to an existing file, in the path, without the trailing back slash.
If this isn't what was being described then hopefully Rex will have a better understanding.

 

[AnrDaemon]

I already explained that in the thread. @PATH is useless for intended purpose of the suggested function.

 

[Charles Dye]

I don't understand what "the intended purpose of the suggested function" is; another implementation of @TRUENAME? But the help text seems to imply that @PATH has something to do with the filesystem. I'm pretty sure that it doesn't. @PATH is just a string-parsing function: strip out any quotes, then delete anything after the last (back)slash. You could use it e.g. to pull a key name out of a fully-qualified registry value name.

 

[AnrDaemon]

Note: The @TRUENAME function makes no assumption about the existence of a file or directory.