Date: Sat, 18 Nov 2000 13:20:11 -0500
Message-Id: <200011181820.NAA03922@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: djgpp-workers AT delorie DOT com
In-reply-to: <9743-Sat18Nov2000101225+0200-eliz@is.elta.co.il>
Subject: Re: snprintf() diff
References: <200011132023 DOT PAA04930 AT qnx DOT com> <3A1328A7 DOT C9866232 AT bigfoot DOT com> <200011160105 DOT UAA01282 AT envy DOT delorie DOT com> <3A15C4B1 DOT 383439DB AT bigfoot DOT com> <200011180030 DOT TAA26797 AT envy DOT delorie DOT com> <9743-Sat18Nov2000101225+0200-eliz AT is DOT elta DOT co DOT il>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Not if we want to keep the existing behavior of putc, which only
> returns EOF when the whole call should fail.

If you're trying to call putc on a string and there's no space left in
the string, yes, the putc call should fail.  You are out of space.

> Perhaps there's some misunderstanding here, because I didn't
> understand why did you suggest to put this snippet into _flsbuf, and
> why did you say ``so that it acts like a "disk full" condition when
> the string buffer is empty''.  Could you please describe the situation
> which you had in mind?

I'm saying that we can treat "disk file, no space on disk" the same
way as "string buffer, no space in string".  We don't need a special
case for it, except at the lowest level - flsbuf.