03:14 <SeanTAllen> Amun_Ra: ?

04:46 <patroclos> are there any resources on how to use pony arrays and strings in c?

10:00 <Amun_Ra> SeanTAllen: I did not type "/j"

12:14 <SeanTAllen> patroclos: what are you looking to do?

18:51 <patroclos> SeanTAllen: I'm looking to pass an Array[String] to a c function and have it access the underlying char buffer of the strings

18:52 <SeanTAllen> hmmm

18:53 <SeanTAllen> you can get the c string representation of the strings by calling .cstring() on them.

18:53 <SeanTAllen> i havent ever tried to call .cstring on pony strings from c, you can do it but passing the cstring() result itself it probably easier.

18:54 <SeanTAllen> in general all the c-ffi i do is stuff that is already nice and c friendly. so i cant really help much. but i think whatever you work out would be a great blog post.

18:55 <SeanTAllen> and an excellent addition to the c-ffi section of the tutorial

18:56 <patroclos> well, all I figured out until now is that I can pass a pony array directly as a ponyint_array_t*

18:58 <SeanTAllen> there are not many (any?) libraries for working pony objects from c in a nice fashion. it can be done but, i think that would be an interesting project.

19:00 <SeanTAllen> aturley_: has a change we made to the pony compiler that allows you to export definitions of pony objects for use in c that would be helfpul but we haven't gotten around to implementing that yet. Eventually he is going to write up a RFC for that.

22:55 <dougmacdoug> anyone know enough about the compiler/optimizer to know if redirected function calls get optimized away.. in other words if I have fun foo(x: Int) => /*do stuff*/ and then I have an alias method like fun bar(x: Int)=> foo(x)

22:57 <dougmacdoug> does the assembled code actually make the bar call, then the foo call or does it just get optimized to call foo

22:58 <SeanTAllen> it should inline that bar call

22:58 <dougmacdoug> nice.. seems reasonable