Get Dual Pane mode?

[admin]

If only we had a not-operator then you could make it:

Code: Select all

if (! get('#800')) {
  #800;
}

If only...

Try next version. (No time to document it...)

PS: All this should work in 9.70.0005... looks like I got it.

I had expected that this would also work:

Code: Select all

$a = 'a';
  if (! "$a" Like "") {
    echo 'hi';
  }

Not a deal breaker since it seems to work with parens:

Code: Select all

$a = 'a';
  if (! ("$a" Like "")) {
    echo 'hi';
  }

Yes, parens are necessary since the NOT operator is pretty much at the end of the precedence chain.

[TheQwerty]

Yes, parens are necessary since the NOT operator is pretty much at the end of the precedence chain.

Erm, I don't like that parens are required here but I'll get over it.

However, I think you must add a section to the Scripting help documenting the full precedence of Math, Comparison, and Boolean operators to make this clear.

And I'd try to format it better than this extremely confusing way which requires a couple of reads:

The operator precedence is (*,/) > (+,-) meaning that * and / are of equal weight, and + and - are of equal weight.

Take a look at the nice tables other languages have: Python, C#, Java, C++, PHP

Maybe even note where not appears in their orders.

[admin]

Yes, parens are necessary since the NOT operator is pretty much at the end of the precedence chain.

Erm, I don't like that parens are required here but I'll get over it.

Looks totally normal to me. I'm not aware of a language where this would be different.

[TheQwerty]

Looks totally normal to me. I'm not aware of a language where this would be different.

I feel the required parens are just wasteful and make the code more difficult to read.. it's more likely that when someone uses:

Code: Select all

if (not "$a" Like '') {...}

that they want "if $a is not empty", rather than "if $a-not'd is empty".

The only reason I've ever wanted a not operator is for avoiding having to switch between:

Code: Select all

if ("$a" Like '') {} else { ... }

and

Code: Select all

if (Compare("$a", '')) { ... }

I have never ever wanted to test $a-not'd against anything.


In the very least could you at least add something like

Code: Select all

if ("$a" not Like '') { ... }

or

Code: Select all

if ("$a" Unlike '') { ... }

[PeterH]

I'm not sure TheQwerty's reasons (like "I prefer ...") are very good -
but thinking about that I looked for operator precedence in XY - and found nothing.
(PS later found it: see below!)
Then I tried to look into the examples referenced by TheQwerty. Only half a success - they don't know a "like".
My solution: "like" does a kind of compare - it could by like < or ==. In this case ! ("not") seems to be *higher* in precedence? That is
! a == b would mean (! a) == b
Or do I read it wrong?
OK - you (Don) *could* *define* "like" much higher in precedence...

By the way: I had several problems in XY-documentation!
- I tried to find "like" via index and via find - no chance.
- Same for "if".
Hey - now I found "precedence"! (This *can* be searched ) But it only defines *, /, + and -, relating only to math?
*Wrong* there is also another chapter with precedence for Boolean Operators!?

OK - what *should* be? Precedences are *all* related - it must be defined what's the meaning of
if ($a > $b + $c / 3 or ! $d like $e)

So I'm afraid there must be one single chapter like "Precedence of operators" for *all* operators - and the chapters for math and boolean should refer to this central point.

And as the very last thing to say: I myself always mix up precedences, and so I prefer excessive use of parentheses.

[admin]

Tip: All Scripting related stuff in the Help is under "Scripting" in the Index.

Yes, I will add something on precedence to the Help.

[PeterH]

Tip: All Scripting related stuff in the Help is under "Scripting" in the Index.

Hey - thanks for the tip! I never noticed the grouping of search-words below Scripting in the index. This at least helps a bit...

But I think the scripting-topic is so long, in between the time, that it also should be divided into (sub-)topics in the Contents (German: "Inhalt"). I don't think it's sufficient just to have this very big Scripting-chapter in Advanced Topics. You have to scroll through all that chapter (about 20 pages), just to find a heading like "General Command Syntax", "Step Mode: ...", "Comments", "If/ElseIf/Else Blocks" or whatever.