01.07.2011, 03:06
(
Последний раз редактировалось RSX; 01.07.2011 в 08:27.
)
I'm back, give or take, anyway, in these days I've made huge progress in mine Object Extension (OO simulation) and now I can continue reviewing other work. Pretty much so far I've figured out a stable version of something like C++ style, and when I'll put it together (It will need additional generator of defines/enum). Just so far I can say it uses this style :
Making an object :
Class Object;
Accessing a variable :
Object.variable; or Object.sub_object.variable; (Basically it should support chain)
Using method:
Object.method(parameters); or Object.method1().method2().method3();
Declaring method :
Class::Method(params) - Doesn't have to use unique name!
Declaring variable :
<Currently shapeless, but will be made as easy as possible, because it'll be used by generator> - Don't have to use unique name! (For example : Class1 and Class2 can both have id variables, and they won't clash in any way - usage of tagof() here)
Accessing local vars :
this.variable;
Ok now I'll get back to putting it together. And the main idea of putting this together is evolving some certain applications (or choosing best way of doing them) and specifying them. For the huge section of OO - I think it should combine into main OO syntax, and also have the main directions of OO - C++ way, Java way, and others.
Edit : Ok here's topic for OO currently : http://forum.sa-mp.com/showthread.ph...32#post1270132
Moving back to creating specifications on sa-mp coding - I think we should provide a solid example of very common place which partially "uses" standards thus forcing further extension of it.
Making an object :
Class Object;
Accessing a variable :
Object.variable; or Object.sub_object.variable; (Basically it should support chain)
Using method:
Object.method(parameters); or Object.method1().method2().method3();
Declaring method :
Class::Method(params) - Doesn't have to use unique name!
Declaring variable :
<Currently shapeless, but will be made as easy as possible, because it'll be used by generator> - Don't have to use unique name! (For example : Class1 and Class2 can both have id variables, and they won't clash in any way - usage of tagof() here)
Accessing local vars :
this.variable;
Ok now I'll get back to putting it together. And the main idea of putting this together is evolving some certain applications (or choosing best way of doing them) and specifying them. For the huge section of OO - I think it should combine into main OO syntax, and also have the main directions of OO - C++ way, Java way, and others.
Edit : Ok here's topic for OO currently : http://forum.sa-mp.com/showthread.ph...32#post1270132
Moving back to creating specifications on sa-mp coding - I think we should provide a solid example of very common place which partially "uses" standards thus forcing further extension of it.

