0 Members and 1 Guest are viewing this topic.
As far as I know, if you use a custom named variable, it is impossible to modify the location it points to, as it is treated as a constant pointer. It is also impossible to have only a single byte custom variable as far as I know.
Lbl Black0->r3Repeat pxl-test(r1+r3++,r2+r3) or pxl-test(r1-r3,r2+r3) or pxl-test(r1+r3,r2-r3) or pxl-test(r1-r3,r2-r3)EndReturn
So, files (Y1 etc) work in Copy() right?Also say I getCalc(...)→{L1+8}r. In a Copy statement, do I tell it L1+8 or do I somehow specify that it's two bytes? Or does it default to two-byte values?
Quote from: Darl181 on March 20, 2012, 02:34:06 pmSo, files (Y1 etc) work in Copy() right?Also say I getCalc(...)→{L1+8}r. In a Copy statement, do I tell it L1+8 or do I somehow specify that it's two bytes? Or does it default to two-byte values?Yes Files work in a copy statement, but what do you mean by your second question? The copy statement copies a certain number of bytes from one location to another
Another, unrelated...How far does the VAR++ / VAR-- syntax stretch?I tried to optimize{L2+10}++If {L2+10}=8to!If {L2+10}++-8And it didn't return true when it should in the context I'm using it though it did compile without error.Putting parenthesis around {L2+10}++ didn't have the statement working either. Also tried !If {L2+10}---255 (it's one byte) but it didn't do much.I'm guessing it's peepholed anyways, but it makes for smaller source and faster typing.The syntax appears kind of weird, but should this work?