Adds TransferSharesToManyV1 to QUTIL

[double-k-3033]

No description provided.

[philippwerner]

Thanks for the contribution. Overall, it looks good to me. Just the following comments:

Why did you change the DebugInformationFormat in the platform libraries? Is there any problem with the "ProgramDatabase" setting that is fixed by changing the value to "OldStyle"? If there isn't a good reason, please undo the changes in the *.vcxproj files.

If management rights are transferred to QUTIL, it also must offer a way to transfer the rights back to other contracts. So please add a procedure TransferShareManagementRights for that purpose to QUTIL.

[double-k-3033]

I'm sorry. An error occurred during the build process, so I had no choice but to change it that way. I forgot that I shouldn't push the related files when I push.

[philippwerner]

Thanks for your contribution. Please address the following comments.

[philippwerner]

Thanks for addressing all the comments. All is looking good now, except for one remaining issue.

[double-k-3033]

@philippwerner
plz give me the feedback to solve this : #823 (comment)

[Franziska-Mueller]

@double-k-3033 please merge the newest version of the develop branch into your branch. we have reenabled the automatic contract verification for the QUtil file.

[double-k-3033]

@double-k-3033 please merge the newest version of the develop branch into your branch. we have reenabled the automatic contract verification for the QUtil file.

what is it for?

[Franziska-Mueller]

@double-k-3033 please merge the newest version of the develop branch into your branch. we have reenabled the automatic contract verification for the QUtil file.

what is it for?

We have an automatic verification tool that checks changes in SC files for forbidden C++ language features (you can see it running as ContractVerify workflow). We had to disable this automatic check for the QUtil file a few weeks ago because the verification tool couldn't handle the oracle-related code in QUtil.
I patched the tool today. I wanted you to merge s.t. the verification tool with the newest version runs on your QUtil file. For example the forbidden use of a local variable that Phil flagged before would usually have been caught by the workflow already. I asked you to do this to make sure that there are no other forbidden language features that were overlooked in the manual review.

[double-k-3033]

@double-k-3033 please merge the newest version of the develop branch into your branch. we have reenabled the automatic contract verification for the QUtil file.

what is it for?

We have an automatic verification tool that checks changes in SC files for forbidden C++ language features (you can see it running as ContractVerify workflow). We had to disable this automatic check for the QUtil file a few weeks ago because the verification tool couldn't handle the oracle-related code in QUtil. I patched the tool today. I wanted you to merge s.t. the verification tool with the newest version runs on your QUtil file. For example the forbidden use of a local variable that Phil flagged before would usually have been caught by the workflow already. I asked you to do this to make sure that there are no other forbidden language features that were overlooked in the manual review.

Thx for your support. As you can see, All checks have passed.
And then plz support me for #823 PR 🙏🏻
I really need your help.
Thx in advance. ✨