On Thu, Jan 24, 2013 at 9:56 AM, Anil Madhavapeddy <span dir="ltr"><<a href="mailto:anil@recoil.org" target="_blank">anil@recoil.org</a>></span> wrote:<div><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
first of several working groups ... wg-parallel (multicore/distributed programming)</blockquote><div><br></div><div>This is great! I'm personally interested in the wg-parallel one.</div><div><br></div><div><br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Firstly, is there agreement on this approach, and secondly, what's the best way to reflect this on <a href="http://ocaml.org" target="_blank">ocaml.org</a>?<br></blockquote><div><br></div><div>Do you mean to publicize the groups? We've had some discussion [1] about a User Groups page, which could be generalized to groups of all sorts, perhaps split into different sections. Working groups could all be listed here with a description and links to their mailing lists, etc. Actually, this resolves the problem we were having that currently there are not enough groups to justify a whole separate page.</div>
<div><br></div><div>[1] <a href="https://github.com/ocaml/ocaml.org/issues/97">https://github.com/ocaml/ocaml.org/issues/97</a></div><div><br></div><div>-Ashish</div><div><br></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Begin forwarded message:<br>
<br>
> From: Alain Frisch <<a href="mailto:alain@frisch.fr">alain@frisch.fr</a>><br>
> Subject: [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4<br>
> Date: 24 January 2013 14:31:01 GMT<br>
> To: caml-list <<a href="mailto:caml-list@inria.fr">caml-list@inria.fr</a>><br>
> Cc: <a href="mailto:wg-camlp4@lists.ocaml.org">wg-camlp4@lists.ocaml.org</a>, Leo P White <<a href="mailto:lpw25@cam.ac.uk">lpw25@cam.ac.uk</a>>, Anil Madhavapeddy <<a href="mailto:avsm2@cl.cam.ac.uk">avsm2@cl.cam.ac.uk</a>><br>
<div><div class="h5">><br>
> Dear caml-list,<br>
><br>
> There is a growing opinion that camlp4 is overly complex considering the benefits it brings to OCaml developers. I would personally go as far as to say that the future of OCaml and the OCaml community would be brighter if camlp4 could be removed from our "basic ecosystem". In particular, most of the current uses of camlp4 to create syntax extensions could probably be replaced by the new "-ppx" technology (see below) and small extensions to the compilers.<br>
><br>
> A lot needs to happens for this camlp4-free OCaml ecosystem to become a reality and we have to come up with a solid transition plan. A new community-driven working group, chaired by Leo White and me, is being set up today to elaborate this plan. If this topic is of interest to you, please join our mailing list:<br>
><br>
> <a href="http://lists.ocaml.org/listinfo/wg-camlp4" target="_blank">http://lists.ocaml.org/listinfo/wg-camlp4</a><br>
><br>
><br>
> Some of the most important tasks for our new working group will be:<br>
><br>
> - Gather information from the community about the use of camlp4.<br>
> (Please consider sharing information about your use of camlp4<br>
> and camlp4-based extensions, even if you don't plan to participate<br>
> to the working group discussions!)<br>
><br>
> - Finalize support for -ppx and make technical proposals for<br>
> extensions of the OCaml compilers in order to enable a transition of<br>
> camlp4-based extensions to -ppx (in particular, we need to come up<br>
> with a concrete syntax for generic extension points in the grammar).<br>
><br>
> - Write some "canonical" examples of extensions based on -ppx and<br>
> provide information and support to developers of extensions for<br>
> switching from camlp4 to -ppx.<br>
><br>
> - Discuss integration of -ppx with existing tools (findlib, build<br>
> systems, etc).<br>
><br>
> - Find a solution in the community for the future of camlp4<br>
> (in particular, discuss how / how long / by who it will be<br>
> maintained).<br>
><br>
> - Discuss longer-terms plans beyond -ppx, including extra language<br>
> support, to facilitate light syntactic meta-programming for OCaml<br>
> (Leo has some clever ideas!).<br>
><br>
><br>
><br>
> The discussion on the mailing list will start in a few days, to give some time for interested people to join. In the meanwhile, Leo has written a blog post to get the discussion started:<br>
><br>
> <a href="http://www.lpw25.net/2013/01/23/camlp4-alternative-part-1.html" target="_blank">http://www.lpw25.net/2013/01/23/camlp4-alternative-part-1.html</a><br>
><br>
> You can also read about -ppx:<br>
><br>
> <a href="http://www.lexifi.com/blog/syntax-extensions-without-camlp4" target="_blank">http://www.lexifi.com/blog/syntax-extensions-without-camlp4</a><br>
> <a href="http://www.lexifi.com/blog/syntax-extensions-without-camlp4-lets-do-it" target="_blank">http://www.lexifi.com/blog/syntax-extensions-without-camlp4-lets-do-it</a><br>
><br>
> Some projects have already started to replace camlp4 by -ppx:<br>
><br>
> bisect (supports both camlp4 and ppx since version 1.3)<br>
> sedlex (unicode-friendly lexer generator, successor of ulex)<br>
> omonad (syntax for monadic code, similar to pa_monad)<br>
><br>
><br>
> Many thanks to Anil Madhavapeddy and to OCamlLabs for setting up the working group and its mailing list!<br>
><br>
><br>
> Alain<br>
><br>
> --<br>
> Caml-list mailing list. Subscription management and archives:<br>
> <a href="https://sympa.inria.fr/sympa/arc/caml-list" target="_blank">https://sympa.inria.fr/sympa/arc/caml-list</a><br>
> Beginner's list: <a href="http://groups.yahoo.com/group/ocaml_beginners" target="_blank">http://groups.yahoo.com/group/ocaml_beginners</a><br>
> Bug reports: <a href="http://caml.inria.fr/bin/caml-bugs" target="_blank">http://caml.inria.fr/bin/caml-bugs</a><br>
><br>
<br>
</div></div>_______________________________________________<br>
Infrastructure mailing list<br>
<a href="mailto:Infrastructure@lists.ocaml.org">Infrastructure@lists.ocaml.org</a><br>
<a href="http://lists.ocaml.org/listinfo/infrastructure" target="_blank">http://lists.ocaml.org/listinfo/infrastructure</a><br>
</blockquote></div><br></div>