From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Derbyshire To: egcs@egcs.cygnus.com Subject: Re: Bug in libm or libstdc++. Date: Thu, 25 Feb 1999 22:25:00 -0000 Message-id: <3.0.6.32.19990226012513.008e5450@pop.globalserve.net> In-reply-to: < 199902242332.PAA09334@atrus.synopsys.com > References: <3.0.6.32.19990222090333.00847df0@pop.globalserve.net> <199902242332.PAA09334@atrus.synopsys.com> X-SW-Source: 1999-02/msg01307.html At 03:32 PM 2/24/99 PST, you wrote: >You have already been informed that libstdc++ is not complete. Sorry. The standard has been around in largely complete form for over a year, and finalized for many months. I am curious as to what is the cause for all of these omissions... I would love to help but I don't know the first thing about implementing these mathematical functions. In any case, to avoid any more unpleasant surprised I would like to see a list of all the omissions in the current libstdc++ and other non-conformances, and where possible ETAs for the missing components. It would be a good idea to post a periodic libstdc++ progress report and calls for volunteers to implement some of the stuff. I think that might attract more developers to fixing up and finishing implementing the standard C++ library. An area where I may be able to help is with the standard valarray and its friends, once I get back a response regarding making the compiler eliminate temporaries and excess copies in argument passing and return. -- .*. "Clouds are not spheres, mountains are not cones, coastlines are not -() < circles, and bark is not smooth, nor does lightning travel in a `*' straight line." ------------------------------------------------- -- B. Mandelbrot | http://surf.to/pgd.net _____________________ ____|________ Paul Derbyshire pderbysh@usa.net Programmer & Humanist|ICQ: 10423848| From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Derbyshire To: egcs@egcs.cygnus.com Subject: Re: Bug in libm or libstdc++. Date: Sun, 28 Feb 1999 22:53:00 -0000 Message-ID: <3.0.6.32.19990226012513.008e5450@pop.globalserve.net> References: <3.0.6.32.19990222090333.00847df0@pop.globalserve.net> <199902242332.PAA09334@atrus.synopsys.com> X-SW-Source: 1999-02n/msg01318.html Message-ID: <19990228225300.vJ7WzV-xzGM68aZVfqZlIQCuJOu7lpf7P0dkXX8UJWA@z> At 03:32 PM 2/24/99 PST, you wrote: >You have already been informed that libstdc++ is not complete. Sorry. The standard has been around in largely complete form for over a year, and finalized for many months. I am curious as to what is the cause for all of these omissions... I would love to help but I don't know the first thing about implementing these mathematical functions. In any case, to avoid any more unpleasant surprised I would like to see a list of all the omissions in the current libstdc++ and other non-conformances, and where possible ETAs for the missing components. It would be a good idea to post a periodic libstdc++ progress report and calls for volunteers to implement some of the stuff. I think that might attract more developers to fixing up and finishing implementing the standard C++ library. An area where I may be able to help is with the standard valarray and its friends, once I get back a response regarding making the compiler eliminate temporaries and excess copies in argument passing and return. -- .*. "Clouds are not spheres, mountains are not cones, coastlines are not -() < circles, and bark is not smooth, nor does lightning travel in a `*' straight line." ------------------------------------------------- -- B. Mandelbrot | http://surf.to/pgd.net _____________________ ____|________ Paul Derbyshire pderbysh@usa.net Programmer & Humanist|ICQ: 10423848|