Bob Ippolito wrote: > Clearly, but that still doesn't answer the question of who's going to > do it. Writing two code paths with availability macros and all the > testing involved is a whole lot of work to fix a harmless warning on > older versions of the OS. If it actually caused a problem I'm sure > someone would go through the trouble, but in this case it's probably > not worth the effort. I can fully understand that it is not worth your effort (it isn't worth mine, either). However, if Skip (or somebody else) wanted to fix it, I wouldn't mind. So I wouldn't agree to "not worth the effort". Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4