> Correctness being, don't import it if you're not using it? I guess it bears > testing both ways, and I'm definitely not asking for a definitive answer, but > a general guideline (which it seems like you just described!). Thanks for > your thoughts on this one.
No; we're discussing 2 mostly-orthogonal things: * OpenGL correctness (getting the right pixels to the right place at the right time) * whether or not the header is necessary In plugins where you are not using any GL, including the header probably isn't necessary. In plugins where you are using GL, you'll want to include the header, _OR_ take proper precautions to ensure you get correct results (include other GL headers, preserve the current context, set the context QC hands you to the current context, issue gl calls, and then restore the original context). There's absolutely no reason to go through that procedure though (it's expensive, and CGLMacro.h provides the exact same functionality with less overhead), other than curiosity perhaps. Before I knew CGLMacro.h existed, I used to do that (back when dinosaurs ruled the earth, otherwise known as 2007). As far as "code correctness" is concerned, the compiler and linker will do a better job of telling you that. Needlessly including the header isn't particularly harmful in this situation. -- Christopher Wright [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
