On 30 Sep 2011, at 10:04, Fons Adriaensen wrote:
> Probably for Apple it's not a bug but a feature, and it may
> be one designed to discourage porting of non-Apple software
> to OSX.
Hardly. Apple didn't spend a lot of time and effort to have POSIX compliance
and alienate a bunch of BSD die-hards, just to have a broken API in the end.
> Anyway OSX users should complain about this.
That's why I'm asking. Because the one recurring theme I hear from Apple
engineers is: "If you don't tell us it's broken, we can't fix it" and "bugs get
fixed by priority, i.e. the ones we internally need to ship products and that
might cause loss of data first, and then by how many reports we get about a
certain issue"
Apple, for it's own threading, likely uses GrandCentral Dispatach APIs, so they
may not even notice it's broken, and the same goes for most other typical Mac
developers.
So things like these are only seen by people who port "legacy" or opensource
software to the mac, and these are often not registered Apple Developers (basic
account is free!) and thus don't have access to the Apple Bug reporting system.
It's also important to note, that unless it's an extremely simple fix and/or
security related, Apple will not back-port. So it's important to see if it's
broken in Lion (10.7.x), and then report it as a Lion bug, because Apple
certainly will not fix something like that in Leopard (10.5.x) or Snow Leopard
(10.6.x)
Everyone can sign up for a free Apple developer account (the link to that is
somewhat burried, because Apple rather sells you the $99/year programs which
give additional perks such as access to beta software, etc.),
http://developer.apple.com/programs/register/
and then access
https://bugreport.apple.com/
to report and track his bugs.
Ronald
_______________________________________________
Sursound mailing list
Sursound@music.vt.edu
https://mail.music.vt.edu/mailman/listinfo/sursound
