Hmm... You're the one who dubbed me the 'ambassador' to the ZC community. If you don't like me doing that job, shut it, and blame yourself. :D
Or perhaps both of you could knock it off.
-KA-
Printable View
I just wanted to mention that I picked up the array thing from reading through ghost.zh. So, blame Saffith. :P
Of course, seeing that ghost uses it, you'd end up breaking quite a lot of things if you don't support it.
The heart of the problem is that ZScript treats int and int[] as the same thing. You can do the same trick for the other types as well, but I don't know of anybody doing that.
If we end up compiling ZScript to AS (still not sure what the exact plan is), it shouldn't be too hard to fix. Just treat ZScript's arrays as their own "thing", separate from actual AS arrays. Just keep a table of them, and look them up anytime you do an array dereference. So, just compile them to eg. ZS_Array_Get(int id, int index) and similar instead of actual array references.
If we're having ZScript and AS side by side, it's a non-issue. If we want ZScript and AS to be able to interact with each other - well, that was gonna be a mess anyway.
Edit: relevant section of ghost.zh:
CODE: Show
Oh, yes, you do. Have you never seen me do this with ffcs or items? I also do it with itemdata now. :/
I second this suggestion. I mentioned earlier, that we should just treat all of the ZScript types as special cases to handle them and avoid all of this incompatibility nonsense.
Precisely. My second option, is parallel operation, with no direct communication. I suppose the ZScript messaging and AS messaging could be used as an interface, but if you are going to do that, you may as well implement all the types in some fashion.Quote:
If we're having ZScript and AS side by side, it's a non-issue. If we want ZScript and AS to be able to interact with each other - well, that was gonna be a mess anyway.
So, compatibility of 40% now? Huzzah, huzzah. I often hate the accuracy of my predictions. :(
@ZoriaRPG
Why don't we go for 0% compatibility and you learn to deal with it. Gleeok already pretty much decided he is not dropping support for ZScript. "since that's crazysauce"
There is therefore no reason for AS and ZScript to be compatible. Pick one or the other, or may'be both who knows.
Therefore every argument you make is invalid. Hence why I am annoyed at you.
Sorry if this makes me sound like a bitch.
@Gleeok
Any chance I can convince you to ditch the AS compiler for ZScript, i would rather we play it safe and not have zscript and as interacting with one another... Too much can go wrong.
the answer for the zscript thing is already "no, that's dumb". It will take significantly more work for significantly less gain. It seems obvious.
I was thinking we'd just expose the ZScript internals to AS as a custom data type or something. Nothing fancy, just let AS get/set any arbitrary ZS variable, no complicated timing or waitdraws or whatever.
In any case, whether it's added or not, I don't believe interaction between the two will affect the current part of the design at all. The decision can be safely put off until AS and ZS are working side by side in the first place.
I mostly do it because my waitframe functions tend to get more and more arguments as I work on a boss. Every time the number of arguments changes I have to change every instance of those functions, so it's faster to just cram most of them in an array.
So for a boss with laser attacks I might have something like this:
I see no use in doing this with global arrays so no worries there. And echoing what Grayswandir said, I learned to do this from looking at some of Saffith's scripts. I LEARNED IT FROM YOU, DAD! I LEARNED IT FROM WATCHING YOU! :PCode:int laserX[32]; //Laser X position
int laserY[32]; //Laser Y position
int laserA[32]; //Laser angle
int laserW[32]; //Laser width
int laserT[32]; //Laser timer
int vars[16] = {laserX, laserY, laserA, laserW, laserT};
void Example_Waitframe(ffc this, npc ghost, int vars){
Example_UpdateLasers(this, ghost, vars);
Ghost_Waitframe(this, ghost, true, true);
}
void Example_UpdateLasers(ffc this, npc ghost, int vars){
int laserX = vars[0];
int laserY = vars[1];
int laserA = vars[2];
int laserW = vars[3];
int laserT = vars[4];
for(int i=0; i<SizeOfArray(laserX); i++){
//pretend this is actually doing something
}
}
Here is my announcement: We are officially ditching both ZScript and AS for the only appropriate language:
Spoiler: show
End of report.
/and I used to be so damned polite./
:banghead: