caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin Jambon <martin.jambon@ens-lyon.org>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Generic printer patch
Date: Thu, 08 Dec 2011 10:20:14 -0800	[thread overview]
Message-ID: <4EE0FFDE.1050107@ens-lyon.org> (raw)
In-Reply-To: <4EE0A6C6.8040703@lri.fr>

On 12/08/2011 04:00 AM, Romain Bardou wrote:
>>> 2) Could you imagine to generalize it to Format.formatter or to
>>> out_channel (without creating a string and concatenating)? Romain Bardou
>>> add in the mantis tracker (I can't give you the bugtracking number since
>>> mantis "is currently offline for maintenance") a feature wish for a new
>>> conversion specification that can print anything. Do you think you can
>>> fulfill is dream?
> 
> Here is the feature request I proposed:
> 
> http://caml.inria.fr/mantis/view.php?id=4956
> 
> Here is the response by Pierre Weis:
> 
> "This is a major feature wish that requires careful thinking and a lot
> of work!
> 
> Furthermore, we would not have a completely satisfactory solution in the
> end (due to this <poly> catch all case that tend to propagate, as far as
> you use polymorphic functions). The correct solution to get this feature
> in its full glory is a major modification of the type system along the
> lines of G'Caml.

The feature we want is exactly Jeremie's "hack" (his words). We need
this feature for debugging and displaying data in log files. This kind
of data is almost never polymorphic, so there is no practical issue
here. Also we don't need a standardized output format. However we would
often like to truncate the data to a reasonable size.

I understand that this feature could be replaced in the future by a more
complete solution, but we would be happy if it were provided as an
"experimental extension" of OCaml.


Martin

> In short, a natural feature wish in a strongly typed polymorphic
> language; we had it in mind for decades; unfortunately, we are not yet
> ready to offer it, even in the rather limited extent you proposed."
> 
> In other words: what you did is awesome but I'm not sure that it will be
> added in the trunk :(
> 
> Cheers,
> 


  parent reply	other threads:[~2011-12-08 18:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07 15:28 Jérémie Dimino
2011-12-07 16:46 ` Alex Rubinsteyn
2011-12-07 17:10   ` Jérémie Dimino
2011-12-07 16:56 ` François Bobot
2011-12-07 17:34   ` Jérémie Dimino
2011-12-08 12:00     ` Romain Bardou
2011-12-08 14:21       ` Gerd Stolpmann
2011-12-08 18:20       ` Martin Jambon [this message]
2011-12-08 21:39         ` Gabriel Scherer
2011-12-09  7:22           ` Jérémie Dimino
2011-12-09  9:26             ` Gabriel Scherer
2011-12-09  7:15         ` Jérémie Dimino
2011-12-08  2:33 ` Edgar Friendly
2011-12-08  7:28   ` François Bobot
2011-12-08  9:00   ` Alain Frisch
2011-12-08  9:24     ` Gerd Stolpmann
2011-12-08 10:32       ` Alain Frisch
2011-12-08 10:41         ` Jonathan Protzenko
2011-12-08 12:00           ` Philippe Veber
2011-12-08  5:26 ` Martin Jambon
2011-12-08  6:52   ` Jérémie Dimino
2011-12-08  7:44     ` Martin Jambon
2011-12-08  9:37       ` Jérémie Dimino

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=4EE0FFDE.1050107@ens-lyon.org \
    --to=martin.jambon@ens-lyon.org \
    --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).