caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrew Herron <thespyder@programmer.net>
To: Jordan W <jordojw@gmail.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] CommonML: An opinionated build/package/develop workflow on top of CommonJS
Date: Wed, 25 Feb 2015 16:24:48 +1000	[thread overview]
Message-ID: <CALATSMZ9f+nFx7GO1fi2mWjSStrufgtnPJbyXz-8enL7uGLOag@mail.gmail.com> (raw)
In-Reply-To: <CAPOA5_4i3rkcy0L35EhdjD7pHuiRaHzBFFvw-t+hEYJxVheeYQ@mail.gmail.com>

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

On Wed, Feb 25, 2015 at 3:58 PM, Jordan W <jordojw@gmail.com> wrote:

> The overarching goal was to just explore the ideal developer
> flow for people who are either used to CommonJS or who appreciate a
> highly sandboxed development model without globals.


This is something I'm keen to see as well - extend the opam switch concept
to per project. Forcing a switch during build is just a poor imitation of
that.


I don't know enough about the OCaml build toolchain to solve this in a
> scalable way so I made it work generally enough for a couple of the
> projects that I'm prototyping. I hope the same can be achieved in some
> other more sophisticated build tool. Has anyone seen anything like the
> automatic namespacing I've prototyped here? I couldn't imagine
> developing without it, personally.


+1

I'll end up developing something custom (or templates like we use in JS) if
need be to suit our development style - which sounds similar to yours - a
bunch of small internal library projects all composed in a tree of
dependencies, culminating in a single high level integration / package
project for the application.

Cheers,
Andy

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

      reply	other threads:[~2015-02-25  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24 20:26 Jordan W
2015-02-25  3:12 ` Andrew Herron
2015-02-25  5:58   ` Jordan W
2015-02-25  6:24     ` Andrew Herron [this message]

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=CALATSMZ9f+nFx7GO1fi2mWjSStrufgtnPJbyXz-8enL7uGLOag@mail.gmail.com \
    --to=thespyder@programmer.net \
    --cc=caml-list@inria.fr \
    --cc=jordojw@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).