X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <4725D805.2C412C94@dessent.net> Date: Mon, 29 Oct 2007 05:54:29 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: llrint implementation in Cygwin References: <46F6C151 DOT 3070301 AT computer DOT org> <4725D1BA DOT C2D2ED8A AT dessent DOT net> <033e01c81a2a$30ae3150$2e08a8c0 AT CAM DOT ARTIMI DOT COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dave Korn wrote: > I don't think it was being advocated in general, but I think it's reasonable > to assume that a pure const function like llrint isn't going to do anything > wacky. Yes, I realize it was probably not a worry in this particular case, but I didn't want somebody stumbling on the archives at a later date and getting the bright idea that you could just go around extracting random objects from a MinGW library for use in a Cygwin link. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/