[Edbrowse-dev] V 3.5.4

[Karl Dahlke <eklhad@comcast.net>]

> Tbh, since this is in C,
> I was just going to use the already built edbrowse modules.

Do you plan to link stringfile.o and url.o into jseng-duk executable?
Sounds good, but I'm sure through external references you'll get
the whole damn thing in your lap, including main.o,
which you can't accommodate.
I'm sure we would need to do some rearranging of routines into sourcefiles,
differently than is done today.
Like the way I moved related functions into plugin.c recently.
I'm sure there's a C graphing tool out there showing functions calling
other functions that would confirm or deny this,
Or just try
cc stringfile.o url.o
and note the zillions of undefines, besides main as expected.

Second, there are a couple of routines that act a little differently in the two processes.
I don't remember which ones or how or why they act differently,
I only remember when I wrote jseng-moz.cpp that there were a couple instances like that.
Would it help if I looked through these functions side by side
and determined, and reported, which ones act differently?

Meantime I'd say just carry the 500 lines of code along in your new process,
and don't try to share any modules yet, unless and until we're pretty sure
we want to go down that path, and then it will be well worth
the effort to rearrange functions in sourcefiles and share modules.

Karl Dahlke