Hi,
PMJI, how about:
Sen>"Hello World"
All character strings should be delimited by a pair of single/double quotes.
On the other hand, %SPACE% is strenously cumbersome.
Cheers,
Armstrong Wong
Hong Kong
clipboard contents not recognised
Moderators: JRL, Dorian (MJT support)
That would cause untold nightmares with backwards compatibility.
While working on the next release we've done two things:
1. Added an option to the editor to view all hidden chars.
2. Added VAREXPLICIT option. When set to 1 variables will only be resolved if embedded by % chars. e.g.:
Let>VAREXPLICIT=1
Let>Name=Fred
Send>Name
Send>%Name%
The first Send would send the literal 'Name'. The second Send would send the value 'Fred'.
The default for VAREXPLICIT=0 which would yield current results where both Sends would send 'Fred'.
While working on the next release we've done two things:
1. Added an option to the editor to view all hidden chars.
2. Added VAREXPLICIT option. When set to 1 variables will only be resolved if embedded by % chars. e.g.:
Let>VAREXPLICIT=1
Let>Name=Fred
Send>Name
Send>%Name%
The first Send would send the literal 'Name'. The second Send would send the value 'Fred'.
The default for VAREXPLICIT=0 which would yield current results where both Sends would send 'Fred'.
MJT Net Support
[email protected]
[email protected]
[So sei es!]For the last 60 years in the software industry, the backward compatibilities is, arguably, not a big issue. In this case, the single/double quote syntax can be handily resolved:
If the first char after Let>= isn't a signle/double quote, then maintain status quo;
If the first char after Let>= is a single/double quote .and. a matching single/double quote is found on the same command line, treat all chars inside the pair of the single/double quotes as a character string; otherwise, issue a syntax error.
Though we should practice democracy in programming language design, we ought not deviate from the wisdom of the convention of the current programming languages. Especially, Macro Scheduler should be syntactically similar to VBscript and CMD batch.
Cheers,
Armstrong Wong
Hong Kong
If the first char after Let>= isn't a signle/double quote, then maintain status quo;
If the first char after Let>= is a single/double quote .and. a matching single/double quote is found on the same command line, treat all chars inside the pair of the single/double quotes as a character string; otherwise, issue a syntax error.
Though we should practice democracy in programming language design, we ought not deviate from the wisdom of the convention of the current programming languages. Especially, Macro Scheduler should be syntactically similar to VBscript and CMD batch.
Cheers,
Armstrong Wong
Hong Kong
-
FS
Well, there is the question about compatibility backwards.
In any event, it is needed that the Macro Scheduler Editor has the feature of "Remove spaces at the end of every line".
I think it is very bad to allow the spaces in variable names or label names. When you do not know this you got a lot of problems.
I think it is good to allow spaces in the middle of a string (some like:
Send>Hello, how are you?)
The problem is the space at the end of a Send.
The most important thing is the request feature of "Remove spaces at the end of every line". Other important thing it is to explain in the manual the "invisible chars".
Indeed, I will never use spaces in variable or label names. Have you ever used?
In any event, it is needed that the Macro Scheduler Editor has the feature of "Remove spaces at the end of every line".
I think it is very bad to allow the spaces in variable names or label names. When you do not know this you got a lot of problems.
I think it is good to allow spaces in the middle of a string (some like:
Send>Hello, how are you?)
The problem is the space at the end of a Send.
The most important thing is the request feature of "Remove spaces at the end of every line". Other important thing it is to explain in the manual the "invisible chars".
Indeed, I will never use spaces in variable or label names. Have you ever used?
