From: Peter Zotov <whitequark@whitequark.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml on the Arduino (or similar)
Date: Mon, 30 Jun 2014 20:50:10 +0400 [thread overview]
Message-ID: <623699e8c56293d1f90cc53703aa0dcb@whitequark.org> (raw)
In-Reply-To: <20140119085847.GA29276@notk.org>
On 2014-01-19 12:58, Adrien Nader wrote:
> On Sun, Jan 19, 2014, Jon Harrop wrote:
>>
>>
>> I don't suppose anyone has retargeted OCaml to run on an Arduino or
>> similar?
>>
>>
>>
>> I'm just getting into Arduino programming and writing async code in
>> C++ is
>> just horrible. L
>
> There is OCaPIC fro PIC18 (or above iirc):
> http://www.algo-prog.info/ocapic/web/index.php?id=OCAPIC
I second this suggestion. Porting OCaPIC runtime to run on AVR (or
Cortex-M ARM) is
the easiest way.
--
Peter Zotov
sip:whitequark@sipnet.ru
next prev parent reply other threads:[~2014-06-30 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 0:12 Jon Harrop
2014-01-19 8:58 ` Adrien Nader
2014-06-30 16:50 ` Peter Zotov [this message]
2014-01-19 10:45 ` oliver
2014-01-19 15:58 ` Dario Teixeira
2014-01-19 16:05 ` Adrien Nader
2014-06-30 14:02 ` Goswin von Brederlow
2014-07-01 6:29 ` Anil Madhavapeddy
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=623699e8c56293d1f90cc53703aa0dcb@whitequark.org \
--to=whitequark@whitequark.org \
--cc=caml-list@inria.fr \
/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