Re: [MacPerl] Newbie question

[Chris Nandor <pudge@pobox.com>]

At 13:59 -0500 2000.09.29, <CoDeReBeL@hotmail.com> wrote:
>Overwhelmed with curiosity, I decided to find out what the deal was. If any
>process *except* MacPerl has a file open for writing, then
>
>open (WHATEVER, '+<theFileName')
>
>returns false. If, however, the process that has the file open for writing
>is MacPerl itself, it returns true. I used MPW in the test. Presumably,
>standalone applications and droplets count as separate processes.

Well, a droplet is just a mini-program that calls MacPerl, so if a droplet
is processing the file, it is MacPerl.

Anyway, yes, this is how mandatory file locking works in Mac OS (not Mac OS
X, though).  It will only let one process edit a file.  But there are ways
around this, so it is not entirely reliable.

-- 
Chris Nandor                      pudge@pobox.com    http://pudge.net/
Open Source Development Network    pudge@osdn.com     http://osdn.com/

# ===== Want to unsubscribe from this list?
# ===== Send mail with body "unsubscribe" to macperl-request@macperl.org