caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vincent Gripon <vincent.gripon@telecom-bretagne.eu>
To: Grant Rettke <grettke@acm.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: WAS Re: [Caml-list] Compiling Ocaml sources to c sources
Date: Wed, 15 Sep 2010 15:11:56 +0200	[thread overview]
Message-ID: <4C90C61C.3090707@telecom-bretagne.eu> (raw)
In-Reply-To: <AANLkTimMzxvi9ErM-+4+rgAPCbv9TMnQn5rywcoTNnHb@mail.gmail.com>

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

  Hello Grant,

This would likely be accepted by the contest, but it would force me to 
boot on my windows partition (which I prefer not to!). As Basile 
proposed another working suggestion, we will avoid the use of .Net.

The contest is IEEEXtreme programming competition ( 
http://www.ieee.org/membership_services/membership/students/competitions/xtreme/index.html 
).

Cheers.

On 09/14/2010 02:36 PM, Grant Rettke wrote:
>  From what I've heard on-list, OCaml and F# are pretty similar; to the
> point where F# can compile OCaml.
>
> You *could* write it in OCaml, compile it under F#, and call the
> library from a C# program that only has as 'main' function.
>
> What contest are you entering?
>
> On Tue, Sep 14, 2010 at 7:09 AM, Vincent Gripon
> <vincent.gripon@telecom-bretagne.eu>  wrote:
>> Hello,
>>
>> We are currently planing to participate to a programming contest. This
>> contest allows the use of four languages (C/C#/C++/java) but not OCaml.
>>
>> We would like to use Ocaml as it is to us the language that fits the most
>> the kind of exercises proposed. The organizers don't mind if we use OCaml as
>> long as we provide an easily compilable C source to them, even if it is not
>> readable.
>>
>> Is there any platform independent way to compile OCaml sources to C
>> sources?  And if not, do you have any pointer (we gave a try at compiling
>> OCaml sources to C object files using the -output-obj option but couldn't
>> compile then the resulting file with our C compiler)?
>>
>> Best,
>>
>> Vincent
>>
>> _______________________________________________
>> Caml-list mailing list. Subscription management:
>> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
>> Archives: http://caml.inria.fr
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>>
>>
>
>

[-- Attachment #2: vincent_gripon.vcf --]
[-- Type: text/x-vcard, Size: 354 bytes --]

begin:vcard
fn:Vincent Gripon
n:Gripon;Vincent
org:Telecom Bretagne;Computer Science and Telecommunications
adr:;;Telecom Bretagne - Technopole Brest Iroise;Brest Cedex 3;;29238;France
email;internet:vincent.gripon@ens-cachan.org
title:PhD Student
tel;work:+0033 2 29 00 1586
url:http://perso.eleves.bretagne.ens-cachan.fr/~gripon
version:2.1
end:vcard


       reply	other threads:[~2010-09-15 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimMzxvi9ErM-+4+rgAPCbv9TMnQn5rywcoTNnHb@mail.gmail.com>
2010-09-15 13:11 ` Vincent Gripon [this message]
2010-09-15 15:22   ` Grant Rettke

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=4C90C61C.3090707@telecom-bretagne.eu \
    --to=vincent.gripon@telecom-bretagne.eu \
    --cc=caml-list@yquem.inria.fr \
    --cc=grettke@acm.org \
    /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).