Mail Archives: djgpp-workers/1998/03/23/09:20:36
Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be> wrote:
> Eli Zaretskii wrote:
> >
> > On Thu, 19 Mar 1998, Vik Heyndrickx wrote:
> >
> > > writing
> > > open it for writing and specify DENYALL
> > > r/w
> > > open it for r/w and specify DENYALL
> >
> > Doesn't this prevent other programs from opening the file in read-only
> > mode?
>
> During the weekend, I reconsidered this already and my new opinion is:
>
> writing
> open it for writing and specify DENYWRITE
> r/w
> open it for r/w and specify DENYWRITE
>
> Like you mentioned, the previous restrictions were too strickt, as a
> second prg CAN control not to open a file for reading when it is already
> written to. Specifying DENYNONE on the other hand, will put data too
> much at stake.
> But: when a file is written to, it is better not to be able to open it
> for reading, as this also can compromise data.
My editor is working currently with the patch I sent to the group and setting
DENYWRITE as default, that's what I consider the better choice, so I agree with
Vik, but the same again: It can break old programs.
SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
CQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013
- Raw text -