[2.xx] Custom Global Pointers (The Easy Way)

If you add the ability to declare other data types (lweapon, ffc) at a global level, we could build our own quasi-objects, as custom pointers.

As an example, I was trying to declare lweapon Player at a global level, so that I could make a custom player object with a pointer that I could call from anywhere.

Is it possible to reference a pointer inside a script, from a global function in the same way that a script at local scope can call a function from elsewhere with :

Code:

---

scriptname:function()

---

?

Code:

---

scriptname:Pointer

---

I suppose not, because the pointer isn't valid until it's executed...so, right, a decent amount of global pointers would be very helpful.

Your forgetting one key component here. Everything is compiled into ZASM. So custom objects aren't happening till the total 3.0 rewrite.

Quote:

---

Originally Posted by Tamamo

Your forgetting one key component here. Everything is compiled into ZASM. So custom objects aren't happening till the total 3.0 rewrite.

---

I'm also remembering that 2.60, is at least a partial engine re-write. I don;t know how much of ZASM Saffith plans to tough in 2.60, but it would be a good time to add things of this nature, that don't require full engine replacements. It would require expanding the assembly language to permit it, but it [the datatype and structure] would otherwise function in the same manner, as it does at present.

That applies to the existing datatypes, of course. You couldn't expand them, or modify their structure, but you may be able to use them to define object-like behaviour. That's why I was specific, to the existing datatypes, and didn't request full-blown custom object definition.

Falls under custom scripted types, really, ..and I agree that it would be nice.

A while back I wanted to add a new scripting language to ZC, angelscript, along with a full-blown c/c++ preprocessor, but nobody really seemed interested. :(
It would have supported everything, basically, from user defined types to inheritance, inferfaces, mixins, function pointers, and on...

There was that whole 'OMG no more new stuff, we want 2.5 released and bugfree now." ...and this reply is going nowhere, so....

Quote:

---

Originally Posted by Tamamo

Your forgetting one key component here. Everything is compiled into ZASM. So custom objects aren't happening till the total 3.0 rewrite.

---

How would running ZASM affect using objects?

Quote:

---

Originally Posted by Gleeok

Falls under custom scripted types, really, ..and I agree that it would be nice.

A while back I wanted to add a new scripting language to ZC, angelscript, along with a full-blown c/c++ preprocessor, but nobody really seemed interested. :(

---

:O

That's because people are stupid.It's never too late, you know!

@Gleeok

If you say it's possible and we can go about implementing user defined pointers and pointer functions. Then I'm all for it. Let's do this shit, but we're still waiting for opensource. :p

I'm tired of waiting for open source too. TBH I don't see myself fixing the ZC qsu problem so I might as well put up ZQ. :shrug:


It would be an interesting experiment though!! -Put in another script language and let the two duke it out and see which one people start using more. XD :P

I still gotta fix wizzrobes though @Gleeok .

Quote:

---

Originally Posted by Gleeok

I'm tired of waiting for open source too. TBH I don't see myself fixing the ZC qsu problem so I might as well put up ZQ. :shrug:

---

What is the qsu problem? I don't see a point in waiting for it to be perfect. It's not like it can't be fixed later.

I am actually leaning toward Angelscript, but I haven't tried doing much with it yet. Just seems a bit premature, y'know? I've got some ideas, but I don't know to what degree it will work the way I want it to.