Mostly:
– incorrectly identified uninitialized variables
– explicit static global variables
– const, sign and down casts and safety
– typename use
– semicolon after function implementation
– unused variables, fields, arguments and macros
– field initialization order
– exact include filename case
– redundant in code macros already defined at project level
(cherry picked from commit f7f00c631e)
Source commit: 90ad9390853aba308abe73cf02e0281238c53c87
The discrepancy was introduced by Bug 2120 cb021fe3.
This restores the mv/MoveFile behavior to fail, if the target file exists with WebDAV protocol (but still allows overwrite in the GUI).
The cp/DuplicateFile behavior is unchanged, but the internal API was modified to match that of mv/MoveFile, in anticipation of aligning move/duplicate command behavior in GUI and need to keep current scripting/.NET behavior.
Source commit: 4661a3ea7ec8123231e376aae9913ce8457750dd
There's a small side-effect: The scripting "checksum" command now prints file name only while before it printed the path as it was original specified in the command.
Source commit: 7594ed8befc67e4da3153cc8b1b711ab104db867
https://winscp.net/tracker/572
- Change: Scripting command "mv" now checks for source file existence (to determine if it is a folder or file), so error message changes
Source commit: 747e51794ef409f3878a890c8a3729ba6d97cdff
https://winscp.net/tracker/572
- cp script command now queries the server for source file/dir, as we need the information for S3_deinitialize
- DUPLICATE_FOLDER_NOT_SUPPORTED was by mistake already committed in 32d26ba76e (Remote file duplication in scripting, .NET assembly and XML log)
Source commit: b0e54d4ef136c6d798ef8010648ba759d02229e4
