There are a number of leaks and other memory related issues which become identified when the Xcode ANALYZE tool is run again ZXing.
Is there any hope that these problems will be attended?
Here's the list that shows up in my project: (ZXing 2.1)
ZXingWidget Group
~/zxing-git/cpp/core/src/zxing/common/BitMatrix.cpp
~/zxing-git/cpp/core/src/zxing/common/BitMatrix.cpp:156:3: Address of stack memory associated with temporary object of type 'string_type' returned to caller
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/ReedSolomonDecoder.cpp
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/ReedSolomonDecoder.cpp:114:5: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/ReedSolomonDecoder.cpp:116:34: Use of memory after it is freed (within a call to 'operator->')
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/ReedSolomonDecoder.cpp:127:3: Use of memory after it is freed (within a call to '~Ref')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/MonochromeRectangleDetector.cpp
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/MonochromeRectangleDetector.cpp:100:15: Use of memory after it is freed (within a call to 'operator->')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/MonochromeRectangleDetector.cpp:114:7: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/Detector.cpp
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/Detector.cpp:421:4: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/Detector.cpp:425:5: Use of memory after it is freed (within a call to 'reset')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/Detector.cpp:426:21: Use of memory after it is freed (within a call to 'operator class zxing::datamatrix::ResultPointsAndTransitions *')
~/zxing-git/cpp/core/src/zxing/datamatrix/detector/Detector.cpp:430:2: Use of memory after it is freed (within a call to '~Ref')
~/zxing-git/cpp/core/src/zxing/oned/OneDReader.cpp
~/zxing-git/cpp/core/src/zxing/oned/OneDReader.cpp:173:24: Division by zero
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp:242:11: Use of memory after it is freed (within a call to '~Ref')
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp:276:26: Use of memory after it is freed (within a call to 'operator->')
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp:281:10: Use of memory after it is freed (within a call to '~Ref')
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp:305:34: Use of memory after it is freed (within a call to 'Ref')
~/zxing-git/cpp/core/src/zxing/qrcode/detector/FinderPatternFinder.cpp:398:5: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/ResultPoint.cpp
~/zxing-git/cpp/core/src/zxing/ResultPoint.cpp:83:5: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/ResultPoint.cpp:84:5: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/ResultPoint.cpp:86:1: Use of memory after it is freed (within a call to '~Ref')
~/zxing-git/cpp/core/src/zxing/common/detector/MonochromeRectangleDetector.cpp
~/zxing-git/cpp/core/src/zxing/common/detector/MonochromeRectangleDetector.cpp:115:10: Use of memory after it is freed (within a call to 'operator->')
~/zxing-git/cpp/core/src/zxing/common/detector/MonochromeRectangleDetector.cpp:133:3: Use of memory after it is freed (within a call to 'operator=')
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/GenericGFPoly.cpp
~/zxing-git/cpp/core/src/zxing/common/reedsolomon/GenericGFPoly.cpp:111:5: Use of memory after it is freed (within a call to 'operator=')
I could probably get in there and fix these myself - but then would have to do so with every new release of ZXing I might use.
What