From: "BdB" <benoit.de-boursetty+caml-list@m4x.org>
To: <matthieu.dubuget@libertysurf.fr>, "caml-list" <caml-list@inria.fr>
Subject: RE: [Caml-list] Re: [Caml-list] Question/Feature request about Camlidl andcomments]
Date: Wed, 30 Jul 2003 09:53:40 +0200 [thread overview]
Message-ID: <JHELJHNLBEFIOPJEFEEKKEEPCAAA.benoit.de-boursetty+caml-list@m4x.org> (raw)
In-Reply-To: <HITRYU$76CE8827F52A1FA020A35343B7932268@tiscali.fr>
Not solving your problem here, but wouldn't it be more consistent to use a
literate programming tool for IDL? After all, your IDL component may or may
not be implemented in O'CaML...
> -----Message d'origine-----
> De : owner-caml-list@pauillac.inria.fr
> [mailto:owner-caml-list@pauillac.inria.fr]De la part de
> matthieu.dubuget@libertysurf.fr
> Envoyé : mercredi 30 juillet 2003 08:43
> À : caml-list
> Objet : [Caml-list] Re: [Caml-list] Question/Feature request about
> Camlidl andcomments]
>
>
> >Depending on what you base your ocamldoc generation,
> >use either ml or mli. Since i think mli is the best
> >place to do it i will use it :
>
> >quote(mli,"(** This is a ocamldoc comment *)");
>
> >int my_function ( [string] const char * msg );
>
> >Simple !
>
> I should have explained in detail what I was trying to do.
>
> I did an attempt to do what you are suggesting. The problem
> is that it seems difficult to control where the comments
> will appear in the generated mli files.
>
> For example, if I try
> quote(mli,"** This is a module *)"); at the very beginning
> of my idl file in order to generate a comment to be
> associated with the whole module, the string appears between
> types definitions and functions definitions, which is not
> what we need to conform to ocamldoc. An other point was that
> I wanted to comment also the elements of enums.
>
> I may have the time to look at camlidl source code during my
> holidays...
>
> Salutations
>
> Matthieu Dubuget
>
>
>
>
>
> ********** L'ADSL A 20 EUR/MOIS**********
> Tiscali propose l'ADSL le moins cher du marché : 20 EUR/mois et
> le modem ADSL offert !
> Pour profiter de cette offre exceptionnelle, cliquez ici :
http://register.tiscali.fr/adsl/
Offre soumise à conditions.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives:
http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ:
http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2003-07-30 7:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 6:42 matthieu.dubuget
2003-07-30 7:53 ` BdB [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=JHELJHNLBEFIOPJEFEEKKEEPCAAA.benoit.de-boursetty+caml-list@m4x.org \
--to=benoit.de-boursetty+caml-list@m4x.org \
--cc=caml-list@inria.fr \
--cc=matthieu.dubuget@libertysurf.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).