From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by hurricane.the-brannons.com (Postfix) with ESMTP id C6B48786FA for ; Wed, 6 Aug 2014 13:49:59 -0700 (PDT) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta04.westchester.pa.mail.comcast.net with comcast id bYLy1o0021ei1Bg54YpAf9; Wed, 06 Aug 2014 20:49:10 +0000 Received: from eklhad ([IPv6:2601:4:5380:4ee:21e:4fff:fec2:a0f1]) by omta24.westchester.pa.mail.comcast.net with comcast id bYo81o0095LMg213kYo9sq; Wed, 06 Aug 2014 20:48:09 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Wed, 06 Aug 2014 16:45:44 -0400 Message-ID: <20140706164544.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=1407358150; bh=BKDAvxaN7AmrlyeuunaafKFRtoK3+MB+hv0/PWKvMJA=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=rdeUE14o/KyJR/MdXb2WoGIhr7dG5BGB51MY82jgvH4JbzmDMsZMLGRPss5IZUiih hyS3fPRkLrRyIYMLAyxuu6XdVYICVXY9rzI1A7uYmi7ENNmysWnY/G8X07JfxxB6j0 u60FVTQiR4R5jDhDwODQAdXzH8B+1/3vgqX9yyfnIJh8Obasi/k3KjCFJDUqV/eLWX MtkG4z8Xy2b8J77rAe93WQE7ejWNqhxH6JcAmDujfI9JeFHVnfvgfMfi3b3PjClcY4 hugxM18rNYxkfobCv1vwmwALBVJQ6JJ5UT/hwuKxBEV/c6efCfxTjHt9wZTnduL3ww 5ZL9+LPnaR8sA== Subject: [Edbrowse-dev] Using C99? 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, 06 Aug 2014 20:50:00 -0000 I would very much like to port edbrowse to windows someday, and so would like the option of compiling under visual studio. Yes the bool type would be especially nice since we do use it for the cpp files, and using eb_bool for the c files is a bit of a workaround that I don't especially like. Some of your other changes would be nice as well. Maybe you can do a little research and see which ones we can make while preserving a reasonable amount of portability, including, someday, the option of a windows port. Someone once ported this to mac, thus the makefile.osx, but that was a long time ago and nobody has kept up with it. makefile.osx is I'm sure out of date by now. Karl Dahlke