Calling opcode string discussion

[Anne Wilson]

To be compliant with this policy, OxygenBasic executes its JIT binaries in system allocated memory, not in data memory, or on the stack. It can't be peeked at run-time.

 I haven't use OxygenBasic yet,  what is this JIT binaries ?     Does JIT means Just in Time ?
 does it means a kind of runtime module where the OxygenBasic interprets the codes ?

It would be great to run some modules in the system memory which hackers cannot peek.

Only problem is to convert the PowerBasic codes to OxygenBasic.  
A lot of our codes are in DDT  ,  can OxygenBasic handle DDT ?

for example in PowerBasic DDT code is 

Code:

  %Widlg = 200
  %Htdlg = 140
' Create the dialog
DIALOG NEW 0, "Color Dlg in Win10",,, %Widlg, %Htdlg, %WS_CAPTION OR %WS_SYSMENU OR _
         %WS_THICKFRAME OR  %WS_MINIMIZEBOX OR %WS_MAXIMIZEBOX, 0 TO hDlg
                            

in OxygenBasic it could be some thing like ?  I'm not sure 

Code:

%Widlg = 200
%Htdlg = 140
' Create the dialog
  hDlg = DIALOG(0, "Color Dlg in Win10", 0, 0, %Widlg, %Htdlg, _
                %WS_CAPTION OR %WS_SYSMENU OR %WS_THICKFRAME OR %WS_MINIMIZEBOX OR %WS_MAXIMIZEBOX)