From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: OT: Commercial Support and Programming Languages
Date: Wed, 7 Nov 2007 16:07:51 +0000 [thread overview]
Message-ID: <200711071607.51274.jon@ffconsultancy.com> (raw)
In-Reply-To: <4731E008.9060605@marseda.com>
On Wednesday 07 November 2007 15:55, Alan Falloon wrote:
> If you write one of those books, I will buy it.
>
> Specifically, I want books covering: packaging ocaml for release, camlp4
> in detail, advanced ocamlbuild, and getting the most out of emacs and/or
> vim.
>
> Maybe you could get Nicolas Pouillard to consult on camlp4 and ocamlbuild.
This is a chicken and egg problem. Without tutorial information on these
subjects I cannot learn about them in order to write a book on them.
Perhaps it would be best if everyone collaborated in writing wiki pages:
http://www.ocaml-tutorial.org/introduction_to_gtk
http://www.ocaml-tutorial.org/camlp4_3.10
http://www.ocaml-tutorial.org/ocaml_and_the_web
http://www.ocaml-tutorial.org/compiling_ocaml_projects
Another subject that I have discovered from my work on F# is the usefulness of
interoperability, specifically being able to manipulate Excel spreadsheets
from F#. I'm writing web analytics software for our company in OCaml and I'd
like to inject the results into OpenOffice's spreadsheet. Any idea how to do
that?
As an aside, although I am very tempted by the idea of writing a mainstream
book on OCaml I am concerned that I might undercut our sales of OCaml for
Scientists. This is particularly worrying because that book still accounts
for 50% of our revenue from sales...
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
next prev parent reply other threads:[~2007-11-07 16:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 12:01 Smoke Vector Graphics: source code licenses for sale Jon Harrop
2007-11-04 15:06 ` [Caml-list] " Oliver Bandel
2007-11-04 16:12 ` skaller
2007-11-04 16:48 ` Oliver Bandel
2007-11-04 17:45 ` skaller
2007-11-04 21:29 ` Oliver Bandel
2007-11-04 17:47 ` David Allsopp
2007-11-04 21:25 ` Oliver Bandel
2007-11-04 16:58 ` Industry looks for commercial OCaml support? Oliver Bandel
2007-11-04 17:52 ` [Caml-list] " skaller
2007-11-04 21:39 ` Oliver Bandel
2007-11-05 3:32 ` skaller
2007-11-05 3:58 ` OT: Commercial Support and Programming Languages Robert Fischer
2007-11-05 5:04 ` [Caml-list] " Jon Harrop
2007-11-07 15:55 ` Alan Falloon
2007-11-07 16:07 ` Jon Harrop [this message]
2007-11-07 16:35 ` [Caml-list] " Edgar Friendly
2007-11-07 16:41 ` Jon Harrop
2007-11-07 17:16 ` Edgar Friendly
2007-11-07 18:46 ` Christophe TROESTLER
2007-11-07 19:28 ` Richard Jones
2007-11-05 7:22 ` [Caml-list] " skaller
2007-11-05 5:05 ` [Caml-list] Industry looks for commercial OCaml support? Jon Harrop
2007-11-04 18:29 ` [Caml-list] Smoke Vector Graphics: source code licenses for sale Vincent Hanquez
2007-11-08 18:28 ` Alexandre Pilkiewicz
2007-11-08 19:09 ` Luc Maranget
2007-11-08 20:24 ` Alexandre Pilkiewicz
2007-11-08 20:53 ` Edgar Friendly
2007-11-08 23:04 ` Oliver Bandel
2007-11-08 19:14 ` Brian Hurt
2007-11-08 23:08 ` Richard Jones
2007-11-09 12:16 ` Gerd Stolpmann
2007-11-09 12:31 ` Richard Jones
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=200711071607.51274.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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