Best strategy class on multi target

[Tim M]

When building a class on different targets what have you found to be the best strategy?

For example, if I need a generic Socket.hx class, how do you keep yourself organized when targeting -swf -hl etc? So far we're using conditional compile (#if #else) on the target instance declaration, but I was thinking we could use a internal implementation with inlines:

#if flash
import flash.SocketImpl
#else if hl
import hl.SocketImpl
#end

class Socket {

var socket:SockImpl;

}

Thoughts?

[Franco Ponticelli]

My preference is for old style interfaces.

--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.

[Tim M]

Thanks for the reply Franco,

Can you elaborate on the specifics? Are you conditional compiling each include? A gist would be nice.

[Philippe Elsass]

We often use typedef declarations and import them like classes:

// video/PlayerVideo.hx

package video;

#if flash

typedef PlayerVideo = video.flash.PlayerVideoImpl;

#else

typedef PlayerVideo = video.js.PlayerVideoImpl;

#end 

[Nicolas Cannasse]

In Haxe 3.4 you can have a Socket.hx class, then a Socket.js.hx , Socket.flash.hx etc for each implementation. Adding @:coreApi to them which would enforce that they respect the Socket.hx API is not yet done but will be soon.

NC

[Philippe Elsass]

What are the rules to choose the file?  Based on target or also custom flags? 

[Nicolas Cannasse]

Le 15/04/2017 à 13:27, Philippe Elsass a écrit :
> What are the rules to choose the file? Based on target or also custom
> flags?

Only target for now, this limits the number of file lookups.

Nicolas