caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: YANG Shouxun <yangsx@fltrp.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] unix.chop_extension
Date: Thu, 27 May 2004 16:15:17 +0800	[thread overview]
Message-ID: <200405271615.18042.yangsx@fltrp.com> (raw)
In-Reply-To: <40B307F7.6060405@baretta.com>

On Tuesday 25 May 2004 16:46, Alex Baretta wrote:
> skaller wrote:
> > # Filename.chop_extension "x.y/z";;
> > - : string = "x"
>
> This is a terrible consequence of not having (* functional *) support
> for regexps in the language or standard library. The Filename library
> uses the very weak functions of the String library to find the rightmost
> dot in the filename (* or path *), which is obviously correct only under
> a very stringent precondition, which is not the most general possible
> precondition for this function.

It seems to me that regexp is not necessary to fix this specific problem. 
Hopefully the following patch will get rid of it.

--8<--
--- filename.ml~        2003-12-17 20:23:26.000000000 +0800
+++ filename.ml 2004-05-27 16:11:08.000000000 +0800
@@ -207,10 +207,11 @@
   if n < 0 then invalid_arg "Filename.chop_suffix" else String.sub name 0 n

 let chop_extension name =
-  try
-    String.sub name 0 (String.rindex name '.')
-  with Not_found ->
-    invalid_arg "Filename.chop_extension"
+  let bn = Filename.basename name in
+    try
+      String.sub bn 0 (String.rindex bn '.')
+    with Not_found ->
+      invalid_arg "Filename.chop_extension"

 external open_desc: string -> open_flag list -> int -> int = "sys_open"
 external close_desc: int -> unit = "sys_close"
--8<--

-------------------
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


  parent reply	other threads:[~2004-05-27  8:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 20:04 skaller
2004-05-24 22:01 ` skaller
2004-05-25  8:46 ` Alex Baretta
2004-05-25  9:35   ` skaller
2004-05-25  9:46     ` Alain Frisch
2004-05-25 10:47       ` skaller
2004-05-25 11:51         ` sejourne kevin
2004-05-26 11:18           ` Florian Hars
2004-05-25 14:06         ` [Caml-list] Re: AAP (was: unix.chop_extension) Christophe TROESTLER
2004-05-25 13:37     ` [Caml-list] unix.chop_extension John Goerzen
2004-05-25 19:17     ` Richard Jones
2004-05-27  8:15   ` YANG Shouxun [this message]
2004-05-27  9:47     ` skaller
2004-05-26  9:05 ` Xavier Leroy
2004-05-26  9:35   ` Luca Pascali
2004-05-26  9:56   ` Remi Vanicat
2004-05-26 10:34   ` skaller
2004-05-26 13:27     ` Damien Doligez
2004-05-26 15:50       ` skaller
2004-05-26 16:04         ` Damien Doligez
2004-05-27  4:33           ` skaller
2004-05-27  4:56             ` John Goerzen
2004-05-28 16:44             ` Damien Doligez
2004-05-28 19:34               ` skaller
2004-05-29  8:37                 ` Damien Doligez
2004-05-29 10:01                   ` skaller
2004-05-29 16:02                     ` David Brown
2004-05-26 11:21   ` Alex Baretta
2004-05-26 16:43     ` Richard Jones
2004-05-27  4:48       ` skaller
2004-05-27  7:46         ` Markus Mottl
2004-05-27  9:33           ` skaller
2004-05-27 17:29       ` brogoff
2004-05-28 12:00         ` Keith Wansbrough
2004-05-28 16:43           ` brogoff
2004-05-28 17:49             ` Marcin 'Qrczak' Kowalczyk
2004-05-28 11:23       ` Alex Baretta

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=200405271615.18042.yangsx@fltrp.com \
    --to=yangsx@fltrp.com \
    --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).