On Wed, May 13, 2015 at 09:15:57AM -0400, Karl Dahlke wrote:
> > since this is in C, I was just going to use the already built edbrowse modules.
> 
> Reviewing the various undefines, most are global variables,
> which can of course be moved, and then perhaps just a couple
> functions to move or stub.
> Here is what I propose, and I would be happy to lay this groundwork if you like.
> Move a few functions and variables around,
> and perhaps stub one or two in jseng-moz.cpp,
> so that edbrowse and edbrowse-js share stringfile.o url.o messages.o.
> This seems to be the best place to draw the circle around.
> Of course I'd need separate make rules to compile these three sources
> stringfile++.o url++.o messages++.o
> when folding them into the c++ program jseng-moz.
> I haven't used make in this way before but I'm sure it can be done.
> I can work on this in preparation for your work on different js engines,
> or I can just wait to see what comes of your duktape research.
> As you wish.

I'd say go for it, may be make a separate header file for these (included in
eb.h of course). For the c++ versions I'd be tempted to leave jseng-moz.cpp as
is at the moment. If duktape fails we can revisit this.

Regards,
Adam.