From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Hendrik Boom <hendrik@topoi.pooq.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Filename.split_extension
Date: Mon, 25 Jul 2016 21:15:37 +0200 [thread overview]
Message-ID: <101DEC7D6F09405583881893AC3EC338@erratique.ch> (raw)
In-Reply-To: <20160725190346.GA8823@topoi.pooq.com>
Le lundi, 25 juillet 2016 à 21:03, Hendrik Boom a écrit :
> I see. There's a funcction to test for a particulat extension
> (check_suffix), and functions to chop the suffix off (chop_suffix if
> you know what it is and chop_extension if you don't) but none to return
> the extension.
The Filename module is a little bit underpowered you might be interested in this PR:
https://github.com/ocaml/ocaml/pull/669
which will be available in 4.04.
If you don't mind a dependency you could use
http://erratique.ch/software/fpath/doc/Fpath
Best,
Daniel
prev parent reply other threads:[~2016-07-25 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 18:35 Hendrik Boom
2016-07-25 18:43 ` Daniel Bünzli
2016-07-25 19:03 ` Hendrik Boom
2016-07-25 19:15 ` Daniel Bünzli [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=101DEC7D6F09405583881893AC3EC338@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=hendrik@topoi.pooq.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;
as well as URLs for NNTP newsgroup(s).