|
From: doug s. <hig...@ho...> - 2013-04-16 15:11:54
|
> > Hey all, so spidermonkey-17 is released, which is going to be the last > spidermonkey that has a C API; after this it's C++ only. > > Should we port freewrl to C++ or freeze our compatibility to > spidermonkey-1.5 through 17 ? > What do you think Ian? Would you like to keep upgrading or would you prefer a freeze? -Doug The last time the freewrl C vs C++ issue came up, C won. I had done a test where I got freewrl to compile as C++. But then it was just C code that took longer to compile on my slow old machine, and had some awkward areas that would need a rewrite. We do have some C++ at-the-margin: libs and plugins. I think there are ways to wrap a C++ library with a C interface, if necessary. But that could be more work for the main javascript maintainer - that's been you Ian - with unknown gain in functionality. My guess: freeze. |