From: Luca Pascali <pasckosky2000@yahoo.it>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: skaller <skaller@users.sourceforge.net>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] unix.chop_extension
Date: Wed, 26 May 2004 11:35:09 +0200 [thread overview]
Message-ID: <40B464CD.8070503@yahoo.it> (raw)
In-Reply-To: <20040526110508.A17806@pauillac.inria.fr>
Xavier Leroy wrote:
[CUT]
>>here's one extra thing I'd like to point out. We have the
>>chop_extension function. Why in the world is there no find_extension
>>function?
>>find_extension "foo.bar" --> "bar"
>>
>>
>
>Why in the world would that be generally useful? Remember, we don't
>shoot for completeness (it's unattainable anyway), just for
>usefulness.
>
>- Xavier Leroy
>
>
>
>
IMHO, this might be considered more as a matter of usefulness instead of
completeness.
I mean that there are systems (like Windows) that use only the extension
of the file to identify how to execute or how to read the file itself,
and anyway the extension is useful to classify a file for any kind of
application (such as compilers, network applications, graphic editing,
and so on).
So a developer has to write its own function to extract the extension
from a filename every time he/she needs. Its not a big deal, but ...
My opinion.
Luca
-------------------
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
next prev parent reply other threads:[~2004-05-26 9:34 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
2004-05-27 9:47 ` skaller
2004-05-26 9:05 ` Xavier Leroy
2004-05-26 9:35 ` Luca Pascali [this message]
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=40B464CD.8070503@yahoo.it \
--to=pasckosky2000@yahoo.it \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
--cc=xavier.leroy@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