So passing an array pointer is fine, but putting an array pointer inside an array isn't? One level of indirection is fine, but not two?
So passing an array pointer is fine, but putting an array pointer inside an array isn't? One level of indirection is fine, but not two?
Morning eyes. I see how what he is doing is the same.
Passing an array pointer to a function is what I assume the behavior being abused was meant to support is different from creating a spaghetti bowl of arrays of pointers to arrays being passed around for the fun of it.
At least I see why saffith did it. Tell me something. If the only option is a conversion tool or even if ZS gets updated to a language with standard types, how would you support that?
It seems to me the people against replacing ZS are the ones hacking it to do things it really wasn't meant to do, things a better scripting language could easily do.
I'm starting to come around. In the context of ZS, anyway. Seeing how ghost.zh used it has my gears turning on how this could be really useful.
Its like a guy playing guitar using only his thumbs, and I'm like, "so what. I can play that and not look like a potato!" And then he shreds that Vai piece from that corny 80s film and I'm like, maybe I should try that.... Potato up!
I'd still rather have a better scripting language.
This post contains the official Gleeok seal of approval. Look for these and other posts in an area near you.
Well, they could be 'fixed' if we truly wanted to go to the effort of adding real arrays, which AFAIK we don't. If we did, they'd just be declared with different syntax, and be true array data, but that's a lot of effort for little reward, save that strings would be real char. I wanted to do that once upon a time, but I've been convinced otherwise more recently.
It is true that if the stored pointers become invalid, the user will hit boundary walls, or other errors may occur; but that is purely user error. You can't possibly package every possible code mishap in bubble plastic to make it extra-safe from any incident.
I'll wait for a working example of your implementation before I discuss anything further on the subject, unless there are any factual, genuine concerns that now exist to discuss. I think that we covered the basics thus far, made some decisions, and have a direction. Once all of our code is in line, our ducks fall in line to be exterminated, and Venus gives Jupiter a celestial lap dance, we can have yet-another-tangent; so, a few months?
I'm frankly sick to death of this entire debate, which we could have resolved far more efficiently if everyone was on the same page from the onset. I should have been more blatant when I initially mentioned the problems that are genuine concerns. Good luck, and happy programming.
http://www.zoriarpg.com/zc/LoE_Userbar.png http://zoriarpg.com/zc/EiyuuUserbar.png
http://www.zoriarpg.com/zc/CIS_Original.pnghttp://www.zoriarpg.com/zc/CIS_II_Userbar.png
Latest ZC 2.53 (Win32) | (Technical Specification | Changelog)
Latest ZC 2.55(Win32) | 2.55 Modules | (Techical Specification | Changelog)
ZC Source Code | ZClaunch Source Code
Featured Scripts & Headers: RPG.zh ( v. a0.97.1 ) ( RPG.zh Thread ) | Zelda 3 Thief's Town Treasure Chest Minigame (ffc) | Bobomb (enemy)
ZScript & ZC-Related Pastebin | ZC Dev & Builds | ARCHIVED ZC Dev & Builds | YouTube Channel | Quests and ZScript Repository
All of the code that I create and publish here is free for use, modification and distribution under the GPL v2.0, or v3.0 where applicable.
There are currently 1 users browsing this thread. (0 members and 1 guests)