Post
by armsys » Thu Dec 19, 2002 11:30 am
Hi Ernest,
Thanks for sharing your view.
With due respect, on the other hand, in light of routine virus attacks, would you concur it might be too risky to allow anyone without any programming knowledge to write a Macro Scheduler script no matter how benign it may seem? It should be done so under supervision. That's exactly where a competent distributor or reseller ('provider") play a vital role. To be more explicit, the provider should be under obligation to walk the customer through the initial script coding.
Let's return back to our philosophical language design issue. Functions can always be extended via VBScript or calls to external .EXE, .COM, or .BAT,...etc., but not language construct. Code reability and maintenability can be enhanced or hindered by the language structure in one or another Conversely, the values of functions written in Clipper, Delphi, C#, VB, VBA,... can alway be returned to Macro Scheduler script. The language constructs in PL/1, Clipper, Delphi, C#, VB, VBA, VBScript,...etc. can't be transferred back to Macor Scheduler.
Even for the logical comparisons, Macro Scheduler only allows =, . It would be nice if Macro Scheduler could support >= and <=.
Look forward to hearing your insightful view. Thanks.
Cheers,
Armstrong Wong
Hong Kong