Re: CompositeOperator enum & possible binary incompatibility
Posted: 2009-04-16T09:35:50-07:00
We tack on any new enums onto the end of the list to avoid problems as you describe. However, there is a better solution. ImageMagick wrappers should use ParseMagickOption() and MagickOptionToMnemonic() which are MagickCore option mapping methods which ensures the wrapper is immune from any future enum changes.