caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Goerzen <jgoerzen@complete.org>
To: skaller <skaller@users.sourceforge.net>
Cc: Damien Doligez <damien.doligez@inria.fr>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] unix.chop_extension
Date: Wed, 26 May 2004 23:56:40 -0500	[thread overview]
Message-ID: <20040527045640.GC23183@complete.org> (raw)
In-Reply-To: <1085632433.32106.93.camel@pelican.wigram>

On Thu, May 27, 2004 at 02:33:54PM +1000, skaller wrote:
> On Thu, 2004-05-27 at 02:04, Damien Doligez wrote:
> > On May 26, 2004, at 17:50, skaller wrote:
> > 
> > > This is mathematically an ill formed statement.
> > >
> > > You cannot say P(x), when x doesn't exist,
> > > for a predicate P. That could lead to a contradiction.
> > 
> > And yet... You can open a file that doesn't exist.
> 
> No you can't. You can call the open function
> with a string for any string. For some strings
> a file will be opened. For other strings
> no file is opened, you get an error.

Well.  You can have an open file that doesn't exist but you can't open a
file that doesn't exist.

If a file is unlinked after it's been opened, it is no longer accessible
from any name but its blocks are not reclaimed until after every process
that has it open has closed it.  Thus the open fd remains valid.

(these semantics may differ on non-POSIX platforms)

-- John

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


  reply	other threads:[~2004-05-27  4:55 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
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 [this message]
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=20040527045640.GC23183@complete.org \
    --to=jgoerzen@complete.org \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@inria.fr \
    --cc=skaller@users.sourceforge.net \
    /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).