public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Caleb Roger Davis <moabtek@gmail•com>
To: Felipe Micaroni Lalli <micaroni@walltime•info>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin development (testing & where to get Wallet code)
Date: Wed, 30 Jul 2014 01:38:39 -0600	[thread overview]
Message-ID: <CALEpF5aryPkg6b+4i-xc8L_d53FLWc_xhnZFY4Zjk_mEm=qDhA@mail.gmail.com> (raw)
In-Reply-To: <7CDDF63C-8451-465C-B98D-20E224045EF2@walltime.info>

[-- Attachment #1: Type: text/plain, Size: 2862 bytes --]

Yes, I was thinking something on the JVM, I have a big interest in Clojure
right now (am a long time Java dev, since 1996).

I do not know if I want to tackle writing bitcoin in Clojure, but I want to
create a tool kit first to learn more about how it works.

Caleb


On Tue, Jul 29, 2014 at 5:12 PM, Felipe Micaroni Lalli <
micaroni@walltime•info> wrote:

> May I ask you which language? I'd love to implement Bitcoin in Clojure or
> Scheme.
>
> Related:
> http://bitcoin.stackexchange.com/questions/5344/has-anyone-ported-the-bitcoin-software-to-pure-clojure
>
>
>
>
> Sincerely,
>
>
> Felipe Micaroni Lalli
>
> Walltime: https://walltime.info
> Bitcoin Paranoid Android developer
> PGP ID: 0x4c0afccfed5cde14
> BTC: 1LipeR1AjHL6gwE7WQECW4a2H4tuqm768N
>
> On 29/07/2014, at 19:32, Caleb Roger Davis <moabtek@gmail•com> wrote:
>
> > I have several Bitcoin contributions I would like to make, mostly for
> learning purposes to get started:
> >
> >       • I would like to contribute to unit and/or other types of tests
> (code), not production code.
> >       • I would like to understand the Bitcoin code (as much as possible
> from top to bottom)
> >       • I would like to write a Bitcoin wallet in another language (so
> would like to know where to get the "Bitcoin - Core Wallet" code, but not
> sure where it resides.
> > I am a seasoned software developer, but I do need direction on where to
> get started.  If there is a wiki doc for new developers that would reduce
> my searching and experimentation that would be great.
> >
> > For each of the three items above, I would like to know the tools and
> frameworks I would need to understand and initially work on tests ( how to
> run the existing tests to get code coverage and find where coverage is
> needed, what is the preferred IDE and full development stack etc ), and
> also where to get started looking at the bitcoin core code and also the
> wallet code (where is the initial starting point and then I could trace
> from there ).
> >
> > Is there a separate area (github & mailing list) for core wallet
> development?
> >
> > Sincerely,
> >
> >
> > --
> > Caleb
> >
> >
> ------------------------------------------------------------------------------
> > Infragistics Professional
> > Build stunning WinForms apps today!
> > Reboot your WinForms applications with our WinForms controls.
> > Build a bridge from your legacy apps to the future.
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk_______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists•sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>


-- 
Caleb
M: 801.896.3278
https://plus.google.com/+CalebRogerDavis/about

[-- Attachment #2: Type: text/html, Size: 4075 bytes --]

  reply	other threads:[~2014-07-30  7:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 22:32 Caleb Roger Davis
2014-07-29 23:12 ` Felipe Micaroni Lalli
2014-07-30  7:38   ` Caleb Roger Davis [this message]
2014-07-30  8:27     ` Andreas Schildbach
2014-07-30  8:37 ` Wladimir

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='CALEpF5aryPkg6b+4i-xc8L_d53FLWc_xhnZFY4Zjk_mEm=qDhA@mail.gmail.com' \
    --to=moabtek@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=micaroni@walltime$(echo .)info \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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