Layering

[Skyler]

It's great for dissection by noobs though :wink: .

Noob said:

MOV ax, bx????? What the !@#$ is that supposed to mean??

[Dr_Davenstein]

It's great for dissection by noobs though :wink: .

Noob said:

MOV ax, bx????? What the !@#$ is that supposed to mean??

Dr_D = n00b!!!111 :???:

Unless, that copies the data stored at the address ax, to the address bx? That's what the OpenGL shader version of that keyword does anyway. Does that actually zero out ax though?

[Zap]

Unless, that copies the data stored at the address ax, to the address bx? That's what the OpenGL shader version of that keyword does anyway. Does that actually zero out ax though?

It's the other way around iirc. "Move to ax the content of bx".

[DrV]

It doesn't have anything to do with addresses either.

[Dr_Davenstein]

I'm interested in this for optimizing my programs, but unlike FB coding, this doesn't look like very much fun at all. :lol:

[Skyler]

Yeah... that's what I thought...
MOV ax, bx copies the value of bx and inserts it into ax.

[Anonymous]

it is a good general rule to look at the left hand side as "recieving" the result of an equation.

Code:

a = b

Code:

mov a, b

see, the same =)

also if i have a function which does an assignment, but i still want to be able to return a fail state, i'll do:

Code:

function assign( dest as integer, src as integer ) as integer

  if src < 9829323  then
    dest = src
    return TRUE

  end if

end function

just a silly example. but it seems to be the convention that is most widely accepted, and you have to admit, it makes sense.