XYplorer Beta Club

obviously setkey is a SC command and has no return value.
Of course I can check with getkey to see if the value is the one desired.
but of course, this takes unreasonable time since the file needs to be accessed again.
would it not be better if setkey was a function and had a return value indicating whether it was successful or not?

I think we had this type of problem long long ago, maybe not in exact the same context.

My current idea for this would be if XY defined a variable like <rc>, containing return code information for the last executed command or function. (This way it also could be used for functions usually returning other information.)

PeterH wrote:I think we had this type of problem long long ago, maybe not in exact the same context.

My current idea for this would be if XY defined a variable like <rc>, containing return code information for the last executed command or function. (This way it also could be used for functions usually returning other information.)

Good idea, but cannot be done. It would be an incredible amount of work to implement and document it.

admin wrote:

PeterH wrote:I think we had this type of problem long long ago, maybe not in exact the same context.

My current idea for this would be if XY defined a variable like <rc>, containing return code information for the last executed command or function. (This way it also could be used for functions usually returning other information.)

Good idea, but cannot be done. It would be an incredible amount of work to implement and document it.

what about only transforming setkey into a function (instead of a command)?

A troublesome thing to do. I see no compelling reason to go that way.

ok, no big issue. was just asking.
there still is the workarund of checking with getkey.

You could check the file size, modified date etc before and after the setkey cmd.. If they differ, setkey was probably successful.

Or a hash value (what I do with my files to make sure they weren't modified)...

That's probably even slower than getkey since hash functions have to read the entire file.

Calculating a sha1 hash 100 times (in a loop) for an .ini file with two sections and 25 key-value pairs takes 47ms. Can't see an issue there.