From: Christian Gillot <cgillot@gruposbd.com>
To: Chris Hecker <checker@d6.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: about toplevels
Date: 23 Jan 2002 10:35:34 +0100 [thread overview]
Message-ID: <1011778534.638.11.camel@node89> (raw)
In-Reply-To: <4.3.2.7.2.20020123011902.00cde840@arda.pair.com>
El dc, 23-01-2002 a las 10:19, Chris Hecker escribió:
>
> >Sorry surely I didn't looked the right way but anyway Google was
> >responseless.
>
> Try groups.google.com and search on "caml toplevel include directories" and the post comes right to the top.
> There's also an archive on caml.inria.fr.
I don't even try to justificate me, I'm definitely wrong. But at the
time I was rather upset by the fact that a toplevel was compiled with
a module and just after you couldn't open it !
My search was rather "caml toplevel Unbound module" because I didn't
even know at the that I had "include directories". Sorry I'm just a
newbie.And the autor of pcre answered to this concern in about 10 minuts
(hat down to him), I wrote him after struggling one hour against
ocamlmktop ;o)
Ocaml deserve to be used by far more people, it's a really interesting
language. But you will agree with me that it's difficult to apprehend.
It's done by researchers, lack some documentation (especially in English
I can't complain the book on Ocaml in French is on the web). Basically
the first step is the harder.
So far I had three problems :
1. the toplevel one
2. two records can't have the same label
type a = {blabla: int}
type b = {blabla: int, comment: string)
3. the exceptions are NOT polymorphics
exception of 'a list is WRONG.
I think I'm gonna do a gotcha page, but don't you think such
a page deserve his place on caml.inria.fr ?
Best regards,
--
Christian Gillot <cgillot@gruposbd.com>
GNU/Linux programmer
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-01-24 15:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 23:27 cgillot
2002-01-21 22:43 ` [Caml-list] Re: your mail Markus Mottl
2002-01-22 0:03 ` [Caml-list] Re: about toplevels cgillot
2002-01-22 20:41 ` Chris Hecker
2002-01-22 21:35 ` [Caml-list] Ocaml and games Matthew D Moss
2002-01-22 21:43 ` Will Benton
2002-01-22 23:53 ` Eric C. Cooper
2002-01-23 0:58 ` Ian Zimmerman
2002-01-23 1:23 ` Yaron M. Minsky
2002-01-23 3:29 ` Doug Bagley
2002-01-23 5:20 ` Chris Hecker
2002-01-24 3:02 ` Matthew D Moss
2002-01-24 6:59 ` Chris Hecker
2002-01-25 20:22 ` Daniel Phillips
2002-01-25 20:53 ` Ken Rose
2002-01-25 22:16 ` Chris Hecker
2002-01-25 23:00 ` Thatcher Ulrich
2002-01-23 8:39 ` Sven
2002-01-23 15:35 ` Xavier Leroy
2002-01-22 9:00 ` [Caml-list] Re: your mail Daniel de Rauglaudre
2002-01-22 13:12 ` Markus Mottl
[not found] ` <4.3.2.7.2.20020123011902.00cde840@arda.pair.com>
2002-01-23 9:35 ` Christian Gillot [this message]
2002-01-23 10:20 ` [Caml-list] Re: about toplevels Chris Hecker
2002-01-24 16:03 ` Daniel de Rauglaudre
2002-01-24 17:20 ` Christophe Raffalli
2002-01-24 17:34 ` Christian Gillot
2002-01-24 20:42 ` [Caml-list] gotchas [Was: toplevels] Ian Zimmerman
2002-01-25 10:59 ` Christian Gillot
2002-01-25 11:17 ` Sven
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=1011778534.638.11.camel@node89 \
--to=cgillot@gruposbd.com \
--cc=caml-list@inria.fr \
--cc=checker@d6.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