by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Benjamin Dasnois
@Pign
@piboistudios There's an abi parameter to set through flags. Did you know that? =)
Gabriel Hayes
@piboistudios
@Pign I didn't. To be completely honest, I have no idea what an ABI is :)
Benjamin Dasnois
@Pign
It lets you decide whether to compile for C or C++
Jaime Domínguez
@jaimedominguez_twitter
Hello Can I convert a Int64 into 2 Int 32 ?
This is not working
Kevin Leung
@kevinresol
there is .high and .low
Mario Carbajal
@basro
Macro question: Is there a way to generate a call to a static function on a type that would not break if the context has variables defined with the same name as the type's first package?
For example { var js = "hi"; /macro adds this: / js.Syntax.code("hi"); }
Kevin Leung
@kevinresol
Prepend std.
Mario Carbajal
@basro
Wont that also break when a var is named std?
Also, I need this for non std packages too.
Kevin Leung
@kevinresol
Don't name a variable as std :)
Mario Carbajal
@basro
Well, as I said, it's not just std. My library makes calls to jsasync.impl.Helper static methods
so users would be forbidden from having jsasync as a variable too
Kevin Leung
@kevinresol
It has nothing related to the standard library
Mario Carbajal
@basro
I don't follow
I mean that my macro library is injecting calls to methods inside a package named jsasync
Kevin Leung
@kevinresol
Just prepend that magic word to access packages from root
Mario Carbajal
@basro
so if a user has a var jsasync the macro breaks
oh
Kevin Leung
@kevinresol
You can also declare a inline function at the beginning of the scope and call that instead
Mario Carbajal
@basro
the std thing is good enough! thanks @kevinresol
is prepending std. the normal way to deal with this?
Kevin Leung
@kevinresol
Define normal
Mario Carbajal
@basro
if most other macro libraries are doing this to avoid this problem
Kevin Leung
@kevinresol
It never occurred to me that ppl use used package names as their var names
at the root there is no way to completely avoid the problem you mentioned
Mario Carbajal
@basro
btw, adding a function at the start of the scope is not good enough because of static imports
import jsasync.JSAsync.func as jsasync;
Kevin Leung
@kevinresol
The inline function way i mentioned may be better. Because you can use some really weird name to avoid clash
Mario Carbajal
@basro
^
wanting to do that is what prompted me to want to fix this in my macro
although it's a bit silly to name it the same as the lib ;P
but in the end that's the only function the end user cares about
Kevin Leung
@kevinresol
insert this to the very beginning of the scope should work:
inline function __jsasync_there_is_no_way_this_function_will_clash_with_anything(args)
  return jsasync.JSAsync.func(args);
Jaime Domínguez
@jaimedominguez_twitter
Hey that low doesnt work
var dataRaw:haxe.Int64 = 10741971081547577991; trace("dataRaw.high:"+dataRaw.high); trace("dataRaw.low:"+dataRaw.low);
Kevin Leung
@kevinresol
what is "doesn't work"?
Jaime Domínguez
@jaimedominguez_twitter
dont worry
try haxe doesnt really work with that
but i mamanged to fix stuff anyway
thanks
Mr zhan
@sonygod
hi,what's lmmix version of hashlink in haxe Benchmark as mentioned here https://haxe.org/blog/haxe-4.1.0-release/
Sylvio Sell
@maitag
did started pure haxe BigInt implementation now (yet another ]robust[wheelchange ;) ... thx.cores one
was to rusty ^~
(to test at all or specific targets only clone and do hxp help for instructions!)
Sylvio Sell
@maitag
wanna put it into haxelib if polished ... but not sure what features is need today (^_^) ..
[i only need to make SRP-sample for my old peote-net lib to avoid ssl-overhead]