Calling OpCode Strings

[Aurel]

Hi Charles
I just found your topic on Jose forum about this OpCode Strings
where you say that on this way can be speed up interpreter without need for bytecode or interpreting
text.
Do you can show us something similar created in Oxygen Basic.
I am interested about this because maybe i can use this technique in my new interpreter...

[Charles Pegge]

Hi Aurel,

That is very similar to what Oxygen does now, but going directly to machine code bytes without using an assembly code layer.

You need to be familiar with how the Pentium works, and the coding patterns of turning instructions into opcodes and address operands. The Pentium is a complex beast, but you only need a small proportion of the instruction set for performing math and logical operations.

The simplest call you can perform is the ret instruction: 0xc3

string s=chr(0xc3)
sys a=strptr s
call a
print "ok"

[JRS]

That is very similar to what Oxygen does now, but going directly to machine code bytes without using an assembly code layer.

That crazy idea I had of using SB as a replacement for FB with O2 until it self compiled doesn't sound so nuts after all. 

If I remember correctly, you said that you only used FB as an easy way to manage variables (data) and any language would do. (please correct anything I said that is untrue)

[Emil_halim]

nice idea Mr Charles.

string s=chr(0xc3)
sys a=strptr s
call a
print "ok"

for the sake of simplicity you can change that to

string s=chr(0xc3)
call s
print "ok"

Oxy must be smart enough to recognize that. 
 

[Charles Pegge]

You can do it with bstrings:

bstring s=chr(0xc3)
call s
print "ok"
frees s

or with normal strings like this:

string s=chr(0xc3)
call *s
print "ok"