From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 2AADF21DE03 for ; Wed, 13 May 2015 01:16:39 -0700 (PDT) Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-04v.sys.comcast.net with comcast id TLGp1q00626dK1R01LGpP2; Wed, 13 May 2015 08:16:49 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-01v.sys.comcast.net with comcast id TLGo1q00J5LMg2101LGoAP; Wed, 13 May 2015 08:16:49 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150410193753.eklhad@comcast.net> <20150513071739.GG2917@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.4+ Date: Wed, 13 May 2015 04:16:48 -0400 Message-ID: <20150413041648.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1431505009; bh=PSBk+S9L/a8CUv6ueC8DQ8/jexRH3gjshgTHFGmKe2I=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=B8nm02vMzm2R4dVo/shHQWmuGpJCGLs/gPfUzkvm0PgntuX9aRj0n1Vql0TedaiRi i2jI3pN3tbCbdJhGxbN/goZE+uCqb3+D9WpNrSJY094cx50ZdR/Ad8Da8RsUXiQAcI 3KvXbfVJxfFCkghxUdReL3F1zq65h2wHoP8piuUUZDVuNGnrlQnKxSKbvBUCESVykY +tP6RiIOTCpMhqIdWrjmV+ONbE8i7lidyjrFE6TbesfvwTkNg/cGO2fFzbwZLikhbq bij42w3psrBjkW3t5X2F+QonR0EtCF0ZnvNoDRHHWMNnzp2g5qt5oXwfew7MeVJMXI WGRPF1C5Qz8Jw== Subject: [Edbrowse-dev] V 3.5.4 X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2015 08:16:39 -0000 > 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