caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
Cc: Gustave Nimant <gustave.nimant@free.fr>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] getting the name of a function from its body
Date: Tue, 02 Jun 2015 10:45:26 +0200	[thread overview]
Message-ID: <1433234726.11499.33.camel@e130.lan.sumadev.de> (raw)
In-Reply-To: <CAHvkLrOhmGKq9fDSjqDzsBTiNY_NGzCR1KYOwB3RMk=No0tozA@mail.gmail.com>

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

You can also put several functions on the same line... The argument does
not make much sense. It is eventually up to the developer of a module to
ensure that error messages are unique (enough).

I guess it is simply an implementation issue. The name of the current
function is not at hand where this kind of macros is expanded.

Gerd

Am Montag, den 01.06.2015, 23:57 +0200 schrieb Fabrice Le Fessant:
> The main reason for the absence of __FUNCTION__ is probably that it
> does not really make sense : you might have several functions with the
> same name within the same module :
> 
> let f x = x+1
> let f list = List.map f list
> 
> It makes sense in C, because you can only define a symbol once in a
> file, so the pair (__FILE__, __FUNCTION__) is uniq (and if the
> function is not static, it is probably even uniq within the
> executable).
> 
> In OCaml, it is probably better to use the pair (__FILE__, __LINE__)
> to tell the dev where to search for the problem.
> 
> --Fabrice
> 
> 
> 
> 
> 
> On Mon, Jun 1, 2015 at 6:36 PM, Gustave Nimant <gustave.nimant@free.fr> wrote:
> > On 01/06/2015 13:46, Fabrice Le Fessant wrote:
> >>
> >> Recent versions of OCaml provide "__LOC__", "__FILE__", "__LINE__",
> >> "__MODULE__" and "__POS__" primitives that can be used to display
> >> precise error messages.
> >>
> >> --Fabrice
> >
> > Thank you for this information I was not aware of.
> > It seems that the functions described in
> > http://caml.inria.fr/pub/docs/manual-ocaml/libref/Pervasives.html
> > do not answer my question :
> > "how to get the name of the current function ?"
> >
> > Do I miss something ?
> >
> >
> > Gustave
> >
> > --
> > Caml-list mailing list.  Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
> 
> 
> 
> -- 
> Fabrice LE FESSANT
> Chercheur en Informatique
> INRIA Paris Rocquencourt -- OCamlPro
> Programming Languages and Distributed Systems
> 

-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
My OCaml site:          http://www.camlcity.org
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-06-02  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01 11:42 Gustave Nimant
2015-06-01 11:46 ` Fabrice Le Fessant
2015-06-01 11:52   ` Gabriel Scherer
2015-06-01 16:36   ` Gustave Nimant
2015-06-01 16:46     ` Francois Berenger
2015-06-01 17:38       ` Gustave Nimant
2015-06-01 18:07         ` Yotam Barnoy
2015-06-01 21:57     ` Fabrice Le Fessant
2015-06-02  8:10       ` Francois Berenger
2015-06-02  8:21         ` Jacques Garrigue
2015-06-02  8:37           ` Romain Bardou
2015-06-04 18:48         ` Damien Doligez
2015-06-02  8:45       ` Gerd Stolpmann [this message]
2015-06-01 14:57 ` [Caml-list] Getting the list of available function within a module Nicolas Ratier

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=1433234726.11499.33.camel@e130.lan.sumadev.de \
    --to=info@gerd-stolpmann.de \
    --cc=Fabrice.Le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=gustave.nimant@free.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).