X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f From: Kbwms AT aol DOT com Message-ID: <6a.37c1c9aa.2cdff45c@aol.com> Date: Sun, 9 Nov 2003 14:49:48 EST Subject: Re: C99 Functions Under Development and Checkout To: djgpp-workers AT delorie DOT com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_6a.37c1c9aa.2cdff45c_boundary" X-Mailer: 8.0 for Windows sub 6021 Reply-To: djgpp-workers AT delorie DOT com --part1_6a.37c1c9aa.2cdff45c_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In a message dated 11/9/2003 2:17:08 PM Eastern Standard Time, rich AT phekda DOT freeserve DOT co DOT uk writes: > The caller can still try to set the global variable. Then the developer > will > wonder why it doesn't work. Hence comp.os.msdos.djgpp gets bombarded with > user > questions on this issue. > > Just because the C standard says the variable should not be modified after > program start doesn't mean that users won't try to. How many people try > fflush(stdin) to clear the waiting input and then wonder why it doesn't > work? > The standard clearly states: The value of math_errhandling is constant for the duration of the program. This means that it cannot be modified. It seems to me that you are second-guessing the developer. A knowledge of the standard is certainly called for in more respects than just this case. > Would it help if I sent a patch to implement math_errhandling the way I'm > thinking of? > No. Thanks for your comments. KB Williams --part1_6a.37c1c9aa.2cdff45c_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable In a message dated 11/9/2003 2:17:08 PM Eastern Standard= Time, rich AT phekda DOT freeserve DOT co DOT uk writes:

The caller can still try to set the global variable. Then t= he developer will
wonder why it doesn't work. Hence comp.os.msdos.djgpp gets bombarded with us= er
questions on this issue.

Just because the C standard says the variable should not be modified after program start doesn't mean that users won't try to. How many people try
fflush(stdin) to clear the waiting input and then wonder why it doesn't work= ?


The standard clearly states:
       The value of math_errhandling is consta= nt
        for the duration of the program.<= BR>
This means that it cannot be modified.

It seems to me that you are second-guessing the developer.  A knowledge= of the standard is certainly called for in more respects than just this cas= e.


Would it help if I sent a patch= to implement math_errhandling the way I'm
thinking of?


No.


Thanks for your comments.



KB Williams --part1_6a.37c1c9aa.2cdff45c_boundary--