[deadlykitten]

hello, please, can i verify something like this :

1) 2 boolean expressions

v1=11
v2=22

IF [ [ v1 EQ 11 ] EQ 1 ] AND [ [ v2 EQ 22 ] EQ 1 ] ...

2) text

VUACM[1]='some_text'

IF [ VUACM EQ 'some_text' ]

kindly !

[deadlykitten]

hello guys & girls i am updating an old code, and i wish to share this :

   IF [ condition ] N1                     ( old stuff )
               GOTO N2
        N1 // true  branch
        GOTO N3
        N2 // false branch
      ( GOTO N3 )
        N3


 ( . . . . . . . . . . . . . . . . . . . . . . . . . . )


    IF [ condition ]   NTRUE               ( new stuff )
       ( NFALSE ) // false branch
                  GOTO NDONE
         NTRUE    // true  branch
         NDONE    NOEX

code is shorter & executes faster kindly !

hello, please, can i verify something like this :
1) 2 boolean expressions
v1=11
v2=22
IF [ [ v1 EQ 11 ] EQ 1 ] AND [ [ v2 EQ 22 ] EQ 1 ] ...

hy past self of me

 do this :
    IF [ [ [ V1 EQ 11 ] AND [ V2 EQ 22 ] ] EQ 1 ] NTRUE
* you forgot to use common factor : " EQ 1 "


checking multiple conditions is also possible :
    IF [ [ [ condition_1 ] AND [ condition_2 ] AND [ condition_3 ] ... AND [ condition_n ] ] EQ 1 ] NTRUE
* the only restriction, is that the entire text must be contained within 1 line of code

2) text
VUACM[1]='some_text'
IF [ VUACM EQ 'some_text' ]

still have no clue / it may not be possible, but is not a must

[deadlykitten]

    IF [ condition ]   NTRUE               ( new stuff )
       ( NFALSE ) // false branch
                  GOTO NDONE
         NTRUE    // true  branch
         NDONE    NOEX

code is shorter & executes faster

hello bellow are even faster execution codes, and there is room for more; the gain in speed between variants of previous post from 2018, and the one from today, is much more smaller, much more subtle, thus this post should have no relevancy for average codes, but only for situations where computation times really matters, like heavy loaded math driven codes, that affect execution time

if you feel like you need speed, then, to boost up code, get rid of comments, spaces, shorten the N*** sequence names, join blocks&codes, and in the end, nothing beats linear simple code ... unless, there is situation where linear code will not perform better than a macro, and this is a class of specific cutting operations

in short, to get speed, is needed to reduce the space that the code requires, making it much more dense, and writing it in a way that scenarios that usually execute will not pass through condition of those cases that execute with less frequency; as more and more conditions are used, the code becomes harder to follow, and for such situations i use a simple to read code, on which i apply formatting functions to make it denser, thus all debuging does not occur on the code in it's final shape / kindly

    IF [ condition ] NT
       ( false     ) // false branch
                   GOTO ND
         NT        // true  branch
         ND        NOEX


 ( . . . . . . . . . . . . . . . . . . )


 IF[condition]NT
      // false branch
      GOTO ND
 NT   // true  branch
 ND // replace NOEX with next block