When ScBridge is in a Delphi 7 module's USES clause, it breaks calls to the Delphi RANDOM function (which generates a real-type random number in a specified range), because that name is also used for a global TScObject variable in ScBridge.pas.
(1) Do you consider this to be a bug in SecureBridge that ought to be corrected?
(2) What's the easiest way to work around it? Is there a way to tell Delphi that I'm referring to the built-in function instead of SCBridge's object?
ScBridge romps on Random (Delphi)
Re: ScBridge romps on Random (Delphi)
The presence of the global variable Random in the ScBridge module corresponds to our architecture and is not a bug.
To call Borland's Random function, you should execute the System.Random code.
To call Borland's Random function, you should execute the System.Random code.
Re: ScBridge romps on Random (Delphi)
Of course! That's such a standard way of clarifying references in other languages that I should've just tried it. Thanks, Viktor.
Re: ScBridge romps on Random (Delphi)
Thank you for the interest in our products.
If you have any questions during using our products, please don't hesitate to contact us - and we will try to help you solve them.
If you have any questions during using our products, please don't hesitate to contact us - and we will try to help you solve them.