From: Thomas Braibant <thomas.braibant@gmail.com>
To: OCaML Mailing List <caml-list@inria.fr>
Subject: [Caml-list] Prochain meetup OUPS 04 juin 2015 / Next OUPS meetup, 4th of June 2015
Date: Fri, 29 May 2015 16:28:51 +0200 [thread overview]
Message-ID: <CAHR=VkzjyO9Fkj2-MWWQKZqxRX_Z+TwQN1sjZOGDZKO+AbhzRg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
(English version below)
Bonjour,
Le prochain meetup OUPS aura lieu jeudi 4 juin 2015. Nous nous retrouverons
à 19h30 à l'IRILL selon la formule habituelle (exposés pendant ~1h30,
suivis d'une discussion autourd'un pot).
Le programme des exposés confirmés jusqu'ici:
- Alain Frisch. gen_js_api: génération de bindings vers Javascript pour
js_of_ocaml
- Pietro Abate. OpamWeather Service : utilisation et développent
- Gabriel Scherer. Quelques nouvelles sur la prochaine version d'OCaml
- Thomas Williams. Ornements pour le refactoring en OCaml.
Pour vous inscrire, ou pour plus d'informations rendez vous ici:
http://www.meetup.com/ocaml-paris/events/222500273/
Thomas, pour les organisateurs du meetup
-----------------------------------------------------------------------------------------
Hi,
The next OUPS meetup will take place on the 4th of June, at IRILL. We will
have a few talks, followed by pizzas.
The program of the talks is:
- Alain Frisch. gen_js_api: Generating Javascript bindings for js_of_ocaml
- Pietro Abate. OpamWeather Service : usage and development
- Gabriel Scherer. Some news about the next version of OCaml
- Thomas Williams. Ornaments for refactoring in OCaml
To register, or for more information, go here
http://www.meetup.com/ocaml-paris/events/222500273/
Thomas, for the organizers of the meetup
[-- Attachment #2: Type: text/html, Size: 1996 bytes --]
next reply other threads:[~2015-05-29 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 14:28 Thomas Braibant [this message]
2015-06-04 13:35 ` Drup
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='CAHR=VkzjyO9Fkj2-MWWQKZqxRX_Z+TwQN1sjZOGDZKO+AbhzRg@mail.gmail.com' \
--to=thomas.braibant@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).