X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com Subject: Re: AW: Missing functions in DJGPP libc (and/or) libm To: djgpp-workers AT delorie DOT com References: <4aed4e35-34a2-56ba-582a-c9c6ccae6699 AT iki DOT fi> <00b501d611a6$03f80ec0$0be82c40$@gmx.de> From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp-workers AT delorie DOT com]" Message-ID: Date: Sat, 18 Apr 2020 18:48:30 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <00b501d611a6$03f80ec0$0be82c40$@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US-large 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 On 4/13/20 6:12 PM, (buers AT gmx DOT de) [via djgpp-workers AT delorie DOT com] wrote: > Hello, > > maybe I lost some context. I seem to remember, that I had written functions > like sinl, cosl, tanl, copysignl almost 2 decades ago and contributed them > to the DJGPP project? For one implementation see thread beginning with http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-workers/2004/12/31/07:43:33 Following mail contains link to at least partial implementation http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-workers/2004/12/31/13:49:44 I guess we have all time followed wrong approach to try to get all completely perfect before trying to commit something to CVS. The result usually was endless discussions about it and at end life went on, work already done was forgotten buried in mailing list archives and maybe sometimes even lost (original URL to proposed additions broken, so lost unless somebody accidentally still have copy somewhere on HDD) and nothing was committed to CVS. Fortunately above mentioned implementation will not get lost as it is already on delorie.com. This approach could be OK if we would have number of developers like such projects as GCC. We do not have resources for it. One need to get stuff in CVS to have something to work on and fix possible problems after that. I'm afraid that otherwise the history will repeat: some discussion (perhaps shorter than 10 or more years ago) and after that really nothing achieved. I guess it maybe time to realize shortness of our resources and if nothing changes on our side deprecate DJGPP port of GCC in version 11 with possible later removal in version 12. It is not my decision though. Andris