From: Mike Hearn <mike@plan99.net>
To: "Jorge Timón" <jtimon@jtimon.cc>
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?)
Date: Thu, 19 Feb 2015 18:30:10 +0100 [thread overview]
Message-ID: <CANEZrP07pZ_SpKJVeAsnR+-663G670_ES1qJZwbNDT4rGHE24g@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDqk0GbzWV-J1ZqTgeSpruiq=sxTmt6bquJ406WNDaiVrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 744 bytes --]
next prev parent reply other threads:[~2015-02-19 17:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABm2gDpReRty6TdfMDssjF27XgC_SYs_U__SFBNdsYW24Mzh8w@mail.gmail.com>
[not found] ` <54CC0E1D.7030409@voskuil.org>
[not found] ` <CABm2gDqM6q24tPEBKSHbbVQu-mvfV37PNc4hD=VjyRHk2jujZw@mail.gmail.com>
[not found] ` <54D0414F.6030806@voskuil.org>
[not found] ` <CABm2gDo_sYjNWU6EEsKmOXt5uUu87Lj1oFzqio79MxSx2SYrNg@mail.gmail.com>
[not found] ` <54DE7601.4070509@voskuil.org>
[not found] ` <CABm2gDpt60B=Sf_2X9xt4fPH7x4fff7K4h36XfosHigV5tP+4Q@mail.gmail.com>
[not found] ` <54DF07A5.1060004@voskuil.org>
[not found] ` <CABm2gDoS+XOR7Ugt91kNWNdvwsb1_Zb-aO0sma_Xps2Sx-0N5g@mail.gmail.com>
[not found] ` <54DF2E80.5060506@voskuil.org>
2015-02-14 13:13 ` [Bitcoin-development] On Rewriting Bitcoin (was Re: [Libbitcoin] Satoshi client: is a fork past 0.10 possible?) Peter Todd
2015-02-14 14:23 ` Tamas Blummer
2015-02-14 19:04 ` Adam Back
2015-02-14 19:29 ` Bryan Bishop
2015-02-15 17:11 ` Peter Todd
2015-02-14 20:00 ` Jorge Timón
2015-02-15 0:05 ` Luke Dashjr
2015-02-15 17:02 ` Peter Todd
2015-02-15 17:13 ` Tamas Blummer
2015-02-15 17:21 ` Peter Todd
2015-02-15 21:48 ` joliver
2015-02-19 3:32 ` Troy Benjegerdes
2015-02-19 3:44 ` Peter Todd
2015-02-19 5:22 ` Tamas Blummer
2015-02-19 5:27 ` Tamas Blummer
2015-02-19 14:03 ` Bryan Bishop
2015-02-19 14:09 ` Tamas Blummer
2015-02-19 17:16 ` Jorge Timón
2015-02-19 17:30 ` Mike Hearn [this message]
2015-02-19 21:43 ` Sean Gilligan
2015-02-19 22:53 ` Angel Leon
2015-02-20 3:47 ` Jorge Timón
[not found] ` <54EE17DD.7050309@voskuil.org>
2015-03-25 8:04 ` Eric Voskuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP07pZ_SpKJVeAsnR+-663G670_ES1qJZwbNDT4rGHE24g@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=jtimon@jtimon.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox