1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YOUvZ-0000c5-VM
for bitcoin-development@lists.sourceforge.net;
Thu, 19 Feb 2015 17:30:17 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.172 as permitted sender)
client-ip=74.125.82.172; envelope-from=mh.in.england@gmail.com;
helo=mail-we0-f172.google.com;
Received: from mail-we0-f172.google.com ([74.125.82.172])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YOUvY-0003hp-Jy
for bitcoin-development@lists.sourceforge.net;
Thu, 19 Feb 2015 17:30:17 +0000
Received: by wesk11 with SMTP id k11so1068674wes.11
for <bitcoin-development@lists.sourceforge.net>;
Thu, 19 Feb 2015 09:30:10 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.121.168 with SMTP id ll8mr10671829wjb.35.1424367010858;
Thu, 19 Feb 2015 09:30:10 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.194.188.11 with HTTP; Thu, 19 Feb 2015 09:30:10 -0800 (PST)
In-Reply-To: <CABm2gDqk0GbzWV-J1ZqTgeSpruiq=sxTmt6bquJ406WNDaiVrA@mail.gmail.com>
References: <CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
<54DE7601.4070509@voskuil.org>
<CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
<54DF07A5.1060004@voskuil.org>
<CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
<54DF2E80.5060506@voskuil.org>
<20150214131320.GA26731@savin.petertodd.org>
<3D4F2E23-CADE-4FE7-B960-3F79815E868C@bitsofproof.com>
<20150215170228.GB21269@savin.petertodd.org>
<E0CB8E24-C67D-48B1-8D9F-2B71BAF13446@bitsofproof.com>
<20150219033205.GS14804@nl.grid.coop>
<065C5F2E-FC1D-4994-A39A-9125D663FC71@petertodd.org>
<EEF57CF9-5AFC-465B-ABA7-1B53118D6A5E@bitsofproof.com>
<CABaSBawRXzeoHEvVBJK_JpvrtZq6tzhASRf3JLsz=skbrMq1QA@mail.gmail.com>
<5944A0DB-DFE9-4D30-9049-AD38F37E3756@bitsofproof.com>
<CABm2gDqk0GbzWV-J1ZqTgeSpruiq=sxTmt6bquJ406WNDaiVrA@mail.gmail.com>
Date: Thu, 19 Feb 2015 18:30:10 +0100
X-Google-Sender-Auth: Di9xehYCJzwzeF_c4mF3PDfJDn0
Message-ID: <CANEZrP07pZ_SpKJVeAsnR+-663G670_ES1qJZwbNDT4rGHE24g@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=089e01227e9eb64aec050f744972
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1YOUvY-0003hp-Jy
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] On Rewriting Bitcoin (was Re:
[Libbitcoin] Satoshi client: is a fork past 0.10 possible?)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 17:30:18 -0000
--089e01227e9eb64aec050f744972
Content-Type: text/plain; charset=UTF-8
>
> He didn't said "a project for all possible language bindings", just
> java bindings. Other languages' bindings would be separate projects.
Yes/no/sorta.
Java/JNA bindings can be used from Python, Ruby, Javascript, PHP as well as
dialects of Haskell, Lisp, Smalltalk and a bunch of more obscure languages
like Scala, Kotlin, Ceylon, etc.
It makes more sense to talk about bindings to particular runtimes these
days, rather than particular languages.
--089e01227e9eb64aec050f744972
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">He didn't said "a project for all possi=
ble language bindings", just<br>
java bindings. Other languages' bindings would be separate projects.</b=
lockquote><div><br></div><div>Yes/no/sorta.</div><div><br></div><div>Java/J=
NA bindings can be used from Python, Ruby, Javascript, PHP as well as diale=
cts of Haskell, Lisp, Smalltalk and a bunch of more obscure languages like =
Scala, Kotlin, Ceylon, etc.</div><div><br></div><div>It makes more sense to=
talk about bindings to particular runtimes these days, rather than particu=
lar languages.</div></div></div></div>
--089e01227e9eb64aec050f744972--
|
