On 6/5/2013 12:15, Corinna Vinschen wrote:
Actually, adding this stuff to Cygwin took almost four days of my
life as it is today.
Understood. Likewise, because I am not full-time on Cygwin SQLite, it's
taken similar amounts of time from me, which is why I'm ignoring your
xidepend complaints
On Jun 5 11:18, Warren Young wrote:
> On 6/5/2013 11:02, Corinna Vinschen wrote:
> >The burden to use it correctly is
> >on the application developer.
>
> That's always true, for all APIs.
>
> If a design change can make it more likely that application
> developers will use it correctly, shouldn
On 6/5/2013 11:02, Corinna Vinschen wrote:
The burden to use it correctly is
on the application developer.
That's always true, for all APIs.
If a design change can make it more likely that application developers
will use it correctly, shouldn't the design be changed?
It's not like anyone is
On Jun 5 10:15, Warren Young wrote:
> On 6/4/2013 02:48, Corinna Vinschen wrote:
> >On Jun 3 11:36, Warren Young wrote:
> >>Could you add an O_MAND open(2) option as well to turn on the same
> >>feature? This will avoid a race condition.
> >
> >If you call F_LCK_MANDATORY right after open in the
On 6/4/2013 02:48, Corinna Vinschen wrote:
On Jun 3 11:36, Warren Young wrote:
Could you add an O_MAND open(2) option as well to turn on the same
feature? This will avoid a race condition.
If you call F_LCK_MANDATORY right after open in the opening routine,
there won't be (much of) a race.
5 matches
Mail list logo
