Re: Eliminating GCC 3.3 warning
Bob Friesenhahn <[email protected]>
| Newsgroups | gmane.comp.video.graphicsmagick.core |
|---|---|
| Message-ID | <[email protected]> |
Besides warning about LiberateMemory, I expect that GCC 3.3 also warns about ReacquireMemory since it also takes a 'void **' argument. The only other interface which accepts a 'void **' argument is the experimental ReadBlobZC function. I'll see if I can come up with some macros and associated functions which avoid the annoying warning, while helping to avoid accidental bugs by eliminating unnecessary pointer casts. Bob ====================================== Bob Friesenhahn [email protected] http://www.simplesystems.org/users/bfriesen ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com