SC <date> and milliseconds?

[Filehero]

... but I have to admit I got used it myself and was surprised that ...

For me it was the other way round. I was quoting them all the time. But as I've read repeatedly it's not required for XY native vars I finally started to get used to. I even have adopted my syntax highlighting rules accordingly.

After releasing 18.60.0100 I will try to improve the situation...

Thanks.

[PeterH]

In general it's correct: exceptions often are not good.

But, hoping that I am right:
- inside <...> no variables seem to be allowed
- without a variable any concatenation doesn't make sense (what would you concatenate?)
- so after all: everything inside <...> could be interpreted just literally

This would mean: Syntax definition can be changed so that everything between <...> is treated just as a string, like between '...'.
No: that's no exception - it's a syntax rule saying "between <...> there are strings", like between '...'.
(I compare to single quotes at will - as they don't allow variable substitution, unlike double quotes.)
(While unquoted $a = text; or many function operands are exceptions. )

If I missed some "exception": please tell

[Filehero]

Thanks for removing the quote-constraint, Don.

[admin]

Well, just saw it's not perfect. This does not work:

Code: Select all

echo <date hh:nn:ss.fff>.<date hh:nn:ss.fff>;

Not sure if I can fix that...

[admin]

Well, I think I could fix it.

[highend]

Thanks, good job!