[vJASS] Your often use API...

[mckill2009]

Ok guys, what's your choice of API when making a system:

#1 - Functions only
#2 - Structs with all static methods and variables
#3 - Structs with all methods
#4 - Structs with all method operators
#5 - Structs with mixed methods and operators
#6 - Modules

 

[msongyboi]

I'm still learning so I've been switching very frequently, but now i'm at

structs with mixed methods and operators

I'm not sure how to use modules and interfaces correctly ㄴㄴㄴㄴㄴ

 

[deathismyfriend]

i like structs with all methods. if there static or not it doesnt matter to me.

this should also not be in this forum.

 

[mckill2009]

good choice, I often use that (method and operators), modules are implementations of full/part of sets of codes, interfaces are just API patterns...although I maybe wrong about interfaces as I dont use them...

 

[deathismyfriend]

i never use interfaces and the only time i use modules are for nestharus's Alloc as i like that one lol.

 

[Adiktuz]

according to Maggy, interfaces are not advisable (I think its coz they create a lot of unneeded code + slow)... I used to use them before... basically all they do is provide your structs with replaceable methods (can be replaced by another struct that extends your struct)

if ur familiar with other languages, it's like overwriting the methods of the parent class...

interface AI
    method Fire takes nothing returns nothing defaults nothing
endinterface

struct A extends AI
    method Fire takes nothing returns nothing
        call BJDebugMSG("A")
    endmethod
endstruct

struct B extends A
    method Fire takes nothing returns nothing
        call BJDebugMSG("B")
    endmethod
endstruct

struct C extends A
    method Fire takes nothing returns nothing
        call super //I forgot if this is the right syntax
        call BJDebugMSG("C")
    endmethod
endstruct

struct D extends A
endstruct

call A.Fire => returns message A
call B.Fire => returns message B
call C.Fire => returns message A and message C
call D.Fire => returns message A

personally, for API I mostly use struct method calls... I'm more used to it, plus it looks nice [Struct.method]

 

[mckill2009]

You must remove the 'defaults nothing' dude XD and all should extends AI...

 

[Garfield1337]

Ok guys, what's your choice of API when making a system:

#1 - Functions only
#2 - Structs with all static methods and variables
#3 - Structs with all methods
#4 - Structs with all method operators
#5 - Structs with mixed methods and operators
#6 - Modules

Doesn't this entirely depend on the system? API should contain everything that's public.

 

[deathismyfriend]

all my systems are 100 percent structs. so this can be used for every system. and is a good question

 

[mckill2009]

Doesn't this entirely depend on the system? API should contain everything that's public.

Modules yes, but that still contains API...and ofc, API's should be public (not the prefix ones)...

 

[Almia]

All of the codes (functions,modules, structs and methods)that are for the users to use.

 

[PurgeandFire]

I usually give an API for structs (and have my code in a struct) and offer function wrappers that call the struct methods.

I'll resort to modules if I need to, but only if it is necessary.