Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-18 Thread Chris Lemmons
I've been toying with Rust plugins for ATS, but certainly nothing in production. It's worth considering, though, that the plugin architecture is specifically designed so that users can keep their plugins private if they wish, so there may be some plugins we don't know about out there. If we make a

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Bryan Call
We shouldn’t be concerned about the support for writing plugins in Java and calling into C vs C++, since no one is doing it and I haven’t heard of anyone attempting it. We should look at Luajit and V8 support for calling C++ APIs since that is the path we are on and going down. -Bryan > On M

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Jason Giedymin
Sounds like a disaster. -Jason > On May 17, 2019, at 12:51 PM, Bryan Call wrote: > > Having a plugin that would call into Java and then back into C sounds like a > really bad idea. > > -Bryan > > >> On May 17, 2019, at 8:59 AM, Walt Karas >> wrote: >> >> http://jonisalonen.com/2012/calli

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Walt Karas
Is it somehow inherently more dangerous or disaster-prone than calling into Lua code that calls back into the C TS API? On Fri, May 17, 2019 at 11:59 AM Jason Giedymin wrote: > Sounds like a disaster. > > -Jason > > > On May 17, 2019, at 12:51 PM, Bryan Call wrote: > > > > Having a plugin that

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Bryan Call
Having a plugin that would call into Java and then back into C sounds like a really bad idea. -Bryan > On May 17, 2019, at 8:59 AM, Walt Karas > wrote: > > http://jonisalonen.com/2012/calling-c-from-java-is-easy/ > > I don't know if there is a way to call Java from C or C++, which you would

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Jason Kenny
I really think we should be doing a c and c++ API. Allen had a PR at one point to move some source around to make this easier to do. Jason On Fri, May 17, 2019 at 10:55 AM Leif Hedstrom wrote: > > > > On May 17, 2019, at 9:48 AM, Walt Karas > wrote: > > > > But are there people who write plugi

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Walt Karas
http://jonisalonen.com/2012/calling-c-from-java-is-easy/ I don't know if there is a way to call Java from C or C++, which you would also need to have a Java plugin. If no one is currently doing anything like this we probably shouldn't worry about it. On Fri, May 17, 2019 at 10:54 AM Leif Hedstro

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Leif Hedstrom
> On May 17, 2019, at 9:48 AM, Walt Karas > wrote: > > But are there people who write plugins in other languages (like Java for > example) that can call C functions, but not C++ functions? If so, wouldn't > this break their plugins? Never heard of that. How would someone do that ? You can

Re: [PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Walt Karas
But are there people who write plugins in other languages (like Java for example) that can call C functions, but not C++ functions? If so, wouldn't this break their plugins? On Fri, May 17, 2019 at 8:41 AM Leif Hedstrom wrote: > If we change this, such that all plugins must be compiled with C++

[PROPOSAL] Make all plugins require C++ compiler

2019-05-17 Thread Leif Hedstrom
If we change this, such that all plugins must be compiled with C++ compilers, we have the liberty of using C++’ism in the public interfaces, such as ts/ts.h and ts/remap.h. This has benefits, such as being able to expose internal APIs of ATS without going through complex glue interfaces and opaq