-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Diego Biurrun on 9/29/2007 1:14 PM:
>> What's wrong with adding llrint to your code (perhaps with a #define,
>> i.e.,
>>
>> #define llrint my_llrint
>> typeof(llrint) my_llrint(...) { ... }
>>
>> )?
>
> It is ugly and it is a workaround for a problem that should be solved
> outside of FFmpeg. Should every project using llrint add that
> workaround? No, Cygwin should be fixed.
What part of portable programming don't you get? On platforms where
something is lacking, a portable program will use replacement functions to
make up for the platform limitations (autoconf is particularly helpful in
determining whether a platform has limitations so the replacement is not
used on platforms with more features, and gnulib is a good supply of a lot
of replacement functions).
And what part of open source programming don't you get? If it bugs you,
write and submit a patch, so that cygwin WILL have llrint. Cygwin won't
have it until someone takes the time to write it.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFG/qkZ84KuGfSFAYARAuigAKCphfivrZirq6b8iJRaz13E/1XtIwCfQjti
8a7jKJGuYocaMLl3iSfDluA=
=dk7b
-----END PGP SIGNATURE-----
--
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/
