From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-11v.sys.comcast.net (resqmta-ch2-11v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:43]) by hurricane.the-brannons.com (Postfix) with ESMTPS id B916721DE03 for ; Tue, 12 May 2015 02:15:24 -0700 (PDT) Received: from resomta-ch2-13v.sys.comcast.net ([69.252.207.109]) by resqmta-ch2-11v.sys.comcast.net with comcast id SxFY1q0022N9P4d01xFYQA; Tue, 12 May 2015 09:15:32 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by resomta-ch2-13v.sys.comcast.net with comcast id SxFY1q0095LMg2101xFYnu; Tue, 12 May 2015 09:15:32 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20150410193753.eklhad@comcast.net> <20150512073215.GF2917@toaster.adamthompson.me.uk> User-Agent: edbrowse/3.5.4+ Date: Tue, 12 May 2015 05:15:32 -0400 Message-ID: <20150412051532.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=1431422132; bh=A7vnDdkCNC1bFj9Ouy1UXzHlplFK23iZR2JHaxe95wE=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=fJtWR7EAlqfdnOzCprnnvYtP+KUoPBfBfen/IRijt9A4zVjsRE7kpLxyM5ATh5y9o P+jzBLQVJTlMNlTveS/ClCTHwct5IZBhuY7GRRSyYLtdDNBvm3BYG8598XfjYQ2osr 12QU3YhsOoo6hCRitlCP7KGPfeydPM2j4NL75LgYsjSpDaoq9uSobN35PKQ7iz41BV jhgtpp9kokeTI7VHBNlfleHXMNnENipY6hFYa20S1U1XDwxXpeWjytDWuvlEQ5VKsB Ht1l9u/USQipQzQXN4K0kopRY+1IZEyOq7KgKf0u2RbIe2oMFuK/9NqIXiJMVI1XhZ wshn7rZVfKg3g== 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: Tue, 12 May 2015 09:15:24 -0000 > Writing the jseng-duk.c process ... And the cool part is, such work can take place independently of other work on edbrowse. To use the new process, if we decide to do so, is just a change of makefile. This is a switch back from c++ to c, but I (wisely) used almost none of the c++ features, save those needed for the mozilla api, and yes a few strings, cause I was being lazy. String effects; for example, to gather side effects of running js and pass them back to edbrowse. I think the easiest path is to copy the stringAndString etc routines over, for growing strings dynamically. They're not perfect but we're all use to them. stringfile.c lines 150 to 227 would probably suffice. If we continue down this path we might want a string + url sourcefile to be shared between the two processes. Nobody likes duplicated code. Common is currently jseng-moz.cpp lines 54 through 548, plus the aforementioned string management routines, so over 600 lines, and that's just too much code to leave duplicated in the long run. Karl Dahlke