[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] an example of broken lib

To: kellis <kellis@leading.net>
Subject: Re: [MiNT] an example of broken lib
From: Michael Schwingen <rincewind@discworld.dascon.de>
Date: Thu, 24 Jun 1999 12:42:20 +0200
Cc: MiNT mailing list <mint@fishpool.com>
In-reply-to: <Pine.MNT.4.10.9906222013280.116-100000@tampa1-052.southeast.net>; from kellis on Tue, Jun 22, 1999 at 08:16:40PM +0000
References: <Pine.LNX.3.96.990617091159.18440H-100000@hal.fishpool.fi> <Pine.MNT.4.10.9906222013280.116-100000@tampa1-052.southeast.net>
Sender: owner-mint@fishpool.com

On Tue, Jun 22, 1999 at 08:16:40PM +0000, kellis wrote:
> bug report or wishes for mintlib.
> 
> Have EAGAIN included (EWOULDBLOCK?)
> 
> snprintf, and vsnprintf added to the lib.

Soubnds reasonable.

> Have fchmod added to the lib, even if simply faked with chmod.

Um - no. Either add a working fchmod to the lib, or none at all - otherwise,
programs using autoconf might draw wrong conclusions because fchmod is
present, but does not do what is intended.

cu
Michael
-- 
Michael Schwingen, Ahornstrasse 36, 52074 Aachen

References:
- [MiNT] an example of broken lib
  - From: Martin-Eric Racine <q-funk@pp.fishpool.com>
- Re: [MiNT] an example of broken lib
  - From: kellis <kellis@leading.net>

Prev by Date: [MiNT] kernel development
Next by Date: Re: [MiNT] Compiling the kernel
Previous by thread: Re: [MiNT] an example of broken lib
Next by thread: Re: [MiNT] an example of broken lib
Index(es):
- Date
- Thread