From: Francois Berenger <francois.berenger@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: exn-source - exception backtraces with source code printing
Date: Mon, 20 Oct 2014 14:15:21 +0200 [thread overview]
Message-ID: <5444FCD9.2090704@inria.fr> (raw)
In-Reply-To: <98bddccae44b9764b252efd7ad3614c5@whitequark.org>
On 10/20/2014 02:06 PM, Peter Zotov wrote:
> On 2014-10-20 15:52, John Whitington wrote:
>> Noted. I'd like to add functionality like this. The first thing I'm
>> going to add is automatic finding of the stdlib, since this just
>> requires parsing the output of "ocamlc -config".
>
> I would take this directly from OCaml configuration (module Config,
> -package compiler-libs.common). No shelling out needed.
>
>> Unfortunately, I don't believe most OPAM packages install their
>> source, just the .mli files. I wonder how much extra space installing
>> source would take on average, and if people think it's worth it, for
>> this or other reasons.
>
> I think it's mainly due to lack of infrastructure that could install
> sources (eg OASIS couldn't easily be coerced into doing that). You could
> probably make opam do the grunt work for you; no need to have the sources
> installed in the same places as mli or binaries!
Isn't opam -b or --keep-build-dir supposed to keep the sources?
--
Regards,
Francois.
next prev parent reply other threads:[~2014-10-20 12:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 18:03 John Whitington
2014-10-19 18:26 ` Gabriel Scherer
2014-10-19 18:55 ` John Whitington
2014-10-19 19:05 ` Gabriel Scherer
[not found] ` <54441347.904@coherentgraphics.co.uk>
2014-10-19 19:50 ` Gabriel Scherer
2014-10-20 9:15 ` Nicolas Boulay
2014-10-20 9:35 ` Peter Zotov
2014-10-20 11:52 ` John Whitington
2014-10-20 12:06 ` Peter Zotov
2014-10-20 12:15 ` Francois Berenger [this message]
2014-10-20 18:28 ` Török Edwin
2014-10-23 8:32 ` John Whitington
2014-10-23 11:48 ` Sébastien Hinderer
2014-10-23 16:43 ` Gabriel Scherer
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=5444FCD9.2090704@inria.fr \
--to=francois.berenger@inria.fr \
--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