04:23 <uniquejokes> hey can anyone help me with my pony CreateProcess windows ffi issue

04:24 <uniquejokes> I have a good explanation of my issue on stackoverflow: http://stackoverflow.com/questions/42238248/ponylang-windows-createprocess-ffi

04:24 <uniquejokes> feel free to reply to stack overflow to recv credit :)

17:01 <aav> is there any symbol (not alphanumeric) which can be used as a part of class/actor/type/primitive name?

18:52 <jemc> aav: no, not under the current naming rules

18:53 <jemc> I believe part of the intent of those restrictions are to make it so that the mangled of functions that get compiled have sane names if you want to call them from C

18:54 <jemc> that is, I'm pretty sure LLVM supports arbitrary unicode in function names, but some users want to be able to create Pony libraries that can be called from C

19:00 <aav> jemc: makes sense. actually i have the following issue, maybe you have some suggestion on how to solve it

19:01 <aav> i'm currently working on ProtoBuf support for pony. as you maybe know, ProtoBuf supports nested messages

19:01 <aav> and i want to reflect it somehow in generated pony class names

19:02 <aav> i.e. if i have 'message Outer { message Inner {....}}' i want to generate something like 'class Outer_Inner ...'

19:03 <aav> without separator it may lead to very unreadable code. i understand the limitation, but maybe you can suggest some other solution, which will fit Pony well

19:09 <jemc> I think I remember having the same frustration when working on pony-capnp, honestly - let me look back to see what I did

19:10 <aav> jemc: thanx. and, btw, i'm re-using code_gen.pony from pony-capnp

19:12 <jemc> I think the answer is that I didn't have a very good solution :/

19:13 <jemc> where capnproto had "scoped" types, I just mashed the names together, for example `CodeGeneratorRequest::RequestedFile` in C++ became `CodeGeneratorRequestRequestedFile` in pony

19:13 <jemc> for things like enums, the solution was worse

19:13 <aav> that's what i do now

19:14 <jemc> sorry, not enums, groups, I mean

19:15 <aav> there will be enums in protobuf, and they will also sloghtly weird :)

20:03 <triangle345> hey guys i was wondering what is the process for native compiled dll's for use with ponylang packages. I was going to extend the Process package to work with windows but looks like i may need a native dll to access the ffi correctly. Is there some place native libraries are build to be used for packages?

20:03 <triangle345> i mean a custom native dll.. my own native dll

20:15 <Praetonus> triangle345: The usual way for standard library packages is to add the functions to libponyrt

20:27 <triangle345> i see

20:27 <triangle345> thanks

20:29 <triangle345> is there a specific place in libponyrt. and also what about building the dll. would i need to include a separate makefile?

20:29 <triangle345> or build script

20:34 <triangle345> ah nm i see so i just call directly from libponyrt dll?

20:42 <SeanTAllen> im not quite sure what you are thinking

20:43 <SeanTAllen> could you step back triangle345 and explain what you want to do that requires you to add c code?

20:43 <SeanTAllen> we could probably tell you how to do what you are asking but i think its best to revisit what you are trying to do and if what you are asking about now is the correct way to go about it

21:41 <triangle345> i am trying to add windows functionality to process monitor

21:41 <triangle345> currently only supports linux

21:41 <triangle345> and in order to call CreateProcess it is easier to create a native function and call from pony

21:45 <SeanTAllen> it supports more than linux, it supports any Unix.

21:46 <SeanTAllen> have you looked at how that is implemented in the runtime triangle345?

21:46 <SeanTAllen> i'd suggest looking at how the runtime c code to support process monitor is implemented

21:46 <SeanTAllen> then look at how TCPConnection support for windows and unix is done in the c runtime code

21:46 <SeanTAllen> and that should give you a good idea of how to go about it

21:46 <SeanTAllen> there would be no DLL that you would be creating and loading

21:46 <triangle345> i see ok thanks. I will take a look

21:47 <SeanTAllen> if you have questions, you can ping me here or drop me an email

21:52 <triangle345> thanks i will let you know

22:17 <triangle345> is there some documentation on how the asio event system works

22:21 <SeanTAllen> no

22:21 <SeanTAllen> but i can help you through it

22:22 <SeanTAllen> triangle345: you are going to be most interested in iocp.c

22:23 <SeanTAllen> in particular void pony_asio_event_subscribe(asio_event_t* ev)

22:23 <SeanTAllen> and

22:23 <SeanTAllen> void pony_asio_event_unsubscribe(asio_event_t* ev)

22:24 <SeanTAllen> then also

22:24 <SeanTAllen> event.c

22:25 <SeanTAllen> https://www.irccloud.com/pastebin/0qrihg6C/

22:25 <SeanTAllen> and the rest of the functions in that file

22:25 <SeanTAllen> asio runs in its own threads

22:25 <SeanTAllen> err

22:25 <SeanTAllen> thread

22:26 <SeanTAllen> check out `void pony_asio_event_send(asio_event_t* ev, uint32_t flags, uint32_t arg)`

22:26 <SeanTAllen> and trace before that for how things get to that point

22:26 <SeanTAllen> from there

22:27 <SeanTAllen> the event is delivered to the owning actor (which you can see in asio_event_t in event.h)

22:27 <SeanTAllen> that in turn will cause `_event_notify` to be called on the actor

22:27 <SeanTAllen> which you can see examples of in many asio handling actors in the standard library

22:29 <triangle345> thank you. i will take a look